Cloud Security Maturity Model 2.0
Browse Cloud Security...
ORM-03.2: Cloud service provider preventive policies are in use
ORM-03.2: CSP preventive policies (AWS Service Control Policies, Azure Policies with deny rules, GCP policies) are in use and applied at the root of the hierarchy and to individual org units (OUs)/management groups (MGs)/folders. Using policies at multiple levels of the hierarchy doesn't necessarily indicate all the right policies are in place, but they are a good key indicator that a strategy exists and is being implemented.
  • Control automation: Automated
  • AWS control specification: At least one SCP is applied at the org root. At least two additional SCPs are applied to two or more OUs.
  • Azure control specification: At least one policy with deny statements is applied at the root management group. At least two other policies with deny statements are applied to two or more other MGs.
  • GCP control specification: none
  • Third-party (CSPM/CNAPP) control specification: none
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: Automated
  • AWS control specification: At least one SCP is applied at the org root. At least two additional SCPs are applied to two or more OUs.
  • Azure control specification: At least one policy with deny statements is applied at the root management group. At least two other policies with deny statements are applied to two or more other MGs.
  • GCP control specification: none
  • Third-party (CSPM/CNAPP) control specification: none