Application of Requirements by Classification
Minimum mandatory requirements by application criticality classification
Minimum mandatory requirements by application criticality classification
Prescriptive validation, evidence and control strategies to ensure a secure, auditable and verifiable adoption of Infrastructure as Code.
Binary verification of the application of the practices prescribed in Chapter 05
Binary control checklist of the adoption of monitoring, alerting, incident response and continuous operational health signal practices.
Objective and binary verification of the application of secure deployment practices in a specific project.
Binary, traceable verification checklist of the adoption of the practices of Chapter 13.
Binary control checklist of the application of governance practices per project
Specifics of exception management in the context of Infrastructure as Code - policy engines, enforcement and TTL
Technical and organisational mechanisms to ensure automatic enforcement of security policies in IaC pipelines.
Ways of validating, reinforcing and governing the application of the controls defined in other chapters of SbD-ToE
Planning and control strategies to ensure an effective and auditable adoption of security practices in Infrastructure as Code.
This checklist applies to all applications classified according to the criteria defined in Chapter 01 - Application Criticality Classification.
Binary and auditable checklist to verify the practical application of the security prescriptions for IaC.
Formal verification checklist for secure technical onboarding, with a record and validation per role.
Mapping known threats is an essential mechanism for validating the risk analysis, ensuring that the identified risks reflect real, plausible and documented attack vectors.