Cloud Security Maturity Model 2.0
Browse Cloud Security...
IAM-05.1: An IAM data perimeter is enforced
IAM-05.1: An IAM data perimeter as an advanced concept that restricts where API calls are able to originate. While it may be implemented in all environments, it is especially important for production accounts. This is typically based on IP address but may also rely on device restrictions. Each cloud provider enforces these differently (and not all cloud providers support the capability at all), but the goal is to prevent an attacker from stealing static or session credentials (including tokens) and using them from a location under that attackers control.
  • Control automation: Automated
  • AWS control specification: NOTE: Implementing a data perimeter in AWS is complex. Please read https://aws.amazon.com/identity/data-perimeters-on-aws/ for more information on getting started. These items represent key indicators that are part of a data perimeter strategy:
  • Any AWS SCP implements global condition keys for sourceIP and sourceVPC restrictions
  • Only approved resources (e.g., S3 buckets) allow unrestricted internet access for read and never allow it for other API calls
  • More than two IAM roles not associated with an instance profile in an account use aws:PrincipalOrgID, PrincipalIsAWSService, ViaAWSService, or SourceIP in the role trust policy
  • Azure control specification: The subscription uses conditional access policies consistently
  • GCP control specification: none
  • Third-party (CSPM/CNAPP) control specification: CSPM assesses for key indicators that a data perimeter is enforced
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: NOTE: Implementing a data perimeter in AWS is complex. Please read https://aws.amazon.com/identity/data-perimeters-on-aws/ for more information on getting started. These items represent key indicators that are part of a data perimeter strategy:
  • Any AWS SCP implements global condition keys for sourceIP and sourceVPC restrictions
  • Only approved resources (e.g., S3 buckets) allow unrestricted internet access for read and never allow it for other API calls
  • More than two IAM roles not associated with an instance profile in an account use aws:PrincipalOrgID, PrincipalIsAWSService, ViaAWSService, or SourceIP in the role trust policy
  • Azure control specification: The subscription uses conditional access policies consistently
  • GCP control specification: none
  • Third-party (CSPM/CNAPP) control specification: CSPM assesses for key indicators that a data perimeter is enforced