You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 24, 2024. It is now read-only.
Realise this is in outline phase so just some suggested areas for consideration
i. use of cloud-based code repositories. I've had a number of clients who go to great lengths to secure their cloud infrastructures and then host all of their Infrastructure as Code on cloud-based code repositories secured via username and password!
ii. patching/fixing of consumer code. Seen a number of clients going down the PaaS route assume that they've handed off patch management completely... consumers need to patch their own code.
iii. security of deployment pipelines is key - authentication and authorisation of those that can deploy, how the pipelines retrieve crypto credentials etc when spinning up instances etc. can be messy.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Realise this is in outline phase so just some suggested areas for consideration
i. use of cloud-based code repositories. I've had a number of clients who go to great lengths to secure their cloud infrastructures and then host all of their Infrastructure as Code on cloud-based code repositories secured via username and password!
ii. patching/fixing of consumer code. Seen a number of clients going down the PaaS route assume that they've handed off patch management completely... consumers need to patch their own code.
iii. security of deployment pipelines is key - authentication and authorisation of those that can deploy, how the pipelines retrieve crypto credentials etc when spinning up instances etc. can be messy.
The text was updated successfully, but these errors were encountered: