Common Cloud Controls Catalog (CCC)
Common Cloud Controls Catalog (CCC) for Azure
Run this compliance with Prowler
Run in Prowler Cloudprowler azure --compliance ccc_v2025.10_azureRequirements (172)
CCC.Core.CN01 Encrypt Data for Transmission520
CCC.Core.CN01.AR01When a port is exposed for non-SSH network traffic, all traffic MUST include a TLS handshake AND be encrypted using TLS 1.3 or higher.13
Attributes
- Section
CCC.Core.CN01 Encrypt Data for Transmission
- Family Name
Data
- Applicability
tlp-green
tlp-amber
tlp-red
- Recommendation
Most cloud services enable TLS 1.3 by default. Where it is not already set, ensure that your services are configured or updated accordingly.
- Family Description
The Data control family ensures the confidentiality, integrity, availability, and sovereignty of data across its lifecycle. These controls govern how data is transmitted, stored, replicated, and protected from unauthorized access, tampering, or exposure beyond defined trust perimeters.
- Sub Section Objective
Ensure that all communications are encrypted in transit to protect data integrity and confidentiality.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
CCC.Core.CN01.AR02When a port is exposed for SSH network traffic, all traffic MUST include a SSH handshake AND be encrypted using SSHv2 or higher.2
Attributes
- Section
CCC.Core.CN01 Encrypt Data for Transmission
- Family Name
Data
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Recommendation
Any time port 22 is exposed, ensure that it has a properly implemented SSH server with SSHv2 enabled and configured with strong ciphers.
- Family Description
The Data control family ensures the confidentiality, integrity, availability, and sovereignty of data across its lifecycle. These controls govern how data is transmitted, stored, replicated, and protected from unauthorized access, tampering, or exposure beyond defined trust perimeters.
- Sub Section Objective
Ensure that all communications are encrypted in transit to protect data integrity and confidentiality.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
CCC.Core.CN01.AR03When the service receives unencrypted traffic, then it MUST either block the request or automatically redirect it to the secure equivalent.4
Attributes
- Section
CCC.Core.CN01 Encrypt Data for Transmission
- Family Name
Data
- Applicability
tlp-green
tlp-amber
tlp-red
- Recommendation
Review firewall, load balancer, and application configurations to ensure insecure protocols such as HTTP, FTP, and Telnet are not exposed. Where possible, implement automatic redirection to secure protocols such as HTTPS, SFTP, SSH, and regularly scan for protocol drift.
- Family Description
The Data control family ensures the confidentiality, integrity, availability, and sovereignty of data across its lifecycle. These controls govern how data is transmitted, stored, replicated, and protected from unauthorized access, tampering, or exposure beyond defined trust perimeters.
- Sub Section Objective
Ensure that all communications are encrypted in transit to protect data integrity and confidentiality.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
CCC.Core.CN01.AR07When a port is exposed, the service MUST ensure that the protocol and service officially assigned to that port number by the IANA Service Name and Transport Protocol Port Number Registry, and no other, is run on that port.0
Attributes
- Section
CCC.Core.CN01 Encrypt Data for Transmission
- Family Name
Data
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Recommendation
Reference the IANA Service Name and Transport Protocol Port Number Registry for more information about correct protocol-to-port assignments. Avoid running non-standard services on well-known ports.
- Family Description
The Data control family ensures the confidentiality, integrity, availability, and sovereignty of data across its lifecycle. These controls govern how data is transmitted, stored, replicated, and protected from unauthorized access, tampering, or exposure beyond defined trust perimeters.
- Sub Section Objective
Ensure that all communications are encrypted in transit to protect data integrity and confidentiality.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
CCC.Core.CN01.AR08When a service transmits data using TLS, mutual TLS (mTLS) MUST be implemented to require both client and server certificate authentication for all connections.1
Attributes
- Section
CCC.Core.CN01 Encrypt Data for Transmission
- Family Name
Data
- Applicability
tlp-amber
tlp-red
- Recommendation
Configure mTLS for all endpoints that process or transmit sensitive data. Ensure both client and server certificates are validated and managed securely. Regularly review certificate authorities and automate certificate rotation where possible.
- Family Description
The Data control family ensures the confidentiality, integrity, availability, and sovereignty of data across its lifecycle. These controls govern how data is transmitted, stored, replicated, and protected from unauthorized access, tampering, or exposure beyond defined trust perimeters.
- Sub Section Objective
Ensure that all communications are encrypted in transit to protect data integrity and confidentiality.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
CCC.Core.CN13 Minimize Lifetime of Encryption and Authentication Certificates36
CCC.Core.CN13.AR01When a port is exposed that uses certificate-based encryption, the service MUST only use valid, unexpired certificates issued by a trusted certificate authority.4
Attributes
- Section
CCC.Core.CN13 Minimize Lifetime of Encryption and Authentication Certificates
- Family Name
Data
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Recommendation
Track certificate expiration dates and automate certificate renewal where possible. Use certificate management tools to ensure only certificates from trusted authorities are deployed.
- Family Description
The Data control family ensures the confidentiality, integrity, availability, and sovereignty of data across its lifecycle. These controls govern how data is transmitted, stored, replicated, and protected from unauthorized access, tampering, or exposure beyond defined trust perimeters.
- Sub Section Objective
Ensure that encryption and authentication certificates have a limited lifetime to reduce the risk of compromise and ensure the use of up-to-date security practices.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
CCC.Core.CN13.AR02When a port is exposed that uses certificate-based encryption, the service MUST rotate active certificates within 180 days of issuance.1
Attributes
- Section
CCC.Core.CN13 Minimize Lifetime of Encryption and Authentication Certificates
- Family Name
Data
- Applicability
tlp-amber
- Recommendation
Track certificate expiration dates and automate certificate renewal where possible. Use certificate management tools to ensure only certificates from trusted authorities are deployed.
- Family Description
The Data control family ensures the confidentiality, integrity, availability, and sovereignty of data across its lifecycle. These controls govern how data is transmitted, stored, replicated, and protected from unauthorized access, tampering, or exposure beyond defined trust perimeters.
- Sub Section Objective
Ensure that encryption and authentication certificates have a limited lifetime to reduce the risk of compromise and ensure the use of up-to-date security practices.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
CCC.Core.CN13.AR03When a port is exposed that uses certificate-based encryption, the service MUST rotate active certificates within 90 days of issuance.1
Attributes
- Section
CCC.Core.CN13 Minimize Lifetime of Encryption and Authentication Certificates
- Family Name
Data
- Applicability
tlp-red
- Recommendation
Track certificate expiration dates and automate certificate renewal where possible. Use certificate management tools to ensure only certificates from trusted authorities are deployed.
- Family Description
The Data control family ensures the confidentiality, integrity, availability, and sovereignty of data across its lifecycle. These controls govern how data is transmitted, stored, replicated, and protected from unauthorized access, tampering, or exposure beyond defined trust perimeters.
- Sub Section Objective
Ensure that encryption and authentication certificates have a limited lifetime to reduce the risk of compromise and ensure the use of up-to-date security practices.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
CCC.Core.CN06 Restrict Deployments to Trust Perimeter20
CCC.Core.CN06.AR01When the service is running, its region and availability zone MUST be included in a list of explicitly trusted or approved locations within the trust perimeter.0
Attributes
- Section
CCC.Core.CN06 Restrict Deployments to Trust Perimeter
- Family Name
Data
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Recommendation
Maintain an up-to-date list of trusted and approved regions based on organizational policies. Validate the service's deployment location is included in this list.
- Family Description
The Data control family ensures the confidentiality, integrity, availability, and sovereignty of data across its lifecycle. These controls govern how data is transmitted, stored, replicated, and protected from unauthorized access, tampering, or exposure beyond defined trust perimeters.
- Sub Section Objective
Ensure that the service and its child resources are only deployed on infrastructure in locations that are explicitly included within a defined trust perimeter.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
CCC.Core.CN06.AR02When a child resource is deployed, its region and availability zone MUST be included in a list of explicitly trusted or approved locations within the trust perimeter.0
Attributes
- Section
CCC.Core.CN06 Restrict Deployments to Trust Perimeter
- Family Name
Data
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Recommendation
Maintain an up-to-date list of trusted and approved regions based on organizational policies. Validate that child resources can only be deployed to locations included in this list.
- Family Description
The Data control family ensures the confidentiality, integrity, availability, and sovereignty of data across its lifecycle. These controls govern how data is transmitted, stored, replicated, and protected from unauthorized access, tampering, or exposure beyond defined trust perimeters.
- Sub Section Objective
Ensure that the service and its child resources are only deployed on infrastructure in locations that are explicitly included within a defined trust perimeter.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
CCC.Core.CN08 Replicate Data to Multiple Locations23
CCC.Core.CN08.AR01When data is created or modified, the data MUST have a complete and recoverable duplicate that is stored in a physically separate data center.2
Attributes
- Section
CCC.Core.CN08 Replicate Data to Multiple Locations
- Family Name
Data
- Applicability
tlp-green
tlp-amber
tlp-red
- Recommendation
Implement automated data replication processes to ensure that data is consistently duplicated in another region or availability zone. Regularly test data recovery from the replicated location to ensure integrity and availability.
- Family Description
The Data control family ensures the confidentiality, integrity, availability, and sovereignty of data across its lifecycle. These controls govern how data is transmitted, stored, replicated, and protected from unauthorized access, tampering, or exposure beyond defined trust perimeters.
- Sub Section Objective
Ensure that data is replicated across multiple physical locations to protect against data loss due to hardware failures, natural disasters, or other catastrophic events.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
CCC.Core.CN08.AR02When data is replicated into a second location, the service MUST be able to accurately represent the replication locations, replication status, and data synchronization status.1
Attributes
- Section
CCC.Core.CN08 Replicate Data to Multiple Locations
- Family Name
Data
- Applicability
tlp-green
tlp-amber
tlp-red
- Family Description
The Data control family ensures the confidentiality, integrity, availability, and sovereignty of data across its lifecycle. These controls govern how data is transmitted, stored, replicated, and protected from unauthorized access, tampering, or exposure beyond defined trust perimeters.
- Sub Section Objective
Ensure that data is replicated across multiple physical locations to protect against data loss due to hardware failures, natural disasters, or other catastrophic events.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
CCC.Core.CN09 Ensure Integrity of Access Logs35
CCC.Core.CN09.AR01When the service is operational, its logs and any child resource logs MUST NOT be accessible from the resource they record access to.2
Attributes
- Section
CCC.Core.CN09 Ensure Integrity of Access Logs
- Family Name
Data
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Family Description
The Data control family ensures the confidentiality, integrity, availability, and sovereignty of data across its lifecycle. These controls govern how data is transmitted, stored, replicated, and protected from unauthorized access, tampering, or exposure beyond defined trust perimeters.
- Sub Section Objective
Ensure that access logs are always recorded to an external location that cannot be manipulated from the context of the service(s) it contains logs for.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
CCC.Core.CN09.AR02When the service is operational, disabling the logs for the service or its child resources MUST NOT be possible without also disabling the corresponding resource.2
Attributes
- Section
CCC.Core.CN09 Ensure Integrity of Access Logs
- Family Name
Data
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Recommendation
No normal business operations should disable logs, as this could indicate an attempt to cover up unauthorized access. Ensure that logging mechanisms are tightly integrated with service operations, so that logging cannot be disabled without stopping the service itself.
- Family Description
The Data control family ensures the confidentiality, integrity, availability, and sovereignty of data across its lifecycle. These controls govern how data is transmitted, stored, replicated, and protected from unauthorized access, tampering, or exposure beyond defined trust perimeters.
- Sub Section Objective
Ensure that access logs are always recorded to an external location that cannot be manipulated from the context of the service(s) it contains logs for.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
CCC.Core.CN09.AR03When the service is operational, any attempt to redirect logs for the service or its child resources MUST NOT be possible without halting operation of the corresponding resource and publishing corresponding events to monitored channels.1
Attributes
- Section
CCC.Core.CN09 Ensure Integrity of Access Logs
- Family Name
Data
- Applicability
tlp-amber
tlp-red
- Recommendation
No normal business operations should result in the redirection of logs, as this could indicate an attempt to cover up unauthorized access. Ensure that logging configurations are immutable during service operation so that any changes require stopping the service and publishing corresponding events to monitored channels.
- Family Description
The Data control family ensures the confidentiality, integrity, availability, and sovereignty of data across its lifecycle. These controls govern how data is transmitted, stored, replicated, and protected from unauthorized access, tampering, or exposure beyond defined trust perimeters.
- Sub Section Objective
Ensure that access logs are always recorded to an external location that cannot be manipulated from the context of the service(s) it contains logs for.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
CCC.Core.CN10 Restrict Data Replication to Trust Perimeter11
CCC.Core.CN10.AR01When data is replicated, the service MUST ensure that replication only occurs to destinations that are explicitly included within the defined trust perimeter.1
Attributes
- Section
CCC.Core.CN10 Restrict Data Replication to Trust Perimeter
- Family Name
Data
- Applicability
tlp-green
tlp-amber
tlp-red
- Family Description
The Data control family ensures the confidentiality, integrity, availability, and sovereignty of data across its lifecycle. These controls govern how data is transmitted, stored, replicated, and protected from unauthorized access, tampering, or exposure beyond defined trust perimeters.
- Sub Section Objective
Ensure that data is only replicated on infrastructure in locations that are explicitly included within a defined trust perimeter.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
CCC.Core.CN02 Encrypt Data for Storage18
CCC.Core.CN02.AR01When data is stored, it MUST be encrypted using the latest industry-standard encryption methods.8
Attributes
- Section
CCC.Core.CN02 Encrypt Data for Storage
- Family Name
Data
- Applicability
tlp-green
tlp-amber
tlp-red
- Family Description
The Data control family ensures the confidentiality, integrity, availability, and sovereignty of data across its lifecycle. These controls govern how data is transmitted, stored, replicated, and protected from unauthorized access, tampering, or exposure beyond defined trust perimeters.
- Sub Section Objective
Ensure that all data stored is encrypted at rest using strong encryption algorithms.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
CCC.Core.CN11 Protect Encryption Keys615
CCC.Core.CN11.AR01When encryption keys are used, the service MUST verify that all encryption keys use the latest industry-standard cryptographic algorithms.1
Attributes
- Section
CCC.Core.CN11 Protect Encryption Keys
- Family Name
Data
- Applicability
tlp-amber
tlp-red
- Family Description
The Data control family ensures the confidentiality, integrity, availability, and sovereignty of data across its lifecycle. These controls govern how data is transmitted, stored, replicated, and protected from unauthorized access, tampering, or exposure beyond defined trust perimeters.
- Sub Section Objective
Ensure that encryption keys are managed securely by enforcing the use of approved algorithms, regular key rotation, and customer-managed encryption keys (CMEKs).
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
CCC.Core.CN11.AR02When encryption keys are used, the service MUST rotate active keys within 180 days of issuance.1
Attributes
- Section
CCC.Core.CN11 Protect Encryption Keys
- Family Name
Data
- Applicability
tlp-amber
- Family Description
The Data control family ensures the confidentiality, integrity, availability, and sovereignty of data across its lifecycle. These controls govern how data is transmitted, stored, replicated, and protected from unauthorized access, tampering, or exposure beyond defined trust perimeters.
- Sub Section Objective
Ensure that encryption keys are managed securely by enforcing the use of approved algorithms, regular key rotation, and customer-managed encryption keys (CMEKs).
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
CCC.Core.CN11.AR03When encrypting data, the service MUST verify that customer-managed encryption keys (CMEKs) are used.5
Attributes
- Section
CCC.Core.CN11 Protect Encryption Keys
- Family Name
Data
- Applicability
tlp-amber
tlp-red
- Family Description
The Data control family ensures the confidentiality, integrity, availability, and sovereignty of data across its lifecycle. These controls govern how data is transmitted, stored, replicated, and protected from unauthorized access, tampering, or exposure beyond defined trust perimeters.
- Sub Section Objective
Ensure that encryption keys are managed securely by enforcing the use of approved algorithms, regular key rotation, and customer-managed encryption keys (CMEKs).
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
CCC.Core.CN11.AR04When encryption keys are accessed, the service MUST verify that access to encryption keys is restricted to authorized personnel and services, following the principle of least privilege.5
Attributes
- Section
CCC.Core.CN11 Protect Encryption Keys
- Family Name
Data
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Family Description
The Data control family ensures the confidentiality, integrity, availability, and sovereignty of data across its lifecycle. These controls govern how data is transmitted, stored, replicated, and protected from unauthorized access, tampering, or exposure beyond defined trust perimeters.
- Sub Section Objective
Ensure that encryption keys are managed securely by enforcing the use of approved algorithms, regular key rotation, and customer-managed encryption keys (CMEKs).
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
CCC.Core.CN11.AR05When encryption keys are used, the service MUST rotate active keys within 365 days of issuance.1
Attributes
- Section
CCC.Core.CN11 Protect Encryption Keys
- Family Name
Data
- Applicability
tlp-clear
tlp-green
- Family Description
The Data control family ensures the confidentiality, integrity, availability, and sovereignty of data across its lifecycle. These controls govern how data is transmitted, stored, replicated, and protected from unauthorized access, tampering, or exposure beyond defined trust perimeters.
- Sub Section Objective
Ensure that encryption keys are managed securely by enforcing the use of approved algorithms, regular key rotation, and customer-managed encryption keys (CMEKs).
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
CCC.Core.CN11.AR06When encryption keys are used, the service MUST rotate active keys within 90 days of issuance.2
Attributes
- Section
CCC.Core.CN11 Protect Encryption Keys
- Family Name
Data
- Applicability
tlp-red
- Family Description
The Data control family ensures the confidentiality, integrity, availability, and sovereignty of data across its lifecycle. These controls govern how data is transmitted, stored, replicated, and protected from unauthorized access, tampering, or exposure beyond defined trust perimeters.
- Sub Section Objective
Ensure that encryption keys are managed securely by enforcing the use of approved algorithms, regular key rotation, and customer-managed encryption keys (CMEKs).
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
CCC.Core.CN14 Maintain Recent Backups36
CCC.Core.CN14.AR01When backups are created for disaster recovery purposes, the storage mechanism MUST NOT allow modification or deletion within 30 days of creation.2
Attributes
- Section
CCC.Core.CN14 Maintain Recent Backups
- Family Name
Data
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Recommendation
Use immutable storage solutions where possible. Implement backup retention policies that enforce a minimum retention period of 30 days.
- Family Description
The Data control family ensures the confidentiality, integrity, availability, and sovereignty of data across its lifecycle. These controls govern how data is transmitted, stored, replicated, and protected from unauthorized access, tampering, or exposure beyond defined trust perimeters.
- Sub Section Objective
Ensure that all backups used for disaster recovery are recent and subject to a retention policy that limits deletion.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
CCC.Core.CN14.AR02When backups are created for disaster recovery purposes, the most recent backup MUST have a creation date within the past 30 days.2
Attributes
- Section
CCC.Core.CN14 Maintain Recent Backups
- Family Name
Data
- Applicability
tlp-clear
tlp-green
tlp-amber
- Recommendation
Implement automated backup processes to ensure that backups are created regularly. Monitor backup schedules and verify that the most recent backup creation date is within the last 30 days.
- Family Description
The Data control family ensures the confidentiality, integrity, availability, and sovereignty of data across its lifecycle. These controls govern how data is transmitted, stored, replicated, and protected from unauthorized access, tampering, or exposure beyond defined trust perimeters.
- Sub Section Objective
Ensure that all backups used for disaster recovery are recent and subject to a retention policy that limits deletion.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
CCC.Core.CN14.AR03When backups are created for disaster recovery purposes, the most recent backup MUST have a creation date within the past 14 days.2
Attributes
- Section
CCC.Core.CN14 Maintain Recent Backups
- Family Name
Data
- Applicability
tlp-red
- Recommendation
Implement automated backup processes to ensure that backups are created regularly. Monitor backup schedules and verify that the most recent backup creation date is within the last 14 days.
- Family Description
The Data control family ensures the confidentiality, integrity, availability, and sovereignty of data across its lifecycle. These controls govern how data is transmitted, stored, replicated, and protected from unauthorized access, tampering, or exposure beyond defined trust perimeters.
- Sub Section Objective
Ensure that all backups used for disaster recovery are recent and subject to a retention policy that limits deletion.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
CCC.Core.CN03 Implement Multi-factor Authentication (MFA) for Access413
CCC.Core.CN03.AR01When an entity attempts to modify the service through a user interface, the authentication process MUST require multiple identifying factors for authentication.4
Attributes
- Section
CCC.Core.CN03 Implement Multi-factor Authentication (MFA) for Access
- Family Name
Identity and Access Management
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Family Description
The Identity and Access Management control family ensures that only trusted and authenticated entities can access resources. These controls establish strong authentication, enforce multi-factor verification, and restrict access to approved sources to prevent unauthorized use or data exfiltration.
- Sub Section Objective
Ensure that all sensitive activities require two or more identity factors during authentication to prevent unauthorized access.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
CCC.Core.CN03.AR02When an entity attempts to modify the service through an API endpoint, the authentication process MUST require a credential such as an API key or token AND originate from within the trust perimeter.3
Attributes
- Section
CCC.Core.CN03 Implement Multi-factor Authentication (MFA) for Access
- Family Name
Identity and Access Management
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Family Description
The Identity and Access Management control family ensures that only trusted and authenticated entities can access resources. These controls establish strong authentication, enforce multi-factor verification, and restrict access to approved sources to prevent unauthorized use or data exfiltration.
- Sub Section Objective
Ensure that all sensitive activities require two or more identity factors during authentication to prevent unauthorized access.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
CCC.Core.CN03.AR03When an entity attempts to view information on the service through a user interface, the authentication process MUST require multiple identifying factors from the user.4
Attributes
- Section
CCC.Core.CN03 Implement Multi-factor Authentication (MFA) for Access
- Family Name
Identity and Access Management
- Applicability
tlp-amber
tlp-red
- Family Description
The Identity and Access Management control family ensures that only trusted and authenticated entities can access resources. These controls establish strong authentication, enforce multi-factor verification, and restrict access to approved sources to prevent unauthorized use or data exfiltration.
- Sub Section Objective
Ensure that all sensitive activities require two or more identity factors during authentication to prevent unauthorized access.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
CCC.Core.CN03.AR04When an entity attempts to view information on the service through an API endpoint, the authentication process MUST require a credential such as an API key or token AND originate from within the trust perimeter.2
Attributes
- Section
CCC.Core.CN03 Implement Multi-factor Authentication (MFA) for Access
- Family Name
Identity and Access Management
- Applicability
tlp-amber
tlp-red
- Family Description
The Identity and Access Management control family ensures that only trusted and authenticated entities can access resources. These controls establish strong authentication, enforce multi-factor verification, and restrict access to approved sources to prevent unauthorized use or data exfiltration.
- Sub Section Objective
Ensure that all sensitive activities require two or more identity factors during authentication to prevent unauthorized access.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
CCC.Core.CN05 Prevent Access from Untrusted Entities658
CCC.Core.CN05.AR01When an attempt is made to modify data on the service or a child resource, the service MUST block requests from unauthorized entities.16
Attributes
- Section
CCC.Core.CN05 Prevent Access from Untrusted Entities
- Family Name
Identity and Access Management
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Family Description
The Identity and Access Management control family ensures that only trusted and authenticated entities can access resources. These controls establish strong authentication, enforce multi-factor verification, and restrict access to approved sources to prevent unauthorized use or data exfiltration.
- Sub Section Objective
Ensure that secure access controls enforce the principle of least privilege to restrict access to authorized entities from explicitly trusted sources only.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
CCC.Core.CN05.AR02When administrative access or configuration change is attempted on the service or a child resource, the service MUST refuse requests from unauthorized entities.10
Attributes
- Section
CCC.Core.CN05 Prevent Access from Untrusted Entities
- Family Name
Identity and Access Management
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Family Description
The Identity and Access Management control family ensures that only trusted and authenticated entities can access resources. These controls establish strong authentication, enforce multi-factor verification, and restrict access to approved sources to prevent unauthorized use or data exfiltration.
- Sub Section Objective
Ensure that secure access controls enforce the principle of least privilege to restrict access to authorized entities from explicitly trusted sources only.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
CCC.Core.CN05.AR03When administrative access or configuration change is attempted on the service or a child resource in a multi-tenant environment, the service MUST refuse requests across tenant boundaries unless the origin is explicitly included in a pre-approved allowlist.3
Attributes
- Section
CCC.Core.CN05 Prevent Access from Untrusted Entities
- Family Name
Identity and Access Management
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Family Description
The Identity and Access Management control family ensures that only trusted and authenticated entities can access resources. These controls establish strong authentication, enforce multi-factor verification, and restrict access to approved sources to prevent unauthorized use or data exfiltration.
- Sub Section Objective
Ensure that secure access controls enforce the principle of least privilege to restrict access to authorized entities from explicitly trusted sources only.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
CCC.Core.CN05.AR04When data is requested from outside the trust perimeter, the service MUST refuse requests from unauthorized entities.12
Attributes
- Section
CCC.Core.CN05 Prevent Access from Untrusted Entities
- Family Name
Identity and Access Management
- Applicability
tlp-amber
tlp-red
- Family Description
The Identity and Access Management control family ensures that only trusted and authenticated entities can access resources. These controls establish strong authentication, enforce multi-factor verification, and restrict access to approved sources to prevent unauthorized use or data exfiltration.
- Sub Section Objective
Ensure that secure access controls enforce the principle of least privilege to restrict access to authorized entities from explicitly trusted sources only.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
CCC.Core.CN05.AR05When any request is made from outside the trust perimeter, the service MUST NOT provide any response that may indicate the service exists.9
Attributes
- Section
CCC.Core.CN05 Prevent Access from Untrusted Entities
- Family Name
Identity and Access Management
- Applicability
tlp-red
- Family Description
The Identity and Access Management control family ensures that only trusted and authenticated entities can access resources. These controls establish strong authentication, enforce multi-factor verification, and restrict access to approved sources to prevent unauthorized use or data exfiltration.
- Sub Section Objective
Ensure that secure access controls enforce the principle of least privilege to restrict access to authorized entities from explicitly trusted sources only.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
CCC.Core.CN05.AR06When any request is made to the service or a child resource, the service MUST refuse requests from unauthorized entities.8
Attributes
- Section
CCC.Core.CN05 Prevent Access from Untrusted Entities
- Family Name
Identity and Access Management
- Applicability
tlp-green
tlp-amber
tlp-red
- Family Description
The Identity and Access Management control family ensures that only trusted and authenticated entities can access resources. These controls establish strong authentication, enforce multi-factor verification, and restrict access to approved sources to prevent unauthorized use or data exfiltration.
- Sub Section Objective
Ensure that secure access controls enforce the principle of least privilege to restrict access to authorized entities from explicitly trusted sources only.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
CCC.Core.CN04 Log All Access and Changes318
CCC.Core.CN04.AR01When administrative access or configuration change is attempted on the service or a child resource, the service MUST log the client identity, time, and result of the attempt.10
Attributes
- Section
CCC.Core.CN04 Log All Access and Changes
- Family Name
Logging and Monitoring
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Family Description
The Logging & Monitoring control family ensures that access, changes, and security-relevant events are captured, monitored, and alerted on in order to provide visibility, support incident response, and meet compliance requirements.
- Sub Section Objective
Ensure that all access attempts are logged to maintain a detailed audit trail for security and compliance purposes.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
CCC.Core.CN04.AR02When any attempt is made to modify data on the service or a child resource, the service MUST log the client identity, time, and result of the attempt.4
Attributes
- Section
CCC.Core.CN04 Log All Access and Changes
- Family Name
Logging and Monitoring
- Applicability
tlp-amber
tlp-red
- Family Description
The Logging & Monitoring control family ensures that access, changes, and security-relevant events are captured, monitored, and alerted on in order to provide visibility, support incident response, and meet compliance requirements.
- Sub Section Objective
Ensure that all access attempts are logged to maintain a detailed audit trail for security and compliance purposes.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
CCC.Core.CN04.AR03When any attempt is made to read data on the service or a child resource, the service MUST log the client identity, time, and result of the attempt.4
Attributes
- Section
CCC.Core.CN04 Log All Access and Changes
- Family Name
Logging and Monitoring
- Applicability
tlp-red
- Family Description
The Logging & Monitoring control family ensures that access, changes, and security-relevant events are captured, monitored, and alerted on in order to provide visibility, support incident response, and meet compliance requirements.
- Sub Section Objective
Ensure that all access attempts are logged to maintain a detailed audit trail for security and compliance purposes.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
CCC.Core.CN07 Alert on Unusual Enumeration Activity20
CCC.Core.CN07.AR01When enumeration activities are detected, the service MUST publish an event to a monitored channel which includes the client identity, time, and nature of the activity.0
Attributes
- Section
CCC.Core.CN07 Alert on Unusual Enumeration Activity
- Family Name
Logging and Monitoring
- Applicability
tlp-amber
tlp-red
- Recommendation
Implement event publication mechanisms and alerts for patterns indicative of enumeration activities, such as repeated access attempts, requests, or liveness probes. Configure alerts to notify security teams of any activities that merit further investigation.
- Family Description
The Logging & Monitoring control family ensures that access, changes, and security-relevant events are captured, monitored, and alerted on in order to provide visibility, support incident response, and meet compliance requirements.
- Sub Section Objective
Ensure that logs and associated alerts are generated when unusual enumeration activity is detected that may indicate reconnaissance activities.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
CCC.Core.CN07.AR02When enumeration activities are detected, the service MUST log the client identity, time, and nature of the activity.0
Attributes
- Section
CCC.Core.CN07 Alert on Unusual Enumeration Activity
- Family Name
Logging and Monitoring
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Recommendation
Implement logging mechanisms to capture details of enumeration activities, including client identity, timestamps, and activity nature. Retain logs according to organizational policies, and occasionally review them for patterns that may indicate reconnaissance activities.
- Family Description
The Logging & Monitoring control family ensures that access, changes, and security-relevant events are captured, monitored, and alerted on in order to provide visibility, support incident response, and meet compliance requirements.
- Sub Section Objective
Ensure that logs and associated alerts are generated when unusual enumeration activity is detected that may indicate reconnaissance activities.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
CCC.AuditLog.CN01 Implement Digital Signatures With Hash Chaining20
CCC.AuditLog.CN01.AR01When the signature validation process is performed, then it MUST detect any modification of data.0
Attributes
- Section
CCC.AuditLog.CN01 Implement Digital Signatures With Hash Chaining
- Family Name
Integrity
- Applicability
tlp-red
- Recommendation
Ensure hash of data is included in digital signature.
- Family Description
Controls designed to protected the integrity of Audit Log data.
- Sub Section Objective
Digital signatures allows for external verification of log data tampering and hash chaining allows for deleted log files to be detected.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.AuditLog.CN01.AR02When the signature validation process is performed, then it MUST detect any missing (deleted) log file.0
Attributes
- Section
CCC.AuditLog.CN01 Implement Digital Signatures With Hash Chaining
- Family Name
Integrity
- Applicability
tlp-red
- Recommendation
Ensure verification process includes a chained hash function.
- Family Description
Controls designed to protected the integrity of Audit Log data.
- Sub Section Objective
Digital signatures allows for external verification of log data tampering and hash chaining allows for deleted log files to be detected.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.AuditLog.CN02 Enable And Validate All Audit Log Types12
CCC.AuditLog.CN02.AR01When a manual action is performed to generate each audit log type, then the corresponding audit log type MUST be generated and recorded.2
Attributes
- Section
CCC.AuditLog.CN02 Enable And Validate All Audit Log Types
- Family Name
Integrity
- Applicability
tlp-red
tlp-amber
- Recommendation
Review audit log configuration
- Family Description
Controls designed to protected the integrity of Audit Log data.
- Sub Section Objective
Review audit log configuration and ensure that all audit log types are being generated and replicated to configured sinks
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.AuditLog.CN03 Alert On Audit Log Changes And Access20
CCC.AuditLog.CN03.AR01When an attempt is made to disable a log source, then an alert MUST be generated.0
Attributes
- Section
CCC.AuditLog.CN03 Alert On Audit Log Changes And Access
- Family Name
Integrity
- Applicability
tlp-red
tlp-amber
- Recommendation
Ensure alerting is correctly configured
- Family Description
Controls designed to protected the integrity of Audit Log data.
- Sub Section Objective
Ensure that specific alerts have been configured to detect changes in audit log configuration such as disabling exporting of logs. Alerts MUST also be created to detect changes in retention/object lock policies for exported data log sources/buckets.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.AuditLog.CN03.AR02When an attempt is made to alter the retention or object lock status of an external data log source or bucket, then an alert MUST be generated.0
Attributes
- Section
CCC.AuditLog.CN03 Alert On Audit Log Changes And Access
- Family Name
Integrity
- Applicability
tlp-red
tlp-amber
- Recommendation
Ensure alerting is correctly configured
- Family Description
Controls designed to protected the integrity of Audit Log data.
- Sub Section Objective
Ensure that specific alerts have been configured to detect changes in audit log configuration such as disabling exporting of logs. Alerts MUST also be created to detect changes in retention/object lock policies for exported data log sources/buckets.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.AuditLog.CN04 Ensure Access Logging Is Enabled on the Audit Log Bucket11
CCC.AuditLog.CN04.AR01When audit log buckets are created then verify that server access logging MUST be enabled for the audit log bucket, with logs delivered to a separate, secure logging bucket.1
Attributes
- Section
CCC.AuditLog.CN04 Ensure Access Logging Is Enabled on the Audit Log Bucket
- Family Name
Integrity
- Applicability
tlp-red
tlp-amber
- Recommendation
Configure the audit log bucket to enable server access logging. Ensure the target logging bucket is configured for appropriate security, including restricted access and immutability.
- Family Description
Controls designed to protected the integrity of Audit Log data.
- Sub Section Objective
Ensure that access logging is enabled for the audit log storage bucket to capture all requests made to the bucket, providing an audit trail of data access.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.AuditLog.CN05 Export Audit Logs To Bucket12
CCC.AuditLog.CN05.AR01When audit logs are exported, then audit logs MUST be present in the configured data location.2
Attributes
- Section
CCC.AuditLog.CN05 Export Audit Logs To Bucket
- Family Name
Availability
- Applicability
tlp-red
tlp-amber
- Recommendation
Configure audit log exporting.
- Family Description
Controls designed to protected the availability of Audit Log data.
- Sub Section Objective
Configure audit logs to be sent to a external bucket where they can be globally replicated and can be subject to greater access control and data retention polices.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.AuditLog.CN06 Enforce Retention Policy on Audit Log Bucket10
CCC.AuditLog.CN06.AR01When the retention policy is applied, then data MUST be automatically deleted after the configured number of days.0
Attributes
- Section
CCC.AuditLog.CN06 Enforce Retention Policy on Audit Log Bucket
- Family Name
Availability
- Applicability
tlp-red
tlp-amber
tlp-green
- Recommendation
Configure the audit log bucket's lifecycle rules or object retention settings to enforce the required data retention period.
- Family Description
Controls designed to protected the availability of Audit Log data.
- Sub Section Objective
Configure a custom retention policy on the designated audit log bucket to ensure that logs are retained for the correct number of days as defined by your organization's policy.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.AuditLog.CN07 Enforce MFA Delete on Audit Log Bucket10
CCC.AuditLog.CN07.AR01When a standard file deletion is attempted on an object within the audit log bucket, then it MUST be prevented unless MFA is provided.0
Attributes
- Section
CCC.AuditLog.CN07 Enforce MFA Delete on Audit Log Bucket
- Family Name
Availability
- Applicability
tlp-red
tlp-amber
tlp-green
- Recommendation
Enable MFA Delete (or equivalent multi-factor authentication for delete operations) on the audit log bucket.
- Family Description
Controls designed to protected the availability of Audit Log data.
- Sub Section Objective
Enable Multi-Factor Authentication (MFA) delete on the audit log bucket to provide greater protection against accidental or malicious deletion of audit data.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.AuditLog.CN08 Enable Object Lock On Audit Log Bucket10
CCC.AuditLog.CN08.AR01When an attempt is made to delete data before the object lock period expires, then the deletion MUST be denied.0
Attributes
- Section
CCC.AuditLog.CN08 Enable Object Lock On Audit Log Bucket
- Family Name
Availability
- Applicability
tlp-red
tlp-amber
- Recommendation
Configure object lock policy.
- Family Description
Controls designed to protected the availability of Audit Log data.
- Sub Section Objective
Ensure that object log is enabled globally on all objects with the bucket. The lock time MUST be configured to meet your organization, legal and compliance goals. Deletion attempts before the lock period MUST be denied.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.AuditLog.CN09 Restrict Field And Log Type Access11
CCC.AuditLog.CN09.AR01When restricted fields are accessed by unauthorized users, then those fields MUST remain masked.1
Attributes
- Section
CCC.AuditLog.CN09 Restrict Field And Log Type Access
- Family Name
Confidentiality
- Applicability
tlp-red
tlp-amber
- Recommendation
Review field level access controls on audit data.
- Family Description
Controls designed to protected the confidentiality of Audit Log data.
- Sub Section Objective
Configure access to audit logs to follow the principle of least privilege in particular where technically possible limit the log fields users have access to to prevent accidental exposure to sensitive information such as PII.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.AuditLog.CN10 Ensure Audit Bucket is Not Publicly Accessible26
CCC.AuditLog.CN10.AR01When audit log storage bucket's are created then, bucket's access control settings MUST explicitly deny public read and write access.3
Attributes
- Section
CCC.AuditLog.CN10 Ensure Audit Bucket is Not Publicly Accessible
- Family Name
Confidentiality
- Applicability
tlp-red
tlp-amber
tlp-green
- Recommendation
Configure bucket policies and access control lists (ACLs) to restrict public access. Regularly review bucket permissions to ensure no public access has been inadvertently granted.
- Family Description
Controls designed to protected the confidentiality of Audit Log data.
- Sub Section Objective
Ensure that audit log storage buckets are not publicly accessible to prevent unauthorized exposure of sensitive log data.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.AuditLog.CN10.AR02When the URL of a audit log storage bucket's object is accessed publicly then, it should be denied by bucket policy.3
Attributes
- Section
CCC.AuditLog.CN10 Ensure Audit Bucket is Not Publicly Accessible
- Family Name
Confidentiality
- Applicability
tlp-red
tlp-amber
tlp-green
- Recommendation
Configure bucket policies and access control lists (ACLs) to restrict public access. Regularly review bucket permissions to ensure no public access has been inadvertently granted.
- Family Description
Controls designed to protected the confidentiality of Audit Log data.
- Sub Section Objective
Ensure that audit log storage buckets are not publicly accessible to prevent unauthorized exposure of sensitive log data.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.Logging.CN01 Centralized and Comprehensive Log Aggregation26
CCC.Logging.CN01.AR01When a new cloud account is created, provider-level audit and network flow logging MUST be enabled by default and directed to the central sink.2
Attributes
- Section
CCC.Logging.CN01 Centralized and Comprehensive Log Aggregation
- Family Name
Data
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Family Description
Controls related to the confidentiality, integrity and availability of log data.
- Sub Section Objective
Ensure all operational and security logs from across the cloud environment, including applications, operating systems, network traffic, and cloud service activity, are captured automatically and streamed to a central, secure log management service.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.Logging.CN01.AR02When a new cloud compute resource is deployed, it MUST be configured to forward all relevant logs (e.g., OS, application, service logs) to the central log sink.4
Attributes
- Section
CCC.Logging.CN01 Centralized and Comprehensive Log Aggregation
- Family Name
Data
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Family Description
Controls related to the confidentiality, integrity and availability of log data.
- Sub Section Objective
Ensure all operational and security logs from across the cloud environment, including applications, operating systems, network traffic, and cloud service activity, are captured automatically and streamed to a central, secure log management service.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.Logging.CN02 Enforce Data Retention Policy for Logs26
CCC.Logging.CN02.AR01When a new log bucket or stream is created, its retention policy MUST be configured in accordance with organisation's data retention policy.3
Attributes
- Section
CCC.Logging.CN02 Enforce Data Retention Policy for Logs
- Family Name
Data
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Family Description
Controls related to the confidentiality, integrity and availability of log data.
- Sub Section Objective
Ensure that the retention period configured for logs aligns with the organization's data retention policy.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.Logging.CN02.AR02When a query is performed to retrieve log events older than the number of days defined in the organisation's data retention policy, it MUST return an empty result.3
Attributes
- Section
CCC.Logging.CN02 Enforce Data Retention Policy for Logs
- Family Name
Data
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Family Description
Controls related to the confidentiality, integrity and availability of log data.
- Sub Section Objective
Ensure that the retention period configured for logs aligns with the organization's data retention policy.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.Logging.CN03 Enable Object Lock On Log Bucket10
CCC.Logging.CN03.AR01When an attempt is made to modify or delete data before the object lock period expires, then the action MUST be denied.0
Attributes
- Section
CCC.Logging.CN03 Enable Object Lock On Log Bucket
- Family Name
Data
- Applicability
tlp-red
tlp-amber
- Recommendation
Configure object lock policy.
- Family Description
Controls related to the confidentiality, integrity and availability of log data.
- Sub Section Objective
Ensure log immutability by enabling Write Once, Read Many (WORM) protection using object lock on log storage buckets. This prevents logs from being modified or deleted during the defined retention period, supporting compliance and forensic integrity.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.Logging.CN04 Restrict Field And Log Type Access11
CCC.Logging.CN04.AR01When restricted fields are accessed by unauthorized users, then those fields MUST remain masked.1
Attributes
- Section
CCC.Logging.CN04 Restrict Field And Log Type Access
- Family Name
Identity and Access Management
- Applicability
tlp-red
tlp-amber
- Recommendation
Review field level access controls on log data.
- Family Description
Controls that restrict who can access and modify logs.
- Sub Section Objective
Configure access to logs to follow the principle of least privilege in particular where technically possible limit the log fields users have access to to prevent accidental exposure to sensitive information such as PII.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.Logging.CN05 Ensure Log Bucket is Not Publicly Accessible24
CCC.Logging.CN05.AR01When a log storage bucket is created, the bucket's access control settings MUST explicitly deny public read and write access.2
Attributes
- Section
CCC.Logging.CN05 Ensure Log Bucket is Not Publicly Accessible
- Family Name
Identity and Access Management
- Applicability
tlp-red
tlp-amber
tlp-green
- Recommendation
Configure bucket policies and access control lists (ACLs) to restrict public access. Regularly review bucket permissions to ensure no public access has been inadvertently granted.
- Family Description
Controls that restrict who can access and modify logs.
- Sub Section Objective
Ensure that log storage buckets are not publicly accessible to prevent unauthorized access to sensitive log data. In addition, logs should be replicated to another cloud region to enhance availability, durability, and support disaster recovery requirements.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.Logging.CN05.AR02When the URL of a log storage bucket's object is accessed publicly, the action MUST be denied by bucket policy.2
Attributes
- Section
CCC.Logging.CN05 Ensure Log Bucket is Not Publicly Accessible
- Family Name
Identity and Access Management
- Applicability
tlp-red
tlp-amber
tlp-green
- Recommendation
Configure bucket policies and access control lists (ACLs) to restrict public access. Regularly review bucket permissions to ensure no public access has been inadvertently granted.
- Family Description
Controls that restrict who can access and modify logs.
- Sub Section Objective
Ensure that log storage buckets are not publicly accessible to prevent unauthorized access to sensitive log data. In addition, logs should be replicated to another cloud region to enhance availability, durability, and support disaster recovery requirements.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.Logging.CN06 Detect and Alert on Potential Log Exfiltration10
CCC.Logging.CN06.AR01When a single principal executes an anomalously high number of log queries, an alert MUST be generated.0
Attributes
- Section
CCC.Logging.CN06 Detect and Alert on Potential Log Exfiltration
- Family Name
Logging and Monitoring
- Applicability
tlp-green
tlp-amber
tlp-red
- Family Description
Controls that collect, alert, and retain logging-related events.
- Sub Section Objective
Identify and alert on anomalous data access patterns that may indicate an attempt to exfiltrate log data.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.Logging.CN07 Detect and Alert on Log Service Tampering10
CCC.Logging.CN07.AR01When an audit log event is recorded that corresponds to a modification of the logging service configuration such as disabling a log trail, deleting a log sink, or altering a log forwarding rule, an alert MUST be generated.0
Attributes
- Section
CCC.Logging.CN07 Detect and Alert on Log Service Tampering
- Family Name
Logging and Monitoring
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Family Description
Controls that collect, alert, and retain logging-related events.
- Sub Section Objective
Alert when any component of the critical logging infrastructure is disabled, modified, or deleted, indicating a defense evasion attempt.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.Monitor.CN01 Rate Limiting on External Monitoring10
CCC.Monitor.CN01.AR01When an External Monitoring system exceeds the anticipated rate of monitoring checks then Rate Limiting MUST be applied and an Audit Alert MUST be generated.0
Attributes
- Section
CCC.Monitor.CN01 Rate Limiting on External Monitoring
- Family Name
Logging and Monitoring
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Family Description
Controls that collect, alert, and retain events from other monitoring services.
- Sub Section Objective
Prevent DoS attacks using External Monitoring tools.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.Monitor.CN02 Rate Limiting on Metric Generation10
CCC.Monitor.CN02.AR01When an Custom or User-Defined Metric starts to flood a collector, then a rate limit MUST be applied to reduce the network impact of traffic and an alert must triggered.0
Attributes
- Section
CCC.Monitor.CN02 Rate Limiting on Metric Generation
- Family Name
Logging and Monitoring
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Family Description
Controls that collect, alert, and retain events from other monitoring services.
- Sub Section Objective
Prevent Malicious Actor or misconfiguration from flooding services with metric data.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.Monitor.CN03 Access External Monitoring10
CCC.Monitor.CN03.AR01When external systems have approved access to internal systems not normally available for public access then they MUST be secured to prevent unauthorised access jumping through to the internal systems and only allow access to specific internal services.0
Attributes
- Section
CCC.Monitor.CN03 Access External Monitoring
- Family Name
Identity and Access Management
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Family Description
Controls designed to prevent unauthorised access to monitoring features.
- Sub Section Objective
Control access to Synthetic monitoring solutions using API keys or Certificate based authentication to ensure they don't become an attack path, preventing monitoring systems from forging network requests to gain access to internal systems.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.Monitor.CN04 Restrict access to Monitoring Dashboards10
CCC.Monitor.CN04.AR01When monitoring dashboards display degraded services which may become potential targets then the dashboard MUST be protected from unauthorised access.0
Attributes
- Section
CCC.Monitor.CN04 Restrict access to Monitoring Dashboards
- Family Name
Identity and Access Management
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Family Description
Controls designed to prevent unauthorised access to monitoring features.
- Sub Section Objective
Control access to Monitoring Dashboards and reports to ensure they don't highlight an attack path.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.Monitor.CN05 Restrict access to silence or acknowledge an alert10
CCC.Monitor.CN05.AR01When monitoring services have generated an alert, the service MUST ensure only authorised responders silence or acknowledge the alert.0
Attributes
- Section
CCC.Monitor.CN05 Restrict access to silence or acknowledge an alert
- Family Name
Identity and Access Management
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Family Description
Controls designed to prevent unauthorised access to monitoring features.
- Sub Section Objective
Ensure only a subset of users can silence or acknowledge alerts to prevent attackers hiding their activity.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.Monitor.CN06 Metrics pushed for authorised services only12
CCC.Monitor.CN06.AR01When systems push metrics or traces they MUST be authenticated for that particular type of metric or trace2
Attributes
- Section
CCC.Monitor.CN06 Metrics pushed for authorised services only
- Family Name
Identity and Access Management
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Family Description
Controls designed to prevent unauthorised access to monitoring features.
- Sub Section Objective
Use IAM to control which types of metrics or traces can be pushed by different system to avoid a compromised system pushing fabricated metrics about a different service
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.ObjStor.CN01 Prevent Requests to Buckets or Objects with Untrusted KMS Keys412
CCC.ObjStor.CN01.AR01When a request is made to read a bucket, the service MUST prevent any request using KMS keys not listed as trusted by the organization.3
Attributes
- Section
CCC.ObjStor.CN01 Prevent Requests to Buckets or Objects with Untrusted KMS Keys
- Family Name
Data
- Applicability
tlp-amber
tlp-red
- Family Description
The Data control family ensures the confidentiality, integrity, availability, and sovereignty of data across its lifecycle.
- Sub Section Objective
Prevent any requests to object storage buckets or objects using untrusted KMS keys to protect against unauthorized data encryption, or sensitive data decryption.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
CCC.ObjStor.CN01.AR02When a request is made to read an object, the service MUST prevent any request using KMS keys not listed as trusted by the organization.3
Attributes
- Section
CCC.ObjStor.CN01 Prevent Requests to Buckets or Objects with Untrusted KMS Keys
- Family Name
Data
- Applicability
tlp-amber
tlp-red
- Family Description
The Data control family ensures the confidentiality, integrity, availability, and sovereignty of data across its lifecycle.
- Sub Section Objective
Prevent any requests to object storage buckets or objects using untrusted KMS keys to protect against unauthorized data encryption, or sensitive data decryption.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
CCC.ObjStor.CN01.AR03When a request is made to write to a bucket, the service MUST prevent any request using KMS keys not listed as trusted by the organization.3
Attributes
- Section
CCC.ObjStor.CN01 Prevent Requests to Buckets or Objects with Untrusted KMS Keys
- Family Name
Data
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Family Description
The Data control family ensures the confidentiality, integrity, availability, and sovereignty of data across its lifecycle.
- Sub Section Objective
Prevent any requests to object storage buckets or objects using untrusted KMS keys to protect against unauthorized data encryption, or sensitive data decryption.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
CCC.ObjStor.CN01.AR04When a request is made to write to an object, the service MUST prevent any request using KMS keys not listed as trusted by the organization.3
Attributes
- Section
CCC.ObjStor.CN01 Prevent Requests to Buckets or Objects with Untrusted KMS Keys
- Family Name
Data
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Family Description
The Data control family ensures the confidentiality, integrity, availability, and sovereignty of data across its lifecycle.
- Sub Section Objective
Prevent any requests to object storage buckets or objects using untrusted KMS keys to protect against unauthorized data encryption, or sensitive data decryption.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
CCC.ObjStor.CN03 Prevent Bucket Deletion Through Irrevocable Bucket Retention Policy23
CCC.ObjStor.CN03.AR01When an object storage bucket deletion is attempted, the bucket MUST be fully recoverable for a set time-frame after deletion is requested.2
Attributes
- Section
CCC.ObjStor.CN03 Prevent Bucket Deletion Through Irrevocable Bucket Retention Policy
- Family Name
Data
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Family Description
The Data control family ensures the confidentiality, integrity, availability, and sovereignty of data across its lifecycle.
- Sub Section Objective
Ensure that object storage bucket is not deleted after creation, and that the preventative measure cannot be unset.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
CCC.ObjStor.CN03.AR02When an attempt is made to modify the retention policy for an object storage bucket, the service MUST prevent the policy from being modified.1
Attributes
- Section
CCC.ObjStor.CN03 Prevent Bucket Deletion Through Irrevocable Bucket Retention Policy
- Family Name
Data
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Family Description
The Data control family ensures the confidentiality, integrity, availability, and sovereignty of data across its lifecycle.
- Sub Section Objective
Ensure that object storage bucket is not deleted after creation, and that the preventative measure cannot be unset.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
CCC.ObjStor.CN04 Objects have an Effective Retention Policy by Default23
CCC.ObjStor.CN04.AR01When an object is uploaded to the object storage system, the object MUST automatically receive a default retention policy that prevents premature deletion or modification.2
Attributes
- Section
CCC.ObjStor.CN04 Objects have an Effective Retention Policy by Default
- Family Name
Data
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Family Description
The Data control family ensures the confidentiality, integrity, availability, and sovereignty of data across its lifecycle.
- Sub Section Objective
Ensure that all objects stored in the object storage system have a retention policy applied by default, preventing premature deletion or modification of objects.
- Section Threat Mappings
[object Object]
[object Object]
- Section Guideline Mappings
[object Object]
CCC.ObjStor.CN04.AR02When an attempt is made to delete or modify an object that is subject to an active retention policy, the service MUST prevent the action from being completed.1
Attributes
- Section
CCC.ObjStor.CN04 Objects have an Effective Retention Policy by Default
- Family Name
Data
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Family Description
The Data control family ensures the confidentiality, integrity, availability, and sovereignty of data across its lifecycle.
- Sub Section Objective
Ensure that all objects stored in the object storage system have a retention policy applied by default, preventing premature deletion or modification of objects.
- Section Threat Mappings
[object Object]
[object Object]
- Section Guideline Mappings
[object Object]
CCC.ObjStor.CN05 Versioning is Enabled for All Objects in the Bucket44
CCC.ObjStor.CN05.AR01When an object is uploaded to the object storage bucket, the object MUST be stored with a unique identifier.1
Attributes
- Section
CCC.ObjStor.CN05 Versioning is Enabled for All Objects in the Bucket
- Family Name
Data
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Family Description
The Data control family ensures the confidentiality, integrity, availability, and sovereignty of data across its lifecycle.
- Sub Section Objective
Ensure that versioning is enabled for all objects stored in the object storage bucket to enable recovery of previous versions of objects in case of loss or corruption.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
CCC.ObjStor.CN05.AR02When an object is modified, the service MUST assign a new unique identifier to the modified object to differentiate it from the previous version.1
Attributes
- Section
CCC.ObjStor.CN05 Versioning is Enabled for All Objects in the Bucket
- Family Name
Data
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Family Description
The Data control family ensures the confidentiality, integrity, availability, and sovereignty of data across its lifecycle.
- Sub Section Objective
Ensure that versioning is enabled for all objects stored in the object storage bucket to enable recovery of previous versions of objects in case of loss or corruption.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
CCC.ObjStor.CN05.AR03When an object is modified, the service MUST allow for recovery of previous versions of the object.1
Attributes
- Section
CCC.ObjStor.CN05 Versioning is Enabled for All Objects in the Bucket
- Family Name
Data
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Family Description
The Data control family ensures the confidentiality, integrity, availability, and sovereignty of data across its lifecycle.
- Sub Section Objective
Ensure that versioning is enabled for all objects stored in the object storage bucket to enable recovery of previous versions of objects in case of loss or corruption.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
CCC.ObjStor.CN05.AR04When an object is deleted, the service MUST retain other versions of the object to allow for recovery of previous versions.1
Attributes
- Section
CCC.ObjStor.CN05 Versioning is Enabled for All Objects in the Bucket
- Family Name
Data
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Family Description
The Data control family ensures the confidentiality, integrity, availability, and sovereignty of data across its lifecycle.
- Sub Section Objective
Ensure that versioning is enabled for all objects stored in the object storage bucket to enable recovery of previous versions of objects in case of loss or corruption.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
CCC.ObjStor.CN07 Multi-Factor Authentication Is Required for Object Deletion30
CCC.ObjStor.CN07.AR01The object storage service MUST support a configuration option that requires MFA to be successfully completed before any object deletion can be attempted, regardless of the request interface.0
Attributes
- Section
CCC.ObjStor.CN07 Multi-Factor Authentication Is Required for Object Deletion
- Family Name
Data
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Family Description
The Data control family ensures the confidentiality, integrity, availability, and sovereignty of data across its lifecycle.
- Sub Section Objective
Ensure that deletion of objects stored in the object storage system is protected by multi-factor authentication (MFA), reducing the risk of accidental, unauthorized, or compromised-credential–based data destruction.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
CCC.ObjStor.CN07.AR02When MFA deletion protection is enabled on a bucket or object namespace, the service MUST deny any deletion request from an identity that has not satisfied the MFA requirement at the time of the request.0
Attributes
- Section
CCC.ObjStor.CN07 Multi-Factor Authentication Is Required for Object Deletion
- Family Name
Data
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Family Description
The Data control family ensures the confidentiality, integrity, availability, and sovereignty of data across its lifecycle.
- Sub Section Objective
Ensure that deletion of objects stored in the object storage system is protected by multi-factor authentication (MFA), reducing the risk of accidental, unauthorized, or compromised-credential–based data destruction.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
CCC.ObjStor.CN07.AR03When an attempt is made to delete an object, the service's audit logs MUST clearly record each deletion attempt, including whether MFA was required and whether validation was met.0
Attributes
- Section
CCC.ObjStor.CN07 Multi-Factor Authentication Is Required for Object Deletion
- Family Name
Data
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Family Description
The Data control family ensures the confidentiality, integrity, availability, and sovereignty of data across its lifecycle.
- Sub Section Objective
Ensure that deletion of objects stored in the object storage system is protected by multi-factor authentication (MFA), reducing the risk of accidental, unauthorized, or compromised-credential–based data destruction.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
CCC.ObjStor.CN02 Enforce Uniform Bucket-level Access to Prevent Inconsistent Permissions24
CCC.ObjStor.CN02.AR01When a permission set is allowed for an object in a bucket, the service MUST allow the same permission set to access all objects in the same bucket.2
Attributes
- Section
CCC.ObjStor.CN02 Enforce Uniform Bucket-level Access to Prevent Inconsistent Permissions
- Family Name
Identity and Access Management
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Family Description
The Identity and Access Management control family ensures that only trusted and authenticated entities can access resources.
- Sub Section Objective
Ensure that uniform bucket-level access is enforced across all object storage buckets. This prevents the use of ad-hoc or inconsistent object-level permissions, ensuring centralized, consistent, and secure access management in accordance with the principle of least privilege.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
CCC.ObjStor.CN02.AR02When a permission set is denied for an object in a bucket, the service MUST deny the same permission set to access all objects in the same bucket.2
Attributes
- Section
CCC.ObjStor.CN02 Enforce Uniform Bucket-level Access to Prevent Inconsistent Permissions
- Family Name
Identity and Access Management
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Family Description
The Identity and Access Management control family ensures that only trusted and authenticated entities can access resources.
- Sub Section Objective
Ensure that uniform bucket-level access is enforced across all object storage buckets. This prevents the use of ad-hoc or inconsistent object-level permissions, ensuring centralized, consistent, and secure access management in accordance with the principle of least privilege.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
CCC.LB.CN01 Enforce and Detect Rate Limiting21
CCC.LB.CN01.AR01When a single client sends more than 2000 requests within any 5-minute sliding window, the load balancer MUST throttle all subsequent requests from that client for at least 60 seconds.0
Attributes
- Section
CCC.LB.CN01 Enforce and Detect Rate Limiting
- Family Name
Logging and Monitoring
- Applicability
tlp-green
tlp-amber
tlp-red
- Recommendation
Implement per-IP token-bucket limits with and verify via synthetic traffic tests.
- Family Description
Controls that detect anomalous traffic and record load-balancer activity.
- Sub Section Objective
Detect and throttle malicious or excessive requests to prevent downstream resource exhaustion and brute-force activity.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.LB.CN01.AR02When throttling is invoked, the load balancer MUST record the event in the access log within 5 minutes for alerting and trend analysis.1
Attributes
- Section
CCC.LB.CN01 Enforce and Detect Rate Limiting
- Family Name
Logging and Monitoring
- Applicability
tlp-green
tlp-amber
tlp-red
- Recommendation
Enable access logging and configure metric filters on HTTP 429 counts to trigger alerts.
- Family Description
Controls that detect anomalous traffic and record load-balancer activity.
- Sub Section Objective
Detect and throttle malicious or excessive requests to prevent downstream resource exhaustion and brute-force activity.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.LB.CN06 Secure Health-Check Telemetry11
CCC.LB.CN06.AR01When more than 10 percent of targets change from healthy to unhealthy within five minutes, an alert MUST be issued.1
Attributes
- Section
CCC.LB.CN06 Secure Health-Check Telemetry
- Family Name
Logging and Monitoring
- Applicability
tlp-green
tlp-amber
tlp-red
- Recommendation
Instrument metrics for health check results and target removal events. Configure monitoring alarms to alert on abnormal spikes in unhealthy targets.
- Family Description
Controls that detect anomalous traffic and record load-balancer activity.
- Sub Section Objective
Monitor health-check endpoints for tampering and alert on abnormal status changes.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.LB.CN04 Enforce Distribution Policies11
CCC.LB.CN04.AR01When routing weights change, the request MUST originate from an explicitly defined and trusted identity and MUST be logged.1
Attributes
- Section
CCC.LB.CN04 Enforce Distribution Policies
- Family Name
Identity and Access Management
- Applicability
tlp-green
tlp-amber
tlp-red
- Recommendation
Define a list of trusted principals allowed to modify routing configurations. Enforce via conditional access policies, and log changes using audit logging.
- Family Description
Controls that restrict who can change or query load-balancer resources.
- Sub Section Objective
Ensure traffic-splitting weights and algorithms are modified only by trusted identities.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.LB.CN05 Validate Session Affinity10
CCC.LB.CN05.AR01When stickiness is enabled, session cookies MUST expire within 30 minutes of inactivity.0
Attributes
- Section
CCC.LB.CN05 Validate Session Affinity
- Family Name
Identity and Access Management
- Applicability
tlp-green
tlp-amber
tlp-red
- Recommendation
Audit CCC.LB.CP15 parameters via configuration scans.
- Family Description
Controls that restrict who can change or query load-balancer resources.
- Sub Section Objective
Configure session persistence to minimise fixation and hijacking risks.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.LB.CN09 Restrict Management API Access11
CCC.LB.CN09.AR01When an API call originates outside the approved CIDR set, the request MUST be denied.1
Attributes
- Section
CCC.LB.CN09 Restrict Management API Access
- Family Name
Identity and Access Management
- Applicability
tlp-green
tlp-amber
tlp-red
- Recommendation
Combine VPC endpoints with IAM condition-key filters for protected APIs.
- Family Description
Controls that restrict who can change or query load-balancer resources.
- Sub Section Objective
Limit load-balancer API calls to authorised identities and trusted networks.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.LB.CN02 Auto-Scale Load Balancer Capacity10
CCC.LB.CN02.AR01When concurrent connections reach 80 percent of capacity, the autoscaling group MUST add at least one instance within five minutes.0
Attributes
- Section
CCC.LB.CN02 Auto-Scale Load Balancer Capacity
- Family Name
Data
- Applicability
tlp-green
tlp-amber
tlp-red
- Recommendation
Enable autoscaling policies.
- Family Description
Controls that preserve availability and confidentiality of traffic processed by the load balancer.
- Sub Section Objective
Expand load-balancer capacity to maintain availability during traffic spikes.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.LB.CN07 Scrub Sensitive Headers10
CCC.LB.CN07.AR01When responses pass through the load balancer, the "Server" header MUST be replaced with "lb".0
Attributes
- Section
CCC.LB.CN07 Scrub Sensitive Headers
- Family Name
Data
- Applicability
tlp-green
tlp-amber
tlp-red
- Recommendation
Configure header-transformation rules.
- Family Description
Controls that preserve availability and confidentiality of traffic processed by the load balancer.
- Sub Section Objective
Remove headers that disclose internal details or software versions from HTTP responses.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.LB.CN08 Automate Certificate Renewal11
CCC.LB.CN08.AR01When a certificate is within 30 days of expiry, automated renewal MUST complete and deploy a new certificate within 24 hours.1
Attributes
- Section
CCC.LB.CN08 Automate Certificate Renewal
- Family Name
Encryption
- Applicability
tlp-green
tlp-amber
tlp-red
- Recommendation
Use certificate-manager auto-renewal workflows.
- Family Description
Controls that ensure trustworthy TLS certificates and ciphers.
- Sub Section Objective
Maintain valid TLS certificates by automating renewal and deployment before expiry.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.VPC.CN01 Restrict Default Network Creation10
CCC.VPC.CN01.AR01When a subscription is created, the subscription MUST NOT contain default network resources.0
Attributes
- Section
CCC.VPC.CN01 Restrict Default Network Creation
- Family Name
Network Security
- Applicability
tlp-amber
tlp-red
- Family Description
TODO: Describe this control family
- Sub Section Objective
Restrict the automatic creation of default virtual networks and related resources during subscription initialization to avoid insecure default configurations and enforce custom network policies.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
[object Object]
[object Object]
CCC.VPC.CN02 Limit Resource Creation in Public Subnet10
CCC.VPC.CN02.AR01When a resource is created in a public subnet, that resource MUST NOT be assigned an external IP address by default.0
Attributes
- Section
CCC.VPC.CN02 Limit Resource Creation in Public Subnet
- Family Name
Network Security
- Applicability
tlp-red
- Family Description
TODO: Describe this control family
- Sub Section Objective
Restrict the creation of resources in the public subnet with direct access to the internet to minimize attack surfaces.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
[object Object]
[object Object]
CCC.VPC.CN03 Restrict VPC Peering to Authorized Accounts10
CCC.VPC.CN03.AR01When a VPC peering connection is requested, the service MUST prevent connections from VPCs that are not explicitly allowed.0
Attributes
- Section
CCC.VPC.CN03 Restrict VPC Peering to Authorized Accounts
- Family Name
Network Security
- Applicability
tlp-green
tlp-amber
tlp-red
- Family Description
TODO: Describe this control family
- Sub Section Objective
Ensure VPC peering connections are only established with explicitly authorized destinations to limit network exposure and enforce boundary controls.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
[object Object]
[object Object]
CCC.VPC.CN04 Enforce VPC Flow Logs on VPCs12
CCC.VPC.CN04.AR01When any network traffic goes to or from an interface in the VPC, the service MUST capture and log all relevant information.2
Attributes
- Section
CCC.VPC.CN04 Enforce VPC Flow Logs on VPCs
- Family Name
Network Security
- Applicability
tlp-amber
tlp-red
- Family Description
TODO: Describe this control family
- Sub Section Objective
Ensure VPCs are configured with flow logs enabled to capture traffic information.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
[object Object]
[object Object]
CCC.KeyMgmt.CN01 Alert on Key-version Changes12
CCC.KeyMgmt.CN01.AR01When a key version is scheduled for deletion or disabled, an alert MUST be generated within five minutes.2
Attributes
- Section
CCC.KeyMgmt.CN01 Alert on Key-version Changes
- Family Name
Logging and Monitoring
- Applicability
tlp-amber
tlp-red
- Recommendation
Use native event services (e.g., CloudWatch Events, Azure Monitor, Cloud Audit Logs) to route notifications to an incident-response channel.
- Family Description
Controls that collect, alert, and retain key-management events.
- Sub Section Objective
Generate near-real-time alerts when a KMS key version is disabled or scheduled for deletion, enabling rapid investigation and recovery.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.KeyMgmt.CN02 Limit Decrypt Permissions12
CCC.KeyMgmt.CN02.AR01When IAM roles and key policies are reviewed, Decrypt permission MUST be granted exclusively to documented authorised principals.2
Attributes
- Section
CCC.KeyMgmt.CN02 Limit Decrypt Permissions
- Family Name
Identity and Access Management
- Applicability
tlp-green
- Recommendation
Periodically audit policy documents via automated tooling and report any deviations.
- Family Description
Controls that enforce least-privilege use of KMS operations.
- Sub Section Objective
Restrict the Decrypt operation to authorised principals only, applying the principle of least privilege to protect sensitive data.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.KeyMgmt.CN03 Enforce Automatic Rotation11
CCC.KeyMgmt.CN03.AR01When rotation settings are examined, rotation MUST be enabled with an interval not exceeding 365 days.1
Attributes
- Section
CCC.KeyMgmt.CN03 Enforce Automatic Rotation
- Family Name
Key Lifecycle Management
- Applicability
tlp-green
- Recommendation
Use cloud-provider rotation features and verify via configuration scanning.
- Family Description
Controls that govern creation, rotation, import, and retirement of cryptographic keys.
- Sub Section Objective
Ensure symmetric keys rotate automatically within policy intervals to reduce exposure of key material.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.KeyMgmt.CN04 Validate Imported Keys10
CCC.KeyMgmt.CN04.AR01When a key import request is processed, the key MUST use an approved algorithm (RSA-2048+, EC-P256+) and originate from a certified HSM.0
Attributes
- Section
CCC.KeyMgmt.CN04 Validate Imported Keys
- Family Name
Key Lifecycle Management
- Applicability
tlp-green
- Recommendation
Implement an approval workflow that validates attestation data before import.
- Family Description
Controls that govern creation, rotation, import, and retirement of cryptographic keys.
- Sub Section Objective
Accept only externally generated keys that meet approved cryptographic strength and provenance requirements.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.SecMgmt.CN01 Enforce Automatic Secret Rotation12
CCC.SecMgmt.CN01.AR01Attempt to use an outdated version of a secret after its rotation period has passed and verify that access is denied.2
Attributes
- Section
CCC.SecMgmt.CN01 Enforce Automatic Secret Rotation
- Family Name
Data Protection
- Applicability
tlp-red
tlp-amber
- Family Description
TODO: Describe this control family
- Sub Section Objective
Ensure that secrets are automatically rotated on a defined schedule to reduce the risk of secret compromise and unauthorized access.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.SecMgmt.CN02 Enforce Secret Replication Policies10
CCC.SecMgmt.CN02.AR01Attempt to retrieve a secret from an unauthorized region and verify that access is denied.0
Attributes
- Section
CCC.SecMgmt.CN02 Enforce Secret Replication Policies
- Family Name
Data Protection
- Applicability
tlp-red
tlp-amber
- Family Description
TODO: Describe this control family
- Sub Section Objective
Ensure that secrets are replicated only to authorized locations as per organizational data residency and compliance requirements.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.DataWar.CN01 Enforce Use of Managed Views for Data Access10
CCC.DataWar.CN01.AR01Attempt to access underlying database tables directly without using managed views and verify that access is denied.0
Attributes
- Section
CCC.DataWar.CN01 Enforce Use of Managed Views for Data Access
- Family Name
Data
- Applicability
tlp-red
tlp-amber
- Family Description
TODO: Describe this control family
- Sub Section Objective
Ensure that data access is provided through managed views, restricting users from accessing underlying tables directly and enforcing consistent security policies.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.DataWar.CN02 Enforce Column-Level Security Policies10
CCC.DataWar.CN02.AR01Attempt to query sensitive columns without the necessary permissions and verify that access is denied or data is masked.0
Attributes
- Section
CCC.DataWar.CN02 Enforce Column-Level Security Policies
- Family Name
Data
- Applicability
tlp-red
tlp-amber
- Family Description
TODO: Describe this control family
- Sub Section Objective
Ensure that access to sensitive data columns is restricted based on user roles, preventing unauthorized access to sensitive information.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.DataWar.CN03 Enforce Row-Level Security Policies10
CCC.DataWar.CN03.AR01Attempt to query data rows that the user should not have access to and verify that access is denied or data is not returned.0
Attributes
- Section
CCC.DataWar.CN03 Enforce Row-Level Security Policies
- Family Name
Data
- Applicability
tlp-red
tlp-amber
- Family Description
TODO: Describe this control family
- Sub Section Objective
Ensure that access to data rows is restricted based on user roles or attributes, preventing unauthorized access to specific subsets of data.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.Vector.CN01 Validate Embeddings Before Indexing10
CCC.Vector.CN01.AR01When a vector embedding is submitted for indexing, the system MUST validate that it matches expected schema, dimension, and format profiles.0
Attributes
- Section
CCC.Vector.CN01 Validate Embeddings Before Indexing
- Family Name
Vector Indexing
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Family Description
Controls specific to the management and protection of vector embedding and index operations.
- Sub Section Objective
Ensure all incoming embeddings are structurally and statistically validated before indexing to prevent poisoning or corruption.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
CCC.Vector.CN02 Enforce Role-Based Index Lifecycle Management10
CCC.Vector.CN02.AR01When an index lifecycle event is triggered, the service MUST verify that the actor has explicit permissions for the operation type.0
Attributes
- Section
CCC.Vector.CN02 Enforce Role-Based Index Lifecycle Management
- Family Name
Vector Indexing
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Family Description
Controls specific to the management and protection of vector embedding and index operations.
- Sub Section Objective
Restrict index lifecycle operations (create, delete, rollback) to privileged identities using fine-grained access controls.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
CCC.Vector.CN03 Enforce Metadata-Level Access Controls10
CCC.Vector.CN03.AR01When a metadata filter is applied to a query, the service MUST verify the requester is authorized to access that field.0
Attributes
- Section
CCC.Vector.CN03 Enforce Metadata-Level Access Controls
- Family Name
Vector Indexing
- Applicability
tlp-amber
tlp-red
- Family Description
Controls specific to the management and protection of vector embedding and index operations.
- Sub Section Objective
Apply access control policies to metadata fields used in filtering to prevent unauthorized exposure or inference.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
CCC.Vector.CN04 Enforce Ingestion Quotas and Throttling10
CCC.Vector.CN04.AR01When ingestion exceeds pre-defined thresholds, the service MUST throttle or reject excess vector write operations.0
Attributes
- Section
CCC.Vector.CN04 Enforce Ingestion Quotas and Throttling
- Family Name
Vector Indexing
- Applicability
tlp-green
tlp-amber
tlp-red
- Family Description
Controls specific to the management and protection of vector embedding and index operations.
- Sub Section Objective
Prevent ingestion-based DoS or index pollution by rate-limiting vector submissions and enforcing quotas.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
CCC.Vector.CN05 Enforce Index Versioning with Rollback Protection10
CCC.Vector.CN05.AR01When a rollback is attempted, the system MUST log the action and verify rollback authorization.0
Attributes
- Section
CCC.Vector.CN05 Enforce Index Versioning with Rollback Protection
- Family Name
Vector Indexing
- Applicability
tlp-amber
tlp-red
- Family Description
Controls specific to the management and protection of vector embedding and index operations.
- Sub Section Objective
Ensure vector indexes are versioned and that rollback operations are authorized and auditable.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
CCC.Vector.CN06 Enforce Dimensional and Format Constraints10
CCC.Vector.CN06.AR01When an embedding is submitted, the service MUST validate that its format and dimensionality match allowed profiles.0
Attributes
- Section
CCC.Vector.CN06 Enforce Dimensional and Format Constraints
- Family Name
Vector Indexing
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Family Description
Controls specific to the management and protection of vector embedding and index operations.
- Sub Section Objective
Reject embeddings that do not conform to expected model specifications (dimensions, format, etc).
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
CCC.Vector.CN07 Support Explicit ANN vs. Exact Search Configuration10
CCC.Vector.CN07.AR01When a search request is issued, clients MUST be allowed to declare their requirement for exact vs approximate results.0
Attributes
- Section
CCC.Vector.CN07 Support Explicit ANN vs. Exact Search Configuration
- Family Name
Vector Indexing
- Applicability
tlp-amber
tlp-red
- Family Description
Controls specific to the management and protection of vector embedding and index operations.
- Sub Section Objective
Provide clients with the option to enforce exact-match (non-ANN) search where search fidelity is critical.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
CCC.RDMS.CN01 Password Management10
CCC.RDMS.CN01.AR02When an attempt is made to authenticate to the database using known default credentials, the authentication attempt must fail and no access should be granted.0
Attributes
- Section
CCC.RDMS.CN01 Password Management
- Family Name
Identity and Access Management
- Applicability
tlp-red
tlp-amber
- Family Description
TODO: Describe this control family
- Sub Section Objective
Ensure default vendor-supplied DB administrator credentials are replaced with strong, unique passwords and that these credentials are properly managed using a secure password or secrets management solution.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.RDMS.CN02 Account Lockout and Rate-Limiting10
CCC.RDMS.CN02.AR01When repeated failed login attempts are made in a short timeframe, the account must be locked out or rate-limited to prevent further login attempts.0
Attributes
- Section
CCC.RDMS.CN02 Account Lockout and Rate-Limiting
- Family Name
Identity and Access Management
- Applicability
tlp-red
tlp-amber
- Family Description
TODO: Describe this control family
- Sub Section Objective
Ensure the database enforces lockouts or rate-limiting after a specified number of failed authentication attempts. This prevents brute force or password-guessing attacks from succeeding.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.RDMS.CN04 Access Control for Backup and Restore Operations10
CCC.RDMS.CN04.AR01When there is an attempt to perform a backup or restore, then the attempt must fail with an access denied message if credentials or roles that are not explicitly authorized for backup/restore functions.0
Attributes
- Section
CCC.RDMS.CN04 Access Control for Backup and Restore Operations
- Family Name
Identity and Access Management
- Applicability
tlp-red
tlp-amber
- Family Description
TODO: Describe this control family
- Sub Section Objective
Restrict who can initiate, manage, and validate database backup or restore operations through strict role-based or least-privilege access. Prevents accidental or malicious restorations, protecting data integrity and availability.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.RDMS.CN05 Restrict Snapshot Sharing to Authorized Accounts10
CCC.RDMS.CN05.AR01When an attempt is made to share a snapshot with an unauthorized account, the sharing request must be denied.0
Attributes
- Section
CCC.RDMS.CN05 Restrict Snapshot Sharing to Authorized Accounts
- Family Name
Identity and Access Management
- Applicability
tlp-red
tlp-amber
- Family Description
TODO: Describe this control family
- Sub Section Objective
Ensure database snapshots can only be shared with explicitly authorized accounts, thereby minimizing the risk of data exposure or exfiltration.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.RDMS.CN03 Enforce and Monitor Automated Backups10
CCC.RDMS.CN03.AR01When backups are disabled, paused, or fail to run as scheduled, an alert must be triggered and logged.0
Attributes
- Section
CCC.RDMS.CN03 Enforce and Monitor Automated Backups
- Family Name
Data
- Applicability
tlp-red
tlp-amber
- Family Description
TODO: Describe this control family
- Sub Section Objective
Ensure database backups are automatically scheduled, actively monitored, and promptly reported if any disruptions occur. This helps maintain data integrity, facilitates disaster recovery, and supports business continuity when a system failure or breach occurs.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.Build.CN01 Restrict Allowed Build Agents10
CCC.Build.CN01.AR01Attempt to initiate a build using an unauthorized build agent and verify that the build is rejected.0
Attributes
- Section
CCC.Build.CN01 Restrict Allowed Build Agents
- Family Name
Access Control
- Applicability
tlp-red
tlp-amber
- Family Description
TODO: Describe this control family
- Sub Section Objective
Ensure that builds are executed only on authorized build agents to maintain control over the build environment and prevent unauthorized code execution.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.Build.CN02 Restrict Allowed External Services for Build Triggers10
CCC.Build.CN02.AR01Attempt to trigger a build from an unauthorized external service or repository and verify that the build does not start.0
Attributes
- Section
CCC.Build.CN02 Restrict Allowed External Services for Build Triggers
- Family Name
Access Control
- Applicability
tlp-red
tlp-amber
- Family Description
TODO: Describe this control family
- Sub Section Objective
Ensure that builds can only be triggered by authorized external services or repositories to prevent unauthorized code execution or tampering.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.Build.CN03 Deny External Network Access for Build Environments10
CCC.Build.CN03.AR01Attempt to access the build environment from an external network and verify that access is denied.0
Attributes
- Section
CCC.Build.CN03 Deny External Network Access for Build Environments
- Family Name
Network Security
- Applicability
tlp-red
tlp-amber
- Family Description
TODO: Describe this control family
- Sub Section Objective
Ensure that build environments do not have external network access to prevent unauthorized external access and data exfiltration.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.CntrReg.CN01 Implement Vulnerability Scanning for Artifacts12
CCC.CntrReg.CN01.AR01Attempt to push an artifact with known vulnerabilities to the registry and observe if it is flagged or rejected by the vulnerability scanning process.2
Attributes
- Section
CCC.CntrReg.CN01 Implement Vulnerability Scanning for Artifacts
- Family Name
Risk Management
- Applicability
tlp-red
tlp-amber
- Family Description
TODO: Describe this control family
- Sub Section Objective
Ensure that container images and artifacts stored in the container registry are scanned for vulnerabilities to identify and remediate security issues before deployment.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.CntrReg.CN02 Implement Cleanup Policies for Artifacts10
CCC.CntrReg.CN02.AR01Confirm that artifacts older than the specified retention period are automatically deleted from the registry.0
Attributes
- Section
CCC.CntrReg.CN02 Implement Cleanup Policies for Artifacts
- Family Name
Data Management
- Applicability
tlp-red
tlp-amber
- Family Description
TODO: Describe this control family
- Sub Section Objective
Ensure that unused or outdated artifacts are cleaned up according to defined policies to manage storage effectively and reduce security risks associated with outdated versions.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.IAM.CN01 Restrict IAM User Credentials Creation24
CCC.IAM.CN01.AR01When an identity policy for a non-administrative principal is evaluated, it MUST NOT grant permissions for creating credentials or generating temporary session tokens.2
Attributes
- Section
CCC.IAM.CN01 Restrict IAM User Credentials Creation
- Family Name
Identity and Access Management
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Family Description
Controls that restrict who can access and modify IAM resources.
- Sub Section Objective
Prevent 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.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.IAM.CN01.AR02When a non-administrative principal attempts to create new credentials or a temporary session token, the service MUST deny the action.2
Attributes
- Section
CCC.IAM.CN01 Restrict IAM User Credentials Creation
- Family Name
Identity and Access Management
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Family Description
Controls that restrict who can access and modify IAM resources.
- Sub Section Objective
Prevent 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.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.IAM.CN02 Restrict IAM Policies Modification26
CCC.IAM.CN02.AR01When an identity policy for a non-administrative principal is evaluated, it MUST NOT grant permissions for creating, updating, or attaching policies.3
Attributes
- Section
CCC.IAM.CN02 Restrict IAM Policies Modification
- Family Name
Identity and Access Management
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Family Description
Controls that restrict who can access and modify IAM resources.
- Sub Section Objective
Ensure that only designated administrative accounts have the ability to create, modify, or attach policies that define permissions for other identities.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.IAM.CN02.AR02When a non-administrative principal attempts to create, update, or attach policies, the service MUST deny the action.3
Attributes
- Section
CCC.IAM.CN02 Restrict IAM Policies Modification
- Family Name
Identity and Access Management
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Family Description
Controls that restrict who can access and modify IAM resources.
- Sub Section Objective
Ensure that only designated administrative accounts have the ability to create, modify, or attach policies that define permissions for other identities.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.IAM.CN03 Restrict Role Assumption / Delegation22
CCC.IAM.CN03.AR01When a policy is created or updated that grants a principal permission to assume a role or impersonate a service identity, the principal MUST NOT contain a wildcard or be public/anonymous.1
Attributes
- Section
CCC.IAM.CN03 Restrict Role Assumption / Delegation
- Family Name
Identity and Access Management
- Applicability
tlp-green
tlp-amber
tlp-red
- Family Description
Controls that restrict who can access and modify IAM resources.
- Sub Section Objective
Limit which principals can assume a role or impersonate a service identity to only those required. This prevents unintended cross-account or public access by securing the "who can act as this identity" boundary.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.IAM.CN03.AR02When an external or unauthenticated principal tries to assume a role or impersonate a service identity, the service MUST deny the action.1
Attributes
- Section
CCC.IAM.CN03 Restrict Role Assumption / Delegation
- Family Name
Identity and Access Management
- Applicability
tlp-green
tlp-amber
tlp-red
- Family Description
Controls that restrict who can access and modify IAM resources.
- Sub Section Objective
Limit which principals can assume a role or impersonate a service identity to only those required. This prevents unintended cross-account or public access by securing the "who can act as this identity" boundary.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.IAM.CN04 Restrict Wildcard Usage in IAM Policies10
CCC.IAM.CN04.AR01When an IAM policy is created or updated, it MUST NOT contain allow statements with wildcard permissions, unless the statement is restricted by a condition.0
Attributes
- Section
CCC.IAM.CN04 Restrict Wildcard Usage in IAM Policies
- Family Name
Identity and Access Management
- Applicability
tlp-green
tlp-amber
tlp-red
- Family Description
Controls that restrict who can access and modify IAM resources.
- Sub Section Objective
Limit the use of wildcard permissions in IAM policies to prevent overly broad access from being granted by default.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.IAM.CN05 Strong Password Policies for IAM Users10
CCC.IAM.CN05.AR01When a new cloud account is provisioned, a password policy MUST be configured for IAM users following the minimum PCI DSS v4.0.1 configurations.0
Attributes
- Section
CCC.IAM.CN05 Strong Password Policies for IAM Users
- Family Name
Identity and Access Management
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Recommendation
When a new cloud account is provisioned, a password policy must be configured for all IAM users to align with the minimum requirements defined in PCI DSS v4.0.1. This includes, at a minimum: strength: 0 # Not yet specified - reference-id: A password length of at least 12 characters. strength: 0 # Not yet specified - reference-id: A mix of upper- and lower-case letters, numbers, and special characters. strength: 0 # Not yet specified - reference-id: Prevention of the use of previously used passwords (password history). strength: 0 # Not yet specified - reference-id: Password expiration at a defined interval (e.g., every 90 days). strength: 0 # Not yet specified - reference-id: Account lockout after a defined number of failed login attempts.
- Family Description
Controls that restrict who can access and modify IAM resources.
- Sub Section Objective
Ensure that the password policies for IAM users have strong configurations.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
[object Object]
CCC.IAM.CN06 Maximum Age for Long-Term Static Credentials10
CCC.IAM.CN06.AR01When a static credential such as an access key has existed for 90 days or more, it MUST be rotated.0
Attributes
- Section
CCC.IAM.CN06 Maximum Age for Long-Term Static Credentials
- Family Name
Identity Provisioning and Lifecycle
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Recommendation
When a static credential such as an access key has existed for 90 days or more, it must be automatically rotated to reduce the risk of compromise due to long-term exposure. Organizations should implement automated checks to identify aging credentials and enforce rotation policies. Additionally, access key usage should be regularly monitored, and credentials that are no longer in use should be deactivated or deleted promptly. Where possible, prefer temporary, short-lived credentials over long-lived static ones to further minimize risk.
- Family Description
Controls related to the provisioning and lifecycle of IAM identities.
- Sub Section Objective
Ensure that long-lived static credentials like access keys are programmatically rotated within a defined time period to limit the window of opportunity if compromised.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.IAM.CN07 Automate Identity De-provisioning10
CCC.IAM.CN07.AR01When a user account is disabled or deleted in the organization's IdP, the corresponding cloud identity and its access policies MUST be disabled or deleted within 24 hours.0
Attributes
- Section
CCC.IAM.CN07 Automate Identity De-provisioning
- Family Name
Identity Provisioning and Lifecycle
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Family Description
Controls related to the provisioning and lifecycle of IAM identities.
- Sub Section Objective
Ensure that when an identity is terminated in the central Identity Provider (IdP), ts corresponding access to cloud resources is revoked automatically.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.IAM.CN08 Maximum Age for Unused Credentials10
CCC.IAM.CN08.AR01When an IAM user has credentials, such as passwords or access keys, that have not been used for 90 days or more, the unused credentials MUST be removed or deactivated.0
Attributes
- Section
CCC.IAM.CN08 Maximum Age for Unused Credentials
- Family Name
Identity Provisioning and Lifecycle
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Recommendation
IAM user credentials (such as passwords or access keys) that have not been used for 90 days or more must be automatically removed or deactivated.
- Family Description
Controls related to the provisioning and lifecycle of IAM identities.
- Sub Section Objective
Ensure that unused IAM credentals are removed to reduce exposure in the event of potential compromise.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.IAM.CN09 Enforce Federated Single Sign-On (SSO) for Human Users11
CCC.IAM.CN09.AR01When a human user accesses the cloud environment, they MUST authenticate through the organization's federated IdP via a standard protocol (e.g., SAML, OIDC).1
Attributes
- Section
CCC.IAM.CN09 Enforce Federated Single Sign-On (SSO) for Human Users
- Family Name
Identity Provisioning and Lifecycle
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Family Description
Controls related to the provisioning and lifecycle of IAM identities.
- Sub Section Objective
Ensure 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.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.IAM.CN10 Alert On Anomalous Behaviour23
CCC.IAM.CN10.AR01When suspicious API requests are detected, real time alerts MUST be generated to notify security personnel.1
Attributes
- Section
CCC.IAM.CN10 Alert On Anomalous Behaviour
- Family Name
Logging and Monitoring
- Applicability
tlp-red
- Family Description
Controls that collect, alert, and retain IAM-related events.
- Sub Section Objective
Ensure 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 credentals may be compromised, as well as for password brute-force attempts and account lockouts.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.IAM.CN10.AR02When suspicious API requests are detected, the associated events MUST be logged, including the source details, time, and nature of the activity.2
Attributes
- Section
CCC.IAM.CN10 Alert On Anomalous Behaviour
- Family Name
Logging and Monitoring
- Applicability
tlp-green
tlp-amber
tlp-red
- Family Description
Controls that collect, alert, and retain IAM-related events.
- Sub Section Objective
Ensure 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 credentals may be compromised, as well as for password brute-force attempts and account lockouts.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.IAM.CN11 Enable Continuous IAM Access and Usage Analysis10
CCC.IAM.CN11.AR01When a cloud account or organization is provisioned, the native automated access and usage analysis services MUST be enabled to continuously monitor for external or public access to resources, and unused access.0
Attributes
- Section
CCC.IAM.CN11 Enable Continuous IAM Access and Usage Analysis
- Family Name
Logging and Monitoring
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Family Description
Controls that collect, alert, and retain IAM-related events.
- Sub Section Objective
Enable and configure the cloud provider's native access and usage analysis services to continuously monitor for external access paths and internal unused access.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.GenAI.CN01 Model Input Filtering and Sanitisation20
CCC.GenAI.CN01.AR01Untrusted input such as user queries, RAG data or tool output MUST be validated before it is passed to a GenAI model.0
Attributes
- Section
CCC.GenAI.CN01 Model Input Filtering and Sanitisation
- Family Name
Data
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Family Description
The Data control family ensures the confidentiality, integrity, availability, and sovereignty of data across its lifecycle. These controls govern how data is transmitted, stored, replicated, and protected from unauthorized access, tampering, or exposure beyond defined trust perimeters.
- Sub Section Objective
Inspect and validate input before it is passed to a GenAI model in order to filter or sanitise adversarial queries and prevent sensitive data leakage.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
[object Object]
CCC.GenAI.CN01.AR02If malicious patterns such as prompt injection or sensitive data are detected during input validation, the input MUST be blocked or sanitised.0
Attributes
- Section
CCC.GenAI.CN01 Model Input Filtering and Sanitisation
- Family Name
Data
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Family Description
The Data control family ensures the confidentiality, integrity, availability, and sovereignty of data across its lifecycle. These controls govern how data is transmitted, stored, replicated, and protected from unauthorized access, tampering, or exposure beyond defined trust perimeters.
- Sub Section Objective
Inspect and validate input before it is passed to a GenAI model in order to filter or sanitise adversarial queries and prevent sensitive data leakage.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
[object Object]
CCC.GenAI.CN02 Model Output Filtering and Sanitisation20
CCC.GenAI.CN02.AR01GenAI model output MUST be validated for format conformance, malicious patterns, sensitive data and inapropriate content before being passed to users, application or plugins.0
Attributes
- Section
CCC.GenAI.CN02 Model Output Filtering and Sanitisation
- Family Name
Data
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Family Description
The Data control family ensures the confidentiality, integrity, availability, and sovereignty of data across its lifecycle. These controls govern how data is transmitted, stored, replicated, and protected from unauthorized access, tampering, or exposure beyond defined trust perimeters.
- Sub Section Objective
Inspect and validate GenAI model output before passing it to users, applications or plugins in order to filter or sanitise insecure or unreliable output and prevent sensitive data leakage.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
[object Object]
CCC.GenAI.CN02.AR02In the event of policy violations, the AI-generated content MUST be redacted, encoded or rejected.0
Attributes
- Section
CCC.GenAI.CN02 Model Output Filtering and Sanitisation
- Family Name
Data
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Family Description
The Data control family ensures the confidentiality, integrity, availability, and sovereignty of data across its lifecycle. These controls govern how data is transmitted, stored, replicated, and protected from unauthorized access, tampering, or exposure beyond defined trust perimeters.
- Sub Section Objective
Inspect and validate GenAI model output before passing it to users, applications or plugins in order to filter or sanitise insecure or unreliable output and prevent sensitive data leakage.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
[object Object]
CCC.GenAI.CN03 Data Provenance and Source Vetting20
CCC.GenAI.CN03.AR01When data is designated for model training or RAG ingestion, then its source MUST be explicitly approved and its provenance documented.0
Attributes
- Section
CCC.GenAI.CN03 Data Provenance and Source Vetting
- Family Name
Data
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Family Description
The Data control family ensures the confidentiality, integrity, availability, and sovereignty of data across its lifecycle. These controls govern how data is transmitted, stored, replicated, and protected from unauthorized access, tampering, or exposure beyond defined trust perimeters.
- Sub Section Objective
Ensure that all data for training, fine-tuning or RAG comes from trusted, approved sources and is authorised for the intended purposes in order to prevent the initial introduction of malicious content or leaked sensitive data.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
[object Object]
CCC.GenAI.CN03.AR02Data from unvetted sources MUST NOT be used in production systems.0
Attributes
- Section
CCC.GenAI.CN03 Data Provenance and Source Vetting
- Family Name
Data
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Family Description
The Data control family ensures the confidentiality, integrity, availability, and sovereignty of data across its lifecycle. These controls govern how data is transmitted, stored, replicated, and protected from unauthorized access, tampering, or exposure beyond defined trust perimeters.
- Sub Section Objective
Ensure that all data for training, fine-tuning or RAG comes from trusted, approved sources and is authorised for the intended purposes in order to prevent the initial introduction of malicious content or leaked sensitive data.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
[object Object]
CCC.GenAI.CN04 Sanitisation of Ingested Data20
CCC.GenAI.CN04.AR01When data is ingested for training, fine-tuning or conversion to vector embeddings, it MUST be validated for sensitive information or malicious content.0
Attributes
- Section
CCC.GenAI.CN04 Sanitisation of Ingested Data
- Family Name
Data
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Family Description
The Data control family ensures the confidentiality, integrity, availability, and sovereignty of data across its lifecycle. These controls govern how data is transmitted, stored, replicated, and protected from unauthorized access, tampering, or exposure beyond defined trust perimeters.
- Sub Section Objective
Validate and sanitise all data ingested by GenAI systems from extenal sources or internal knowledge bases, whether for training, conversion to vector embeddings, or real-time retireval, in order to remove or redact poisoned or sensitive data before further processing.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
[object Object]
CCC.GenAI.CN04.AR02If sensitive data or malicious content is detected, it must be rejected, redacted or flagged for manual review.0
Attributes
- Section
CCC.GenAI.CN04 Sanitisation of Ingested Data
- Family Name
Data
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Family Description
The Data control family ensures the confidentiality, integrity, availability, and sovereignty of data across its lifecycle. These controls govern how data is transmitted, stored, replicated, and protected from unauthorized access, tampering, or exposure beyond defined trust perimeters.
- Sub Section Objective
Validate and sanitise all data ingested by GenAI systems from extenal sources or internal knowledge bases, whether for training, conversion to vector embeddings, or real-time retireval, in order to remove or redact poisoned or sensitive data before further processing.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
[object Object]
CCC.GenAI.CN05 Citations and Source Traceability10
CCC.GenAI.CN05.AR01When a RAG-enabled system generates a response containing information retrieved from its knowledge base, then the response MUST include a verifiable citation that links back to the specific source document.0
Attributes
- Section
CCC.GenAI.CN05 Citations and Source Traceability
- Family Name
Data
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Family Description
The Data control family ensures the confidentiality, integrity, availability, and sovereignty of data across its lifecycle. These controls govern how data is transmitted, stored, replicated, and protected from unauthorized access, tampering, or exposure beyond defined trust perimeters.
- Sub Section Objective
Require the GenAI system to provide citations or direct links back to the source documents used to generate a response, in to enhance the transparency, trustworthiness, and verifiability of AI-generated content.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
CCC.GenAI.CN06 Least Privilege for Plugins10
CCC.GenAI.CN06.AR01When an LLM invokes an external tool (e.g., an API, a plugin), then the tool MUST operate with the least privileges required for performing its intended functionality.0
Attributes
- Section
CCC.GenAI.CN06 Least Privilege for Plugins
- Family Name
Identity and Access Management
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Family Description
The Identity and Access Management control family ensures that only trusted and authenticated entities can access resources. These controls establish strong authentication, enforce multi-factor verification, and restrict access to approved sources to prevent unauthorized use or data exfiltration.
- Sub Section Objective
Restricts the permissions of any external tools the GenAI system can call to limit the potential damage if an agent is coerced to perform unintended actions or vulnerabilities in the tools are exploited.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
CCC.GenAI.CN07 Model Version Pinning10
CCC.GenAI.CN07.AR01When an application makes an API call to a foundational model in a production environment, then it MUST specify an explicit version identifier.0
Attributes
- Section
CCC.GenAI.CN07 Model Version Pinning
- Family Name
Configuration Management
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Family Description
The Configuration Management control family involves establishing, maintaining and monitoring the configuration of the service and related applications and infrastructure to ensure consistency, secure defaults and compliance.
- Sub Section Objective
Mandate that applications are locked ("pinned") to a specific, tested version of a foundational model to prevent unexpected behaviour changes introduced by provider-side updates.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
CCC.GenAI.CN08 Quality Control and Red Teaming20
CCC.GenAI.CN08.AR01When a new AI model is considered for production deployment, it MUST undergo a formal red teaming and quality assurance review.0
Attributes
- Section
CCC.GenAI.CN08 Quality Control and Red Teaming
- Family Name
Model Assurance and Evaluation
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Family Description
The Model Assurance and Evaluation control family encompasses the proactiveand continuous processes of testing and validating the AI model's behavior to ensure it aligns with safety, ethical, and quality standards.
- Sub Section Objective
Establish a formal program for quality evaluation and adversarial testing (red teaming) to ensure GenAI system meet all business, quality, security and compliance requirements before getting deployed into production environments.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
[object Object]
CCC.GenAI.CN08.AR02If model quality review or red teaming identifies an issue that exceeds the organization's risk tolerance, the model MUST NOT be deployed until the issue is remediated.0
Attributes
- Section
CCC.GenAI.CN08 Quality Control and Red Teaming
- Family Name
Model Assurance and Evaluation
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Family Description
The Model Assurance and Evaluation control family encompasses the proactiveand continuous processes of testing and validating the AI model's behavior to ensure it aligns with safety, ethical, and quality standards.
- Sub Section Objective
Establish a formal program for quality evaluation and adversarial testing (red teaming) to ensure GenAI system meet all business, quality, security and compliance requirements before getting deployed into production environments.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
[object Object]
CCC.MLDE.CN01 Define Access Mode for ML Development Environments10
CCC.MLDE.CN01.AR01Verify that only authorized users can access MLDE resources, and that access modes are properly defined and enforced.0
Attributes
- Section
CCC.MLDE.CN01 Define Access Mode for ML Development Environments
- Family Name
Identity and Access Management
- Applicability
tlp-red
tlp-amber
tlp-green
tlp-clear
- Family Description
TODO: Describe this control family
- Sub Section Objective
Ensure that access to Machine Learning Development Environment (MLDE) resources is strictly defined and controlled. Only authorized users with appropriate permissions can access these environments, mitigating the risk of unauthorized access, data leakage, or service disruption.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
[object Object]
[object Object]
CCC.MLDE.CN03 Disable Root Access on MLDE Instances20
CCC.MLDE.CN03.AR01Verify that root access is disabled on MLDE instances containing sensitive data.0
Attributes
- Section
CCC.MLDE.CN03 Disable Root Access on MLDE Instances
- Family Name
Identity and Access Management
- Applicability
tlp-red
- Family Description
TODO: Describe this control family
- Sub Section Objective
Prevent users from obtaining root access on MLDE instances to reduce the risk of unauthorized system modifications and potential security breaches.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
[object Object]
[object Object]
CCC.MLDE.CN03.AR02For MLDE instances without sensitive data, ensure that root access is only enabled when necessary and properly authorized.0
Attributes
- Section
CCC.MLDE.CN03 Disable Root Access on MLDE Instances
- Family Name
Identity and Access Management
- Applicability
tlp-red
tlp-amber
tlp-green
tlp-clear
- Family Description
TODO: Describe this control family
- Sub Section Objective
Prevent users from obtaining root access on MLDE instances to reduce the risk of unauthorized system modifications and potential security breaches.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
[object Object]
[object Object]
CCC.MLDE.CN04 Disable Terminal Access on MLDE Instances20
CCC.MLDE.CN04.AR01Verify that terminal access is disabled on MLDE instances containing sensitive data.0
Attributes
- Section
CCC.MLDE.CN04 Disable Terminal Access on MLDE Instances
- Family Name
Identity and Access Management
- Applicability
tlp-red
- Family Description
TODO: Describe this control family
- Sub Section Objective
Prevent users from accessing the terminal on MLDE instances to limit the risk of unauthorized commands and potential system compromise.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
[object Object]
[object Object]
CCC.MLDE.CN04.AR02For MLDE instances without sensitive data, ensure that terminal access is only enabled when necessary and properly authorized.0
Attributes
- Section
CCC.MLDE.CN04 Disable Terminal Access on MLDE Instances
- Family Name
Identity and Access Management
- Applicability
tlp-red
tlp-amber
tlp-green
tlp-clear
- Family Description
TODO: Describe this control family
- Sub Section Objective
Prevent users from accessing the terminal on MLDE instances to limit the risk of unauthorized commands and potential system compromise.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
[object Object]
[object Object]
CCC.MLDE.CN02 Disable File Downloads on MLDE Instances20
CCC.MLDE.CN02.AR01Confirm that file download functionality is disabled on MLDE instances containing sensitive data.0
Attributes
- Section
CCC.MLDE.CN02 Disable File Downloads on MLDE Instances
- Family Name
Data Protection
- Applicability
tlp-red
- Family Description
TODO: Describe this control family
- Sub Section Objective
Prevent unauthorized file downloads from MLDE instances to protect sensitive data from being exfiltrated.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
[object Object]
[object Object]
CCC.MLDE.CN02.AR02For MLDE instances without sensitive data, ensure that file downloads are monitored and logged.0
Attributes
- Section
CCC.MLDE.CN02 Disable File Downloads on MLDE Instances
- Family Name
Data Protection
- Applicability
tlp-red
tlp-amber
tlp-green
tlp-clear
- Family Description
TODO: Describe this control family
- Sub Section Objective
Prevent unauthorized file downloads from MLDE instances to protect sensitive data from being exfiltrated.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
[object Object]
[object Object]
CCC.MLDE.CN05 Restrict Environment Options on MLDE Instances20
CCC.MLDE.CN05.AR01Verify that only approved VM and container images can be selected when creating MLDE instances.0
Attributes
- Section
CCC.MLDE.CN05 Restrict Environment Options on MLDE Instances
- Family Name
Configuration Management
- Applicability
tlp-red
tlp-amber
- Family Description
TODO: Describe this control family
- Sub Section Objective
Limit the virtual machine and container image options available when creating new MLDE instances to approved and secure configurations.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
[object Object]
[object Object]
CCC.MLDE.CN05.AR02Attempt to create an MLDE instance with an unapproved image and confirm that it is denied.0
Attributes
- Section
CCC.MLDE.CN05 Restrict Environment Options on MLDE Instances
- Family Name
Configuration Management
- Applicability
tlp-red
- Family Description
TODO: Describe this control family
- Sub Section Objective
Limit the virtual machine and container image options available when creating new MLDE instances to approved and secure configurations.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
[object Object]
[object Object]
CCC.MLDE.CN06 Require Automatic Scheduled Upgrades on User-Managed MLDE Instances20
CCC.MLDE.CN06.AR01Verify that automatic scheduled upgrades are enabled on user-managed MLDE instances containing sensitive data.0
Attributes
- Section
CCC.MLDE.CN06 Require Automatic Scheduled Upgrades on User-Managed MLDE Instances
- Family Name
Vulnerability Management
- Applicability
tlp-red
- Family Description
TODO: Describe this control family
- Sub Section Objective
Ensure that MLDE instances are kept up-to-date with the latest security patches by enforcing automatic scheduled upgrades.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
[object Object]
[object Object]
CCC.MLDE.CN06.AR02Ensure that the upgrade schedule is appropriately configured and does not interfere with critical operations.0
Attributes
- Section
CCC.MLDE.CN06 Require Automatic Scheduled Upgrades on User-Managed MLDE Instances
- Family Name
Vulnerability Management
- Applicability
tlp-red
tlp-amber
tlp-green
tlp-clear
- Family Description
TODO: Describe this control family
- Sub Section Objective
Ensure that MLDE instances are kept up-to-date with the latest security patches by enforcing automatic scheduled upgrades.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
[object Object]
[object Object]
CCC.MLDE.CN07 Restrict Public IP Access on MLDE Instances20
CCC.MLDE.CN07.AR01Verify that MLDE instances containing sensitive data cannot be accessed via public IP addresses.0
Attributes
- Section
CCC.MLDE.CN07 Restrict Public IP Access on MLDE Instances
- Family Name
Network Security
- Applicability
tlp-red
- Family Description
TODO: Describe this control family
- Sub Section Objective
Prevent public IP access to MLDE instances to reduce exposure to the internet and enhance security.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
[object Object]
[object Object]
CCC.MLDE.CN07.AR02For MLDE instances without sensitive data requiring public access, ensure that appropriate security controls are in place and access is approved.0
Attributes
- Section
CCC.MLDE.CN07 Restrict Public IP Access on MLDE Instances
- Family Name
Network Security
- Applicability
tlp-red
tlp-amber
tlp-green
tlp-clear
- Family Description
TODO: Describe this control family
- Sub Section Objective
Prevent public IP access to MLDE instances to reduce exposure to the internet and enhance security.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
[object Object]
[object Object]
CCC.MLDE.CN08 Restrict Virtual Networks for MLDE Instances20
CCC.MLDE.CN08.AR01Verify that MLDE instances containing sensitive data can only be deployed in approved virtual networks with appropriate security controls.0
Attributes
- Section
CCC.MLDE.CN08 Restrict Virtual Networks for MLDE Instances
- Family Name
Network Security
- Applicability
tlp-red
- Family Description
TODO: Describe this control family
- Sub Section Objective
Limit the virtual networks that can be used when creating new MLDE instances to ensure they are deployed within approved and secure network environments.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
[object Object]
[object Object]
CCC.MLDE.CN08.AR02Ensure that MLDE instances without sensitive data are deployed in networks that meet organizational security standards.0
Attributes
- Section
CCC.MLDE.CN08 Restrict Virtual Networks for MLDE Instances
- Family Name
Network Security
- Applicability
tlp-red
tlp-amber
tlp-green
tlp-clear
- Family Description
TODO: Describe this control family
- Sub Section Objective
Limit the virtual networks that can be used when creating new MLDE instances to ensure they are deployed within approved and secure network environments.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
[object Object]
[object Object]
CCC.Message.CN01 Use Customer-Managed Encryption Keys (CMEK) for Messages10
CCC.Message.CN01.AR01Attempt to publish a message without using a customer-managed encryption key and verify that the message is rejected or not stored.0
Attributes
- Section
CCC.Message.CN01 Use Customer-Managed Encryption Keys (CMEK) for Messages
- Family Name
Encryption
- Applicability
tlp-clear
tlp-green
tlp-amber
tlp-red
- Family Description
TODO: Describe this control family
- Sub Section Objective
Ensure that messages are encrypted using customer-managed encryption keys (CMEK) to provide enhanced control over encryption processes and keys, meeting compliance and security requirements.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.SvlsComp.CN01 Enforce Use of Private Endpoints for Serverless Function11
CCC.SvlsComp.CN01.AR01Attempt to access the serverless function over the public internet and verify that access is denied.1
Attributes
- Section
CCC.SvlsComp.CN01 Enforce Use of Private Endpoints for Serverless Function
- Family Name
Network Security
- Applicability
tlp-red
tlp-amber
- Family Description
TODO: Describe this control family
- Sub Section Objective
Ensure that the serverless function is accessible only through a private endpoint, allowing it to communicate securely within a virtual private network and preventing unauthorized external access.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]
CCC.SvlsComp.CN02 Implement Function Invocation Rate Limits10
CCC.SvlsComp.CN02.AR01Send requests to invoke the function up to the allowed threshold and confirm they are successful; then send additional requests exceeding the threshold from the same entity and verify that they are denied.0
Attributes
- Section
CCC.SvlsComp.CN02 Implement Function Invocation Rate Limits
- Family Name
Availability
- Applicability
tlp-red
tlp-amber
- Family Description
TODO: Describe this control family
- Sub Section Objective
Ensure that function invocation is limited to a specified threshold from any single entity, preventing resource exhaustion and denial of service attacks.
- Section Threat Mappings
[object Object]
- Section Guideline Mappings
[object Object]
[object Object]