Cloud development policy #298
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…on to reflect that elasticsearch and APM are standard for logging and observability (#287)
… into cloud-development-policy
* training section of cloud development policy * cloud pilots license
* added order of preference for wiremock plus fixed capitalisation (#281) * Create Test-Approach-TSR-Reviews.md (#285) * Correcting the rings on the tech radar referenced by the tech governance policy (#283) * Correcting the rings on the tech radar referenced by the tech governance policy, and some rewording for clarification. * Include a link to the tech radar application on the tech governance page. --------- Co-authored-by: nevillejrbrown <[email protected]> Co-authored-by: Martin Rock-Evans <[email protected]>
* wip * WIP * IaC base * push latest DDC changes * add SC link * adds Tagging policy --------- Co-authored-by: bolt-io <[email protected]> Co-authored-by: Callum Young <[email protected]> Co-authored-by: skins-uk <[email protected]> Co-authored-by: James Thomas <[email protected]>
* Initial pass of the Deployment policy * Fix linting * Add dependency check * Update CloudDevelopmentPolicy.md * Update CloudDevelopmentPolicy.md
Introduced a new "Centralized Secrets Management" section under "Secrets Management" with detailed guidelines on: - Access Control: Use Azure RBAC and Key Vault Access Policies. - Network Security: Enable Private or Service Endpoints. - Secret Rotation and Expiration: Automate renewal and alerting. - Audit and Monitoring: Enable and monitor access logs. - Secure Application Integration: Use Managed Identities, remove hardcoded secrets. - Compliance: Align with UK government standards. - Exceptions: Require documented approval and risk assessment. Co-authored-by: Jim <[email protected]>
software-engineering-policies/CloudDevelopment/CloudDevelopmentPolicy.md
Show resolved
Hide resolved
software-engineering-policies/CloudDevelopment/CloudDevelopmentPolicy.md
Show resolved
Hide resolved
software-engineering-policies/CloudDevelopment/CloudDevelopmentPolicy.md
Show resolved
Hide resolved
software-engineering-policies/CloudDevelopment/CloudDevelopmentPolicy.md
Show resolved
Hide resolved
software-engineering-policies/CloudDevelopment/CloudDevelopmentPolicy.md
Show resolved
Hide resolved
software-engineering-policies/CloudDevelopment/CloudDevelopmentPolicy.md
Show resolved
Hide resolved
software-engineering-policies/CloudDevelopment/CloudDevelopmentPolicy.md
Show resolved
Hide resolved
software-engineering-policies/CloudDevelopment/CloudDevelopmentPolicy.md
Show resolved
Hide resolved
software-engineering-policies/CloudDevelopment/CloudDevelopmentPolicy.md
Show resolved
Hide resolved
software-engineering-policies/CloudDevelopment/CloudDevelopmentPolicy.md
Show resolved
Hide resolved
|
Thanks Jim. I will try to do another look through before the attending the Cloud Guild. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Not intended as a 'complete' policy - missing areas may already be planned, but all suggestions welcome