Cloud Security Maturity Model 2.0
Browse Cloud Security...
LOG-03.2: CSP threat/detection feeds are enabled and collected for at least production environments
LOG-03.2: All cloud providers include add-on security feeds that often require separate subscriptions. While these can incrementally increase costs, they can typically perform monitoring and alerting for active cloud threats that are difficult to otherwise obtain and build. These feeds should be enabled for at least production deployments, with the results feeding a SIEM or other monitoring platform.
  • Control automation: Automated
  • AWS control specification: GuardDuty (GD) is enabled in at least two regions in all accounts labeled "production." If accounts are not labeled, pass if 50% of accounts use GD
  • Azure control specification: Defender for Cloud Standard is enabled in all subscriptions labeled production. If subscriptions are not labeled, pass if >50% of subscriptions use Defender
  • 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: GuardDuty (GD) is enabled in at least two regions in all accounts labeled "production." If accounts are not labeled, pass if 50% of accounts use GD
  • Azure control specification: Defender for Cloud Standard is enabled in all subscriptions labeled production. If subscriptions are not labeled, pass if >50% of subscriptions use Defender
  • GCP control specification: none
  • Third-party (CSPM/CNAPP) control specification: none