Cloud Security Maturity Model 2.0
Browse Cloud Security...
DAT-03.2: Customer-managed encryption keys are used for some resources or services
DAT-03.2: By default, most services in most cloud providers encrypt data using default keys. This meets the requirement for basic compliance and security, but for some data, a customer-managed key (CMK) is more appropriate. Major cloud providers support using your own key (via their key management system) for different services. This can improve security not because it protects from the cloud provider accessing your data, but because splitting the key from the repository reduces inadvertent disclosures and supports separation of duties internally because access to the data and access to the keys can be split. To meet the requirements for Level 3 maturity, only some CMKs in some deployments is required.
  • Control automation: Automated
  • AWS control specification: * KMS is used
  • A CMK exists NOTE: This check should pass even if only some accounts in the organization have any CMKs
  • Azure control specification: none
  • 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: * KMS is used
  • A CMK exists NOTE: This check should pass even if only some accounts in the organization have any CMKs
  • Azure control specification: none
  • GCP control specification: none
  • Third-party (CSPM/CNAPP) control specification: none