Skip to main content

Identity / IAM

CCC Identity and Access Management Controls

Version: v2026.11

IDTitleObjectiveControl FamilyThreat MappingsGuideline MappingsAssessment Requirements
CCC.IAM.CN01Restrict IAM User Credentials CreationPrevent non-administrative principals from creating new long-lived credentials like access keys or generating temporary session tokens. This blocks a common privilege escalation and persistence vector.Access Control152
CCC.IAM.CN02Restrict IAM Policies ModificationEnsure that only designated administrative accounts have the ability to create, modify, or attach policies that define permissions for other identities.Access Control152
CCC.IAM.CN03Restrict Role Assumption / DelegationLimit which principals can assume a role or impersonate a service identity, and which roles a principal may pass to a resource, to only those required. This prevents unintended cross-account or public access by securing the "who can act as this identity" boundary.Access Control354
CCC.IAM.CN04Restrict Wildcard Usage in IAM PoliciesLimit the use of wildcard permissions in IAM policies to prevent overly broad access from being granted by default.Access Control241
CCC.IAM.CN05Strong Password Policies for IAM UsersEnsure that the password policies for IAM users have strong configurations.Access Control141
CCC.IAM.CN06Maximum Age for Long-Term Static CredentialsEnsure that long-lived static credentials like access keys are programmatically rotated within a defined time period to limit the window of opportunity if compromised.Access Control221
CCC.IAM.CN07Automate Identity De-provisioningEnsure that when an identity is terminated in the central Identity Provider (IdP), its corresponding access to cloud resources is revoked automatically.Access Control222
CCC.IAM.CN08Maximum Age for Unused CredentialsEnsure that unused IAM credentials are removed to reduce exposure in the event of potential compromise.Access Control221
CCC.IAM.CN09Enforce Federated Single Sign-On (SSO) for Human UsersEnsure that all human users must authenticate through a central, federated Identity Provider (IdP) to access the cloud environment. This eliminates cloud-native user accounts with long-lived passwords, centralizes authentication controls, and simplifies lifecycle management.Access Control221
CCC.IAM.CN10Alert On Anomalous BehaviourEnsure that logs and associated alerts are generated when anomalous API requests are made by a single identity, such as API requests commonly associated with privilege escalation tactics, originating from an external or malicious IP address or performed by a previously dormant identity, which may indicate that credentials may be compromised, as well as for password brute-force attempts and account lockouts.Observability162
CCC.IAM.CN11Enable Continuous IAM Access and Usage AnalysisEnable and configure the cloud provider's native access and usage analysis services to continuously monitor for external access paths and internal unused access.Observability552
CCC.IAM.CN12Restrict IAM Role CreationEnsure that only designated administrative principals can create roles or service identities, closing a persistence and privilege escalation path.Access Control132
CCC.IAM.CN13Enforce Multi-Factor Authentication for Human IdentitiesEnsure that no human identity can authenticate to the cloud environment with a single factor, so that a compromised password alone grants no access.Access Control222

Imports

IDRemarks
CCC.Core.CN01Encrypt Data for Transmission
CCC.Core.CN03Implement Multi-factor Authentication (MFA) for Access
CCC.Core.CN04Log All Access and Changes
CCC.Core.CN05Prevent Access from Untrusted Entities
CCC.Core.CN07Alert on Unusual Enumeration Activity
CCC.Core.CN09Ensure Integrity of Access Logs
CCC.Core.CN16Alert on Changes to Protective Configuration