Cloud Security Maturity Model 2.0
Browse Cloud Security...
GOV-03.2: Initial benchmarks established
GOV-03.2: An initial set of benchmarks for at least one primary IaaS/PaaS provider is established. Popular choices are the CIS Foundations Benchmark for that provider or the CSP's Best Practices controls. This control objective can be automatically assessed and enforced when using a cloud provider's automated assessment capabilities or a CSPM/CNAPP tool. The objective is manual when the benchmark is adopted but manually managed/assessed.
  • Control automation: Either
  • AWS control specification: Security Hub Security Standards enabled
  • Azure control specification: Defender for Cloud enabled
  • GCP control specification: Security Command Center enabled
  • Third-party (CSPM/CNAPP) control specification: The CSPM assessing maturity also assesses to the CIS or equivalent provider-specific practices framework for each deployment
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: Either
  • AWS control specification: Security Hub Security Standards enabled
  • Azure control specification: Defender for Cloud enabled
  • GCP control specification: Security Command Center enabled
  • Third-party (CSPM/CNAPP) control specification: The CSPM assessing maturity also assesses to the CIS or equivalent provider-specific practices framework for each deployment