Cloud Security Maturity Model 2.0
Browse Cloud Security...
IR-03.2: Cloud incident responders have at least full-read access to all cloud deployments
IR-03.2: It is not possible to effectively investigate many cloud incidents without access to the deployment to evaluate the context and configuration of the resources. Responders can't perform proper analysis using log files and events alone. Responders should have, at a minimum, the capability to escalate to full read access. In many providers a "Security" or "Security Audit" default role does not provide sufficient access. Use of this role can and should be tightly controlled and use a privilege escalation or "break glass" process.
  • Control automation: Either
  • AWS control specification: * A full-read IAM role exists in the account
  • That role is designated for incident responders (can check automatically by using a consistent role name that is the basis for the automated check)
  • 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: Either
  • AWS control specification: * A full-read IAM role exists in the account
  • That role is designated for incident responders (can check automatically by using a consistent role name that is the basis for the automated check)
  • Azure control specification: none
  • GCP control specification: none
  • Third-party (CSPM/CNAPP) control specification: none