Cloud Security Maturity Model 2.0
Browse Cloud Security...
CA-04.1: Technical compliance is continuously assessed using automation
CA-04.1: Although compliance for cloud deployments includes more than just technical configurations, the configuration state is continuously monitored using automated tools. These are typically CSPM/CNAPP tools but may also include compliance automation tools with cloud integrations. For maturity Level 4, the tools in use must cover all major compliance standards the organization must comply with and provide standards-specific reports. For example, a report on PCI or HIPAA and not a generic framework like NIST 800-53 of CIS Foundations Benchmark, unless that framework is designated and accepted by the regulator/compliance body as fully meeting the requirements.
  • Control automation: Partially Automated
  • AWS control specification: * Security Hub is in use with Security Standards and the organization attests that this meets their compliance requirements for that account OR
  • AWS Audit manager is in use and the organization attests that this meets their compliance requirements
  • Azure control specification: none
  • GCP control specification: none
  • Third-party (CSPM/CNAPP) control specification: The CSPM/CNAPP supports the compliance frameworks required by the customer and provides supporting artifacts for audits
Not Applicable - Not applicable
Level 1: Initial - Initial. Manually managing policies/procedures, mostly through console. Architectures tend to resemble traditional infrastructure (e.g., low use of serverless and high reliance on network security controls). IAM mostly ad hoc with little-to-no federation.
Level 2: Repeatable - Repeatable. Policy-/checklist-based and relies more on manual or simple tooling. High variability between projects; not coordinated across deployments. Initial use of infrastructure as code (Terraform/CloudFormation), but security not consistently engaged in design/review. Federation on some accounts, but limited use of MFA due to difficulties supporting teams (especially on the command line).
Level 3: Defined - Defined. Policies and central coordination in place. Some initial security automation still executed manually. Some third-party tooling (orchestration with other tools), Federation on most accounts with widespread MFA, but still gaps on consistency. Security starting to review and promote use of CloudFormation/Terraform. CSPM/CNAPP (CSP or third party) in use.
Level 4: Capable - Capable. Strong centralized security management with consistent enforcement. Automation and guardrails across multiple deployments. Expanding library. Big shift from manual management and execution to running security operations with centralized platforms with centralized management and reporting. Consistent use of federation and MFA, with some gaps supporting toolchains.
Level 5: Efficient - Efficient. All major activities centrally managed, covering all of the CSMM domains. Integrated into infrastructure-as-code (IaC) environment. Built into the stack with provisioning automation. Federation and MFA working consistently across toolchains (e.g., command-line support).

Description
  • Control automation: Partially Automated
  • AWS control specification: * Security Hub is in use with Security Standards and the organization attests that this meets their compliance requirements for that account OR
  • AWS Audit manager is in use and the organization attests that this meets their compliance requirements
  • Azure control specification: none
  • GCP control specification: none
  • Third-party (CSPM/CNAPP) control specification: The CSPM/CNAPP supports the compliance frameworks required by the customer and provides supporting artifacts for audits