Infrastructure as Code (IaC)
Security practices for the definition, validation and management of infrastructure as code
Security practices for the definition, validation and management of infrastructure as code
Canonical catalogue of security requirements for IaC projects (IAC-001 to IAC-013), organised by risk level, with acceptance criteria for the governance of repositories, pipelines, state, modules and configuration drift.
Why this chapter is exceptional, which sources support the IaC requirements catalogue and how to create/adapt the organisational catalogue
Organisational policy that defines the security requirements for the definition, validation, execution and maintenance of Infrastructure as Code (IaC), including configuration scanning, policy-as-code, environment separation, drift control, approved modules and plan signing, proportional to the criticality level (L1, L2, L3).
Practical upskilling for technical teams that develop, review or operate IaC projects securely