Identity / IAM / Controls / v2026.11
Enforce Multi-Factor Authentication for Human Identities
CCC.IAM.CN13 · Access Control
Ensure that no human identity can authenticate to the cloud environment with a single factor, so that a compromised password alone grants no access.
Related Capabilities
| ID | Title | Description |
|---|
| CCC.IAM.CP02 | IAM Users | The service can create, list, modify and delete user identities, each representing a single person or application that authenticates directly to the provider's identity platform. |
| CCC.IAM.CP04 | Password Management | The service can set, change and reset passwords for user identities, and may be configured with a password policy that enforces complexity, history and expiry requirements. |
| CCC.IAM.CP14 | Multi-Factor Authentication | The service may be configured to require a second authentication factor when a user signs in, and can require that MFA was used as a condition on sensitive actions. |
| CCC.Core.CP05 | Signed URLs | The service can generate an ad hoc URL containing authentication information to enforce user-configured permissions for accessing a specific component or a child resource. |
| CCC.Core.CP06 | Access Control | The service automatically enforces user configurations to restrict or allow access to a specific component or a child resource based on factors such as user identities, roles, groups, or attributes. |
| CCC.Core.CP23 | Network Access Rules | The service restricts access to child or networked resources based on user-defined network parameters such as IP address, protocol, port, or source. |
| CCC.Core.CP29 | Active Ingestion | While running, the service itself can fetch or reach out to some other service or external source to get data, inputs or commands for the service to process or operate on. |
| CCC.Core.CP33 | Public Access Restriction | The service may be configured to deny all access to a child resource from the public internet, regardless of any resource-level permission that would otherwise grant it. |
Related Threats
| ID | Title | Description |
|---|
| CCC.IAM.TH13 | Multi-Factor Authentication is Not Enforced | MFA enforcement may be left unconfigured or disabled for an identity, or a sign-in may be allowed to complete with a single factor. A password or token obtained through phishing, leakage or brute force is then sufficient to authenticate as that identity. This results in a loss of confidentiality of the resources the identity can read and of integrity where it can write. |
| CCC.Core.TH01 | Access is Granted to Unauthorized Users | Logic designed to give different permissions to different entities may be misconfigured or manipulated, allowing unauthorized entities to access restricted parts of the service, its data, or its child resources. This could result in a loss of data confidentiality or tolerance of unauthorized actions which impact the integrity and availability of resources and data. |
Assessment Requirements
| ID | Text | Applicability |
|---|
| CCC.IAM.CN13.AR01 | When a human identity exists, an MFA enforcement policy MUST apply to it. | tlp-clear, tlp-green, tlp-amber, tlp-red |
| CCC.IAM.CN13.AR02 | When a root, global administrator or break-glass account exists, it MUST have a phishing-resistant MFA method enrolled. | tlp-clear, tlp-green, tlp-amber, tlp-red |