Cloud Security Maturity Model 2.0
Browse Cloud Security...
LOG-04.1: Robust cloud platform security telemetry centrally collected
LOG-04.1: Organizations should have a list of required security telemetry from their cloud providers, which will include multiple sources beyond just the management plane logs. These sources should include a mixture of CSP security feeds, service logs/events and workload logs. This control objective can be automatically assessed by looking for a mixture of common security telemetry feeds, but this needs to be backed by manual assessment because, in many cases, security telemetry will be collected using third-party tooling (especially for workload logs).
  • Control automation: Both
  • AWS control specification: Check that more than three of the following security sources are enabled in >50% of monitored accounts:
  • S3 data events
  • Lambda data events
  • Security Hub
  • Access Analyzer
  • VPC Flow Logs
  • Config
  • Security Lake
  • AWS WAF Logs
  • Azure control specification: Check that more than three of the following security sources are enabled in >50% of monitored subscriptions:
  • Azure Defender for Cloud CSPM
  • AAD sign in logs
  • AAD activity log
  • 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: Both
  • AWS control specification: Check that more than three of the following security sources are enabled in >50% of monitored accounts:
  • S3 data events
  • Lambda data events
  • Security Hub
  • Access Analyzer
  • VPC Flow Logs
  • Config
  • Security Lake
  • AWS WAF Logs
  • Azure control specification: Check that more than three of the following security sources are enabled in >50% of monitored subscriptions:
  • Azure Defender for Cloud CSPM
  • AAD sign in logs
  • AAD activity log
  • GCP control specification: none
  • Third-party (CSPM/CNAPP) control specification: none