Google Cloud Compliance FrameworksCore Frameworks
NIST Cybersecurity Framework v2.0
Best for: The official page says the Cybersecurity Framework is "For industry, government, and organizations to reduce cybersecurity risks". It describes its purpose as helping organizations better understand and improve their management of cybersecurity risk.
| Mandatory? | Voluntary — widely adopted across sectors |
| Who validates? | Self-assessment; optional third-party |
| Renewal | No fixed cycle; continuous improvement |
| Scope | All organizations; six functions: Govern, Identify, Protect, Detect, Respond, Recover |
Controls by Category
DE.AE-02: Potentially adverse events are analyzed to better understand associated activities. (9 controls)
Projects should have Cloud Audit Logs properly configured across all services and all usersProjects should have log metric filters and alerts configured for Audit Configuration changesProjects should have log metric filters and alerts configured for Custom Role changesProjects should have log metric filters and alerts configured for VPC Network Firewall rule changesProjects should have log metric filters and alerts configured for VPC network changesProjects should have log metric filters and alerts configured for VPC network route changesProjects should have log metric filters and alerts configured for project ownership assignments and changesProjects should have log metric filters and alerts configured for Cloud SQL instance configuration changesProjects should have log metric filters and alerts configured for Cloud Storage IAM permission changes
DE.AE-03: Information is correlated from multiple sources. (1 control)
DE.AE-04: The estimated impact and scope of adverse events are understood. (9 controls)
Projects should have Cloud Audit Logs properly configured across all services and all usersProjects should have log metric filters and alerts configured for Audit Configuration changesProjects should have log metric filters and alerts configured for Custom Role changesProjects should have log metric filters and alerts configured for VPC Network Firewall rule changesProjects should have log metric filters and alerts configured for VPC network changesProjects should have log metric filters and alerts configured for VPC network route changesProjects should have log metric filters and alerts configured for project ownership assignments and changesProjects should have log metric filters and alerts configured for Cloud SQL instance configuration changesProjects should have log metric filters and alerts configured for Cloud Storage IAM permission changes
DE.AE-06: Information on adverse events is provided to authorized staff and tools. (9 controls)
Projects should have log metric filters and alerts configured for Audit Configuration changesProjects should have log metric filters and alerts configured for Custom Role changesProjects should have log metric filters and alerts configured for VPC Network Firewall rule changesProjects should have log metric filters and alerts configured for VPC network changesProjects should have log metric filters and alerts configured for VPC network route changesProjects should have log metric filters and alerts configured for project ownership assignments and changesProjects should have log metric filters and alerts configured for Cloud SQL instance configuration changesProjects should have log metric filters and alerts configured for Cloud Storage IAM permission changesProjects should have log sinks configured for all log entries
DE.AE-07: Cyber threat intelligence and other contextual information are integrated into the analysis. (1 control)
DE.AE-08: Incidents are declared when adverse events meet the defined incident criteria. (8 controls)
Projects should have log metric filters and alerts configured for Audit Configuration changesProjects should have log metric filters and alerts configured for Custom Role changesProjects should have log metric filters and alerts configured for VPC Network Firewall rule changesProjects should have log metric filters and alerts configured for VPC network changesProjects should have log metric filters and alerts configured for VPC network route changesProjects should have log metric filters and alerts configured for project ownership assignments and changesProjects should have log metric filters and alerts configured for Cloud SQL instance configuration changesProjects should have log metric filters and alerts configured for Cloud Storage IAM permission changes
DE.CM-01: Networks and network services are monitored to find potentially adverse events. (5 controls)
VPC networks should all have Cloud DNS logging enabledVPC subnets should all have VPC Flow Logs enabledProjects should have log metric filters and alerts configured for VPC Network Firewall rule changesProjects should have log metric filters and alerts configured for VPC network changesProjects should have log metric filters and alerts configured for VPC network route changes
DE.CM-02: The physical environment is monitored to find potentially adverse events. (1 control)
DE.CM-03: Personnel activity and technology usage are monitored to find potentially adverse events. (6 controls)
Projects should have Cloud Audit Logs properly configured across all services and all usersAPI keys should have rotation configured every 90 daysUser-managed or external service account keys should have rotation configured every 90 days or lessProjects should have log metric filters and alerts configured for Audit Configuration changesProjects should have log metric filters and alerts configured for Custom Role changesProjects should have log metric filters and alerts configured for project ownership assignments and changes
DE.CM-06: External service provider activities and services are monitored to find potentially adverse events. (2 controls)
DE.CM-09: Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events. (5 controls)
Projects should have Cloud Audit Logs properly configured across all services and all usersGKE clusters should have monitoring enabledProjects should have log metric filters and alerts configured for project ownership assignments and changesProjects should have log metric filters and alerts configured for Cloud SQL instance configuration changesProjects should have log metric filters and alerts configured for Cloud Storage IAM permission changes
GV.OC-01: The organizational mission is understood and informs cybersecurity risk management. (6 controls)
IAM policies should allow only members from the organization's domainOrganizations should have Essential Contacts configuredProjects should have 'Access Approval' set to 'Enabled'Projects should have Cloud Asset Inventory enabledBigQuery datasets should require corporate-domain access and prohibit access by gmail.com addressesBigQuery datasets should require corporate-domain access and prohibit access by googlegroups.com addresses
GV.OC-02: Internal and external stakeholders are understood, and their needs and expectations regarding cybersecurity risk management are understood and considered. (1 control)
GV.OC-03: Legal, regulatory, and contractual requirements regarding cybersecurity — including privacy and civil liberties obligations — are understood and managed. (11 controls)
Log buckets should have retention policies configured using Bucket LockProjects should have log metric filters and alerts configured for Audit Configuration changesProjects should have log metric filters and alerts configured for Custom Role changesProjects should have log metric filters and alerts configured for Custom Role changes, including undeleteProjects should have log metric filters and alerts configured for VPC Network Firewall rule changesProjects should have log metric filters and alerts configured for VPC network changesProjects should have log metric filters and alerts configured for VPC network route changesProjects should have log metric filters and alerts configured for project ownership assignments and changesProjects should have log metric filters and alerts configured for Cloud SQL instance configuration changesProjects should have log metric filters and alerts configured for Cloud Storage IAM permission changesProjects should have log sinks configured for all log entries
GV.OC-04: Critical objectives, capabilities, and services that external stakeholders depend on or expect from the organization are understood and communicated. (2 controls)
GV.OC-05: Outcomes, capabilities, and services that the organization depends on are understood and communicated. (2 controls)
GV.OV-01: Cybersecurity risk management strategy outcomes are reviewed to inform and adjust strategy and direction. (11 controls)
Projects should have Cloud Audit Logs properly configured across all services and all usersProjects should have log metric filters and alerts configured for Audit Configuration changesProjects should have log metric filters and alerts configured for Custom Role changesProjects should have log metric filters and alerts configured for Custom Role changes, including undeleteProjects should have log metric filters and alerts configured for VPC Network Firewall rule changesProjects should have log metric filters and alerts configured for VPC network changesProjects should have log metric filters and alerts configured for VPC network route changesProjects should have log metric filters and alerts configured for project ownership assignments and changesProjects should have log metric filters and alerts configured for Cloud SQL instance configuration changesProjects should have log metric filters and alerts configured for Cloud Storage IAM permission changesProjects should have log sinks configured for all log entries
GV.OV-02: The cybersecurity risk management strategy is reviewed and adjusted to ensure coverage of organizational requirements and risks. (11 controls)
Projects should have Cloud Audit Logs properly configured across all services and all usersProjects should have log metric filters and alerts configured for Audit Configuration changesProjects should have log metric filters and alerts configured for Custom Role changesProjects should have log metric filters and alerts configured for Custom Role changes, including undeleteProjects should have log metric filters and alerts configured for VPC Network Firewall rule changesProjects should have log metric filters and alerts configured for VPC network changesProjects should have log metric filters and alerts configured for VPC network route changesProjects should have log metric filters and alerts configured for project ownership assignments and changesProjects should have log metric filters and alerts configured for Cloud SQL instance configuration changesProjects should have log metric filters and alerts configured for Cloud Storage IAM permission changesProjects should have log sinks configured for all log entries
GV.OV-03: Organizational cybersecurity risk management performance is evaluated and reviewed for adjustments needed. (11 controls)
Projects should have Cloud Audit Logs properly configured across all services and all usersProjects should have log metric filters and alerts configured for Audit Configuration changesProjects should have log metric filters and alerts configured for Custom Role changesProjects should have log metric filters and alerts configured for Custom Role changes, including undeleteProjects should have log metric filters and alerts configured for VPC Network Firewall rule changesProjects should have log metric filters and alerts configured for VPC network changesProjects should have log metric filters and alerts configured for VPC network route changesProjects should have log metric filters and alerts configured for project ownership assignments and changesProjects should have log metric filters and alerts configured for Cloud SQL instance configuration changesProjects should have log metric filters and alerts configured for Cloud Storage IAM permission changesProjects should have log sinks configured for all log entries
GV.PO-01: Policy for managing cybersecurity risks is established based on organizational context, cybersecurity strategy, and priorities and is communicated and enforced. (10 controls)
Projects should have Cloud Audit Logs properly configured across all services and all usersProjects should have log metric filters and alerts configured for Audit Configuration changesProjects should have log metric filters and alerts configured for Custom Role changesProjects should have log metric filters and alerts configured for Custom Role changes, including undeleteProjects should have log metric filters and alerts configured for VPC Network Firewall rule changesProjects should have log metric filters and alerts configured for VPC network changesProjects should have log metric filters and alerts configured for VPC network route changesProjects should have log metric filters and alerts configured for project ownership assignments and changesProjects should have log metric filters and alerts configured for Cloud SQL instance configuration changesProjects should have log metric filters and alerts configured for Cloud Storage IAM permission changes
GV.PO-02: Policy for managing cybersecurity risks is reviewed, updated, communicated, and enforced to reflect changes in requirements, threats, technology, and organizational mission. (11 controls)
Projects should have Cloud Audit Logs properly configured across all services and all usersProjects should have log metric filters and alerts configured for Audit Configuration changesProjects should have log metric filters and alerts configured for Custom Role changesProjects should have log metric filters and alerts configured for Custom Role changes, including undeleteProjects should have log metric filters and alerts configured for VPC Network Firewall rule changesProjects should have log metric filters and alerts configured for VPC network changesProjects should have log metric filters and alerts configured for VPC network route changesProjects should have log metric filters and alerts configured for project ownership assignments and changesProjects should have log metric filters and alerts configured for Cloud SQL instance configuration changesProjects should have log metric filters and alerts configured for Cloud Storage IAM permission changesProjects should have log sinks configured for all log entries
GV.RM-01: Risk management objectives are established and agreed to by organizational stakeholders. (5 controls)
Service accounts should use only GCP-managed service account keysUser-managed or external service account keys should have rotation configured every 90 days or lessIAM policies should allow only members from the organization's domainProjects should have 'Access Approval' set to 'Enabled'Projects should have Cloud Asset Inventory enabled
GV.RM-02: Risk appetite and risk tolerance statements are established, communicated, and maintained. (6 controls)
Customer-managed encryption keys should be rotated within 100 daysAPI keys should have rotation configured every 90 daysUser-managed or external service account keys should have rotation configured every 90 days or lessCloud KMS encryption keys should have rotation configured within 90 daysLog buckets should have retention policies configured using Bucket LockProjects should have 'Access Approval' set to 'Enabled'
GV.RM-03: Cybersecurity risk management activities and outcomes are included in enterprise risk management processes. (5 controls)
Projects should have Cloud Audit Logs properly configured across all services and all usersUser-managed or external service account keys should have rotation configured every 90 days or lessCloud KMS encryption keys should have rotation configured within 90 daysProjects should have log metric filters and alerts configured for Audit Configuration changesProjects should have 'Access Approval' set to 'Enabled'
GV.RM-04: Strategic direction that describes appropriate risk response options is established and communicated. (6 controls)
API keys should have rotation configured every 90 daysUser-managed or external service account keys should have rotation configured every 90 days or lessLog buckets should have retention policies configured using Bucket LockOrganizations should have Essential Contacts configuredProjects should have 'Access Approval' set to 'Enabled'Cloud Storage buckets should have Bucket Only Policy enabled
GV.RM-05: Lines of communication across the organization are established for cybersecurity risks, including risks from suppliers and other third parties. (10 controls)
Projects should have log metric filters and alerts configured for Audit Configuration changesProjects should have log metric filters and alerts configured for Custom Role changesProjects should have log metric filters and alerts configured for Custom Role changes, including undeleteProjects should have log metric filters and alerts configured for VPC Network Firewall rule changesProjects should have log metric filters and alerts configured for VPC network changesProjects should have log metric filters and alerts configured for VPC network route changesProjects should have log metric filters and alerts configured for project ownership assignments and changesProjects should have log metric filters and alerts configured for Cloud SQL instance configuration changesProjects should have log metric filters and alerts configured for Cloud Storage IAM permission changesOrganizations should have Essential Contacts configured
GV.RM-06: A standardized method for calculating, documenting, categorizing, and prioritizing cybersecurity risks is established and communicated. (10 controls)
Projects should have Cloud Audit Logs properly configured across all services and all usersProjects should have log metric filters and alerts configured for Audit Configuration changesProjects should have log metric filters and alerts configured for Custom Role changesProjects should have log metric filters and alerts configured for Custom Role changes, including undeleteProjects should have log metric filters and alerts configured for VPC Network Firewall rule changesProjects should have log metric filters and alerts configured for VPC network changesProjects should have log metric filters and alerts configured for VPC network route changesProjects should have log metric filters and alerts configured for project ownership assignments and changesProjects should have log metric filters and alerts configured for Cloud SQL instance configuration changesProjects should have log metric filters and alerts configured for Cloud Storage IAM permission changes
GV.RM-07: Strategic opportunities (i.e., positive risks) are characterized and are included in organizational cybersecurity risk discussions. (10 controls)
Projects should have Cloud Audit Logs properly configured across all services and all usersProjects should have log metric filters and alerts configured for Audit Configuration changesProjects should have log metric filters and alerts configured for Custom Role changesProjects should have log metric filters and alerts configured for Custom Role changes, including undeleteProjects should have log metric filters and alerts configured for VPC Network Firewall rule changesProjects should have log metric filters and alerts configured for VPC network changesProjects should have log metric filters and alerts configured for VPC network route changesProjects should have log metric filters and alerts configured for project ownership assignments and changesProjects should have log metric filters and alerts configured for Cloud SQL instance configuration changesProjects should have log metric filters and alerts configured for Cloud Storage IAM permission changes
GV.RR-01: Organizational leadership is responsible and accountable for cybersecurity risk and fosters a culture that is risk-aware, ethical, and continually improving. (4 controls)
Projects should have Cloud Audit Logs properly configured across all services and all usersProjects should have log metric filters and alerts configured for Audit Configuration changesProjects should have log metric filters and alerts configured for Custom Role changesProjects should have log metric filters and alerts configured for Custom Role changes, including undelete
GV.RR-02: Roles, responsibilities, and authorities related to cybersecurity risk management are established, communicated, understood, and enforced. (7 controls)
Service accounts should use only GCP-managed service account keysUser-managed or external service account keys should have rotation configured every 90 days or lessIAM users should not have Service Account User or Service Account Token Creator roles at project levelProjects should have log metric filters and alerts configured for Custom Role changesProjects should have log metric filters and alerts configured for Custom Role changes, including undeleteProjects should have log metric filters and alerts configured for project ownership assignments and changesProjects should have log metric filters and alerts configured for Cloud Storage IAM permission changes
GV.RR-03: Adequate resources are allocated commensurate with the cybersecurity risk strategy, roles, responsibilities, and policies. (7 controls)
Projects should have Cloud Audit Logs properly configured across all services and all usersIAM users should not have Service Account User or Service Account Token Creator roles at project levelProjects should have log metric filters and alerts configured for Audit Configuration changesProjects should have log metric filters and alerts configured for Custom Role changesProjects should have log metric filters and alerts configured for Custom Role changes, including undeleteProjects should have log metric filters and alerts configured for project ownership assignments and changesProjects should have log metric filters and alerts configured for Cloud Storage IAM permission changes
GV.RR-04: Cybersecurity is included in human resources practices. (5 controls)
IAM users should not have Service Account User or Service Account Token Creator roles at project levelProjects should have log metric filters and alerts configured for Custom Role changesProjects should have log metric filters and alerts configured for Custom Role changes, including undeleteProjects should have log metric filters and alerts configured for project ownership assignments and changesProjects should have 'Access Approval' set to 'Enabled'
GV.SC-01: A cybersecurity supply chain risk management program, strategy, objectives, policies, and processes are established and agreed to by organizational stakeholders. (7 controls)
Projects should have Cloud Audit Logs properly configured across all services and all usersProjects should have log metric filters and alerts configured for Audit Configuration changesProjects should have log metric filters and alerts configured for Custom Role changesProjects should have log metric filters and alerts configured for Custom Role changes, including undeleteProjects should have log metric filters and alerts configured for project ownership assignments and changesProjects should have log metric filters and alerts configured for Cloud Storage IAM permission changesProjects should have log sinks configured for all log entries
GV.SC-02: Cybersecurity roles and responsibilities for suppliers, customers, and partners are established, communicated, and coordinated internally and externally. (6 controls)
Service accounts should use only GCP-managed service account keysUser-managed or external service account keys should have rotation configured every 90 days or lessIAM users should not have Service Account User or Service Account Token Creator roles at project levelProjects should have log metric filters and alerts configured for Custom Role changesProjects should have log metric filters and alerts configured for Custom Role changes, including undeleteProjects should have log metric filters and alerts configured for Cloud Storage IAM permission changes
GV.SC-03: Cybersecurity supply chain risk management is integrated into cybersecurity and enterprise risk management, risk assessment, and improvement processes. (7 controls)
Projects should have Cloud Audit Logs properly configured across all services and all usersProjects should have log metric filters and alerts configured for Audit Configuration changesProjects should have log metric filters and alerts configured for Custom Role changesProjects should have log metric filters and alerts configured for Custom Role changes, including undeleteProjects should have log metric filters and alerts configured for project ownership assignments and changesProjects should have log metric filters and alerts configured for Cloud Storage IAM permission changesProjects should have log sinks configured for all log entries
GV.SC-04: Suppliers are known and prioritized by criticality. (2 controls)
GV.SC-05: Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant third parties. (13 controls)
IAM policies should not grant access to 'allUsers' or 'allAuthenticatedUsers'Projects should have log metric filters and alerts configured for Custom Role changesProjects should have log metric filters and alerts configured for Custom Role changes, including undeleteProjects should have log metric filters and alerts configured for VPC Network Firewall rule changesProjects should have log metric filters and alerts configured for VPC network changesProjects should have log metric filters and alerts configured for VPC network route changesProjects should have log metric filters and alerts configured for project ownership assignments and changesIAM policies should allow only members from the organization's domainOrganizations should have Essential Contacts configuredProjects should have 'Access Approval' set to 'Enabled'Projects should have Cloud Asset Inventory enabledCloud Storage buckets should have Bucket Only Policy enabledCloud Storage buckets should prohibit anonymous and public access
GV.SC-06: Planning and due diligence are performed to reduce risks before entering into formal supplier or other third-party relationships. (12 controls)
IAM users should not hold both KMS admin and KMS key user rolesIAM users should not have Service Account User or Service Account Token Creator roles at project levelIAM users should not hold both service account admin and service account user rolesProjects should have log metric filters and alerts configured for Custom Role changesProjects should have log metric filters and alerts configured for Custom Role changes, including undeleteProjects should have log metric filters and alerts configured for VPC Network Firewall rule changesProjects should have log metric filters and alerts configured for VPC network changesProjects should have log metric filters and alerts configured for VPC network route changesProjects should have log metric filters and alerts configured for project ownership assignments and changesOrganizations should have Essential Contacts configuredProjects should have 'Access Approval' set to 'Enabled'Projects should have Cloud Asset Inventory enabled
GV.SC-07: The risks posed by a supplier, their products and services, and other third parties are understood, recorded, prioritized, assessed, responded to, and monitored over the course of the relationship. (21 controls)
Projects should have Cloud Audit Logs properly configured across all services and all usersFirewall rules should have logging enabledGKE clusters should have monitoring enabledLog buckets should have retention policies configured using Bucket LockProjects should have log metric filters and alerts configured for Audit Configuration changesProjects should have log metric filters and alerts configured for Custom Role changesProjects should have log metric filters and alerts configured for Custom Role changes, including undeleteProjects should have log metric filters and alerts configured for VPC Network Firewall rule changesProjects should have log metric filters and alerts configured for VPC network changesProjects should have log metric filters and alerts configured for VPC network route changesProjects should have log metric filters and alerts configured for project ownership assignments and changesProjects should have log metric filters and alerts configured for Cloud SQL instance configuration changesProjects should have log metric filters and alerts configured for Cloud Storage IAM permission changesProjects should have log sinks configured for all log entriesCloud SQL PostgreSQL instances should each have 'cloudsql.enable_pgaudit' set to 'on' for centralized loggingCloud SQL PostgreSQL instances should have 'log_checkpoints' set to 'on'Cloud SQL PostgreSQL instances should have 'log_connections' set to 'on'Cloud SQL PostgreSQL instances should have 'log_statement' set to 'ddl'Cloud Storage buckets used for exporting logs should prohibit anonymous and public accessCloud Storage buckets used for exporting logs should have object versioning enabledCloud Storage buckets used for exporting logs should have retention policies enabled
GV.SC-08: Relevant suppliers and other third parties are included in incident planning, response, and recovery activities. (13 controls)
Projects should have Cloud Audit Logs properly configured across all services and all usersLog buckets should have retention policies configured using Bucket LockProjects should have log metric filters and alerts configured for Audit Configuration changesProjects should have log metric filters and alerts configured for Custom Role changesProjects should have log metric filters and alerts configured for Custom Role changes, including undeleteProjects should have log metric filters and alerts configured for VPC Network Firewall rule changesProjects should have log metric filters and alerts configured for VPC network changesProjects should have log metric filters and alerts configured for VPC network route changesProjects should have log metric filters and alerts configured for project ownership assignments and changesProjects should have log metric filters and alerts configured for Cloud SQL instance configuration changesProjects should have log metric filters and alerts configured for Cloud Storage IAM permission changesProjects should have log sinks configured for all log entriesOrganizations should have Essential Contacts configured
GV.SC-09: Supply chain security practices are integrated into cybersecurity and enterprise risk management programs, and their performance is monitored throughout the technology product and service life cycle. (14 controls)
Projects should have Cloud Audit Logs properly configured across all services and all usersGKE clusters should have monitoring enabledGKE cluster shielded nodes should have integrity monitoring enabledLog buckets should have retention policies configured using Bucket LockProjects should have log metric filters and alerts configured for Audit Configuration changesProjects should have log metric filters and alerts configured for Custom Role changesProjects should have log metric filters and alerts configured for Custom Role changes, including undeleteProjects should have log metric filters and alerts configured for VPC Network Firewall rule changesProjects should have log metric filters and alerts configured for VPC network changesProjects should have log metric filters and alerts configured for VPC network route changesProjects should have log metric filters and alerts configured for project ownership assignments and changesProjects should have log metric filters and alerts configured for Cloud SQL instance configuration changesProjects should have log metric filters and alerts configured for Cloud Storage IAM permission changesProjects should have log sinks configured for all log entries
GV.SC-10: Cybersecurity supply chain risk management plans include provisions for activities that occur after the conclusion of a partnership or service agreement. (17 controls)
Projects should have Cloud Audit Logs properly configured across all services and all usersAPI keys should have rotation configured every 90 daysService accounts should use only GCP-managed service account keysUser-managed or external service account keys should have rotation configured every 90 days or lessIAM users should not have Service Account User or Service Account Token Creator roles at project levelIAM users should not hold both service account admin and service account user rolesKMS keys should have separation of duties enforced for KMS-related rolesCloud KMS encryption keys should limit users to 3Projects should have log metric filters and alerts configured for Custom Role changesProjects should have log metric filters and alerts configured for Custom Role changes, including undeleteProjects should have log metric filters and alerts configured for VPC Network Firewall rule changesProjects should have log metric filters and alerts configured for VPC network changesProjects should have log metric filters and alerts configured for VPC network route changesProjects should have log metric filters and alerts configured for project ownership assignments and changesOrganizations should have Essential Contacts configuredProjects should have 'Access Approval' set to 'Enabled'Projects should have Cloud Asset Inventory enabled
ID.AM-01: Inventories of hardware managed by the organization are maintained. (9 controls)
Disks for critical VMs should use Customer-Supplied Encryption Keys (CSEK) for encryptionCompute Engine instances should have 'Block Project-wide SSH keys' enabledCompute Engine instances should have Confidential Computing enabledCompute Engine instances should all have OS Login enabled in the projectCompute Engine instances should have 'Enable connecting to serial ports' disabledCompute Engine instances should have Shielded VM enabled at launchCompute Engine instances should not use the default service accountCompute Engine instances should not have public IP addressesProjects should have Cloud Asset Inventory enabled
ID.AM-02: Inventories of software, services, and systems managed by the organization are maintained. (5 controls)
Projects should have Cloud Audit Logs properly configured across all services and all usersService accounts should use only GCP-managed service account keysUser-managed or external service account keys should have rotation configured every 90 days or lessIAM users should not have Service Account User or Service Account Token Creator roles at project levelProjects should have Cloud Asset Inventory enabled
ID.AM-03: Representations of the organization's authorized network communication and internal and external network data flows are maintained. (5 controls)
VPC networks should all have Cloud DNS logging enabledVPC subnets should all have VPC Flow Logs enabledProjects should have log metric filters and alerts configured for VPC Network Firewall rule changesProjects should have log metric filters and alerts configured for VPC network changesProjects should have log metric filters and alerts configured for VPC network route changes
ID.AM-04: Inventories of services provided by suppliers are maintained. (2 controls)
ID.AM-05: Assets are prioritized based on classification, criticality, resources, and impact on the mission. (1 control)
ID.AM-07: Inventories of data and corresponding metadata for designated data types are maintained. (5 controls)
Projects should have log metric filters and alerts configured for Cloud Storage IAM permission changesProjects should have Cloud Asset Inventory enabledCloud Storage buckets used for exporting logs should have object versioning enabledCloud Storage buckets used for exporting logs should have retention policies enabledCloud Storage buckets should prohibit anonymous and public access
ID.AM-08: Systems, hardware, software, services, and data are managed throughout their life cycles. (5 controls)
User-managed or external service account keys should have rotation configured every 90 days or lessCloud KMS encryption keys should have rotation configured within 90 daysLog buckets should have retention policies configured using Bucket LockProjects should have Cloud Asset Inventory enabledCloud Storage buckets used for exporting logs should have retention policies enabled
ID.IM-01: Improvements are identified from evaluations. (3 controls)
ID.IM-02: Improvements are identified from security tests and exercises, including those done in coordination with suppliers and relevant third parties. (3 controls)
ID.IM-03: Improvements are identified from execution of operational processes, procedures, and activities. (4 controls)
Projects should have Cloud Audit Logs properly configured across all services and all usersLog buckets should have retention policies configured using Bucket LockProjects should have log metric filters and alerts configured for Audit Configuration changesCloud SQL PostgreSQL instances should each have 'cloudsql.enable_pgaudit' set to 'on' for centralized logging
ID.IM-04: Incident response plans and other cybersecurity plans that affect operations are established, communicated, maintained, and improved. (1 control)
ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. (1 control)
ID.RA-02: Cyber threat intelligence is received from information sharing forums and sources. (10 controls)
Projects should have log metric filters and alerts configured for Audit Configuration changesProjects should have log metric filters and alerts configured for Custom Role changesProjects should have log metric filters and alerts configured for Custom Role changes, including undeleteProjects should have log metric filters and alerts configured for VPC Network Firewall rule changesProjects should have log metric filters and alerts configured for VPC network changesProjects should have log metric filters and alerts configured for VPC network route changesProjects should have log metric filters and alerts configured for project ownership assignments and changesProjects should have log metric filters and alerts configured for Cloud SQL instance configuration changesProjects should have log metric filters and alerts configured for Cloud Storage IAM permission changesOrganizations should have Essential Contacts configured
ID.RA-03: Internal and external threats to the organization are identified and recorded. (9 controls)
Projects should have log metric filters and alerts configured for Audit Configuration changesProjects should have log metric filters and alerts configured for Custom Role changesProjects should have log metric filters and alerts configured for Custom Role changes, including undeleteProjects should have log metric filters and alerts configured for VPC Network Firewall rule changesProjects should have log metric filters and alerts configured for VPC network changesProjects should have log metric filters and alerts configured for VPC network route changesProjects should have log metric filters and alerts configured for project ownership assignments and changesProjects should have log metric filters and alerts configured for Cloud SQL instance configuration changesProjects should have log metric filters and alerts configured for Cloud Storage IAM permission changes
ID.RA-04: Potential impacts and likelihoods of threats exploiting vulnerabilities are identified and recorded. (9 controls)
Projects should have log metric filters and alerts configured for Audit Configuration changesProjects should have log metric filters and alerts configured for Custom Role changesProjects should have log metric filters and alerts configured for Custom Role changes, including undeleteProjects should have log metric filters and alerts configured for VPC Network Firewall rule changesProjects should have log metric filters and alerts configured for VPC network changesProjects should have log metric filters and alerts configured for VPC network route changesProjects should have log metric filters and alerts configured for project ownership assignments and changesProjects should have log metric filters and alerts configured for Cloud SQL instance configuration changesProjects should have log metric filters and alerts configured for Cloud Storage IAM permission changes
ID.RA-05: Threats, vulnerabilities, likelihoods, and impacts are used to understand inherent risk and inform risk response prioritization. (9 controls)
Projects should have log metric filters and alerts configured for Audit Configuration changesProjects should have log metric filters and alerts configured for Custom Role changesProjects should have log metric filters and alerts configured for Custom Role changes, including undeleteProjects should have log metric filters and alerts configured for VPC Network Firewall rule changesProjects should have log metric filters and alerts configured for VPC network changesProjects should have log metric filters and alerts configured for VPC network route changesProjects should have log metric filters and alerts configured for project ownership assignments and changesProjects should have log metric filters and alerts configured for Cloud SQL instance configuration changesProjects should have log metric filters and alerts configured for Cloud Storage IAM permission changes
ID.RA-06: Risk responses are chosen, prioritized, planned, tracked, and communicated. (9 controls)
Projects should have log metric filters and alerts configured for Audit Configuration changesProjects should have log metric filters and alerts configured for Custom Role changesProjects should have log metric filters and alerts configured for Custom Role changes, including undeleteProjects should have log metric filters and alerts configured for VPC Network Firewall rule changesProjects should have log metric filters and alerts configured for VPC network changesProjects should have log metric filters and alerts configured for VPC network route changesProjects should have log metric filters and alerts configured for project ownership assignments and changesProjects should have log metric filters and alerts configured for Cloud SQL instance configuration changesProjects should have log metric filters and alerts configured for Cloud Storage IAM permission changes
ID.RA-07: Changes and exceptions are managed, assessed for risk impact, recorded, and tracked. (9 controls)
Projects should have log metric filters and alerts configured for Audit Configuration changesProjects should have log metric filters and alerts configured for Custom Role changesProjects should have log metric filters and alerts configured for Custom Role changes, including undeleteProjects should have log metric filters and alerts configured for VPC Network Firewall rule changesProjects should have log metric filters and alerts configured for VPC network changesProjects should have log metric filters and alerts configured for VPC network route changesProjects should have log metric filters and alerts configured for project ownership assignments and changesProjects should have log metric filters and alerts configured for Cloud SQL instance configuration changesProjects should have log metric filters and alerts configured for Cloud Storage IAM permission changes
ID.RA-08: Processes for receiving, analyzing, and responding to vulnerability disclosures are established. (10 controls)
Projects should have log metric filters and alerts configured for Audit Configuration changesProjects should have log metric filters and alerts configured for Custom Role changesProjects should have log metric filters and alerts configured for Custom Role changes, including undeleteProjects should have log metric filters and alerts configured for VPC Network Firewall rule changesProjects should have log metric filters and alerts configured for VPC network changesProjects should have log metric filters and alerts configured for VPC network route changesProjects should have log metric filters and alerts configured for project ownership assignments and changesProjects should have log metric filters and alerts configured for Cloud SQL instance configuration changesProjects should have log metric filters and alerts configured for Cloud Storage IAM permission changesProjects should have container vulnerability scanning enabled
ID.RA-09: The authenticity and integrity of hardware and software are assessed prior to acquisition and use. (6 controls)
Compute Engine instances should have Shielded VM enabled at launchGKE clusters should have Binary Authorization enabledGKE cluster shielded nodes should have integrity monitoring enabledGKE cluster shielded nodes should have secure boot enabledProjects should have container vulnerability scanning enabledCloud SQL SQL Server instances should have 'contained database authentication' set to 'off'
ID.RA-10: Critical suppliers are assessed prior to acquisition. (2 controls)
Other (2 controls)
PR.AA-01: Identities and credentials for authorized users, services, and hardware are managed by the organization. (15 controls)
IAM policies should not grant access to 'allUsers' or 'allAuthenticatedUsers'API keys should have rotation configured every 90 daysAPI keys should allow access only to APIs needed by the applicationAPI keys should allow use only by specified hosts and appsService account keys should limit age to 100 daysService accounts should use only GCP-managed service account keysUser-managed or external service account keys should have rotation configured every 90 days or lessService accounts should not have Admin privilegesIAM users should not hold both KMS admin and KMS key user rolesIAM users should not have Service Account User or Service Account Token Creator roles at project levelIAM users should not hold both service account admin and service account user rolesCloud KMS cryptokeys should prohibit anonymous and public accessCloud KMS encryption keys should have rotation configured within 90 daysKMS keys should have separation of duties enforced for KMS-related rolesCloud KMS encryption keys should limit users to 3
PR.AA-02: Identities are proofed and bound to credentials based on the context of interactions. (5 controls)
IAM users should not hold both KMS admin and KMS key user rolesIAM users should not hold both service account admin and service account user rolesKMS keys should have separation of duties enforced for KMS-related rolesGKE clusters should have client certificate authentication enabledCloud SQL SQL Server instances should have 'contained database authentication' set to 'off'
PR.AA-03: Users, services, and hardware are authenticated. (10 controls)
IAM policies should not grant access to 'allUsers' or 'allAuthenticatedUsers'API keys should have rotation configured every 90 daysAPI keys should allow access only to APIs needed by the applicationAPI keys should allow use only by specified hosts and appsService accounts should use only GCP-managed service account keysUser-managed or external service account keys should have rotation configured every 90 days or lessService accounts should not have Admin privilegesIAM users should not have Service Account User or Service Account Token Creator roles at project levelGKE clusters should have client certificate authentication enabledCloud SQL SQL Server instances should have 'contained database authentication' set to 'off'
PR.AA-04: Identity assertions are protected, conveyed, and verified. (8 controls)
HTTP(S) load balancers should have logging enabledHTTPS or SSL proxy load balancers should prohibit SSL policies with weak cipher suitesCompute Engine target HTTPS proxies should use the latest TLS versionCloud KMS cryptokeys should prohibit anonymous and public accessCloud KMS encryption keys should have rotation configured within 90 daysKMS keys should have separation of duties enforced for KMS-related rolesCloud KMS encryption keys should limit users to 3Cloud SQL instances should have SSL enabled
PR.AA-05: Access permissions, entitlements, and authorizations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties. (12 controls)
IAM policies should not grant access to 'allUsers' or 'allAuthenticatedUsers'API keys should have rotation configured every 90 daysAPI keys should allow access only to APIs needed by the applicationAPI keys should allow use only by specified hosts and appsService account keys should limit age to 100 daysService accounts should use only GCP-managed service account keysUser-managed or external service account keys should have rotation configured every 90 days or lessService accounts should not have Admin privilegesIAM users should not hold both KMS admin and KMS key user rolesIAM users should not have Service Account User or Service Account Token Creator roles at project levelIAM users should not hold both service account admin and service account user rolesProjects should have log metric filters and alerts configured for Cloud Storage IAM permission changes
PR.AA-06: Physical access to assets is managed, monitored, and enforced commensurate with risk. (1 control)
PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. (13 controls)
Customer-managed encryption keys should be rotated within 100 daysDisks for critical VMs should use Customer-Supplied Encryption Keys (CSEK) for encryptionDataproc clusters should use customer-managed encryption keys for encryptionCloud KMS cryptokeys should prohibit anonymous and public accessCloud KMS encryption keys should have rotation configured within 90 daysKMS keys should have separation of duties enforced for KMS-related rolesCloud KMS encryption keys should limit users to 3Cloud SQL instances should have automated backups configuredCloud SQL instances should have IP assignment set to privateCloud SQL PostgreSQL instances should each have 'cloudsql.enable_pgaudit' set to 'on' for centralized loggingCloud Storage buckets used for exporting logs should have object versioning enabledCloud Storage buckets used for exporting logs should have retention policies enabledCloud Storage buckets should prohibit anonymous and public access
PR.DS-02: The confidentiality, integrity, and availability of data-in-transit are protected. (5 controls)
Default firewall rules should prohibit ingress from 0.0.0.0/0 except HTTP and HTTPSHTTP(S) load balancers should have logging enabledHTTPS or SSL proxy load balancers should prohibit SSL policies with weak cipher suitesCompute Engine target HTTPS proxies should use the latest TLS versionCloud SQL instances should have SSL enabled
PR.DS-10: The confidentiality, integrity, and availability of data-in-use are protected. (2 controls)
PR.DS-11: Backups of data are created, protected, maintained, and tested. (5 controls)
Log buckets should have retention policies configured using Bucket LockCloud SQL instances should have automated backups configuredCloud Storage buckets used for exporting logs should have object versioning enabledCloud Storage buckets used for exporting logs should have retention policies enabledCloud Storage buckets used for exporting logs should use Bucket Lock
PR.IR-01: Networks and environments are protected from unauthorized logical access and usage. (53 controls)
Cloud Functions should have a VPC connector enabledFirewall rules for IAP-protected instances should allow only Google Cloud Load Balancer health check and proxy trafficFirewall rules should allow TCP traffic only from Google IP ranges for Identity-Aware Proxy (IAP)Default firewall rules should prohibit ingress from 0.0.0.0/0 except HTTP and HTTPSFirewall rules should prohibit ingress from 0.0.0.0/0 to DNS port 53Firewall rules should prohibit ingress from 0.0.0.0/0 to FTP port 21Firewall rules should prohibit ingress from 0.0.0.0/0 to HTTP port 80Firewall rules should prohibit ingress from 0.0.0.0/0 to Microsoft DS port 445Firewall rules should prohibit ingress from 0.0.0.0/0 to MongoDB port 27017Firewall rules should prohibit ingress from 0.0.0.0/0 to MySQL DB port 3306Firewall rules should prohibit ingress from 0.0.0.0/0 to NetBIOS session port 139Firewall rules should prohibit ingress from 0.0.0.0/0 to Oracle DB port 1521Firewall rules should prohibit ingress from 0.0.0.0/0 to POP3 port 110Firewall rules should prohibit ingress from 0.0.0.0/0 to port 10250Firewall rules should prohibit ingress from 0.0.0.0/0 to port 10255Firewall rules should prohibit ingress from 0.0.0.0/0 to PostgreSQL port 5432Firewall rules should prohibit ingress from 0.0.0.0/0 to SMTP port 25Firewall rules should prohibit ingress from 0.0.0.0/0 to TCP ports 137-139Firewall rules should prohibit ingress from 0.0.0.0/0 to TCP ports 27017-27019Firewall rules should prohibit ingress from 0.0.0.0/0 to TCP ports 61620 or 61621Firewall rules should prohibit ingress from 0.0.0.0/0 to TCP port 636Firewall rules should prohibit ingress from 0.0.0.0/0 to TCP port 6379Firewall rules should prohibit ingress from 0.0.0.0/0 to TCP ports 7000 or 7001Firewall rules should prohibit ingress from 0.0.0.0/0 to TCP port 7199Firewall rules should prohibit ingress from 0.0.0.0/0 to TCP port 8888Firewall rules should prohibit ingress from 0.0.0.0/0 to TCP port 9042Firewall rules should prohibit ingress from 0.0.0.0/0 to TCP port 9090Firewall rules should prohibit ingress from 0.0.0.0/0 to TCP port 9160Firewall rules should prohibit ingress from 0.0.0.0/0 to TCP ports 9200 or 9300Firewall rules should prohibit ingress from 0.0.0.0/0 to TCP or UDP port 11211Firewall rules should prohibit ingress from 0.0.0.0/0 to TCP or UDP ports 11214-11215Firewall rules should prohibit ingress from 0.0.0.0/0 to TCP or UDP ports 2483-2484Firewall rules should prohibit ingress from 0.0.0.0/0 to TCP or UDP port 389Firewall rules should prohibit ingress from 0.0.0.0/0 to Telnet port 23Firewall rules should have logging enabledFirewall rules should prohibit ingress from 0.0.0.0/0 to any portFirewall rules without specific targets should prohibit ingress from 0.0.0.0/0 to any portCompute Engine networks should have automatic subnetwork creation enabledProjects should prohibit default networksProjects should prohibit legacy networksVPC networks should all have Cloud DNS logging enabledGKE clusters should have 'Master authorized networks' set to 'Enabled'VPC subnets should all have VPC Flow Logs enabledVPC subnets should have Private Google Access enabledGKE clusters should not use default networkGKE clusters should have private nodes configuredGKE cluster subnetworks should all have Private Google Access enabledProjects should have log metric filters and alerts configured for VPC Network Firewall rule changesProjects should have log metric filters and alerts configured for VPC network changesProjects should have log metric filters and alerts configured for VPC network route changesFirewall rules should prohibit unrestricted RDP access from the internetFirewall rules should prohibit unrestricted SSH access from the internetFirewall rules should prohibit unrestricted TCP/UDP access from the internet to all ports
PR.IR-02: The organization's technology assets are protected from environmental threats. (8 controls)
Compute Engine instances should have Shielded VM enabled at launchGKE cluster shielded nodes should have integrity monitoring enabledGKE cluster shielded nodes should have secure boot enabledGKE clusters should have shielded nodes enabledCloud SQL instances should have automated backups configuredCloud Storage buckets used for exporting logs should have object versioning enabledCloud Storage buckets used for exporting logs should have retention policies enabledCloud Storage buckets used for exporting logs should use Bucket Lock
PR.IR-03: Mechanisms are implemented to achieve resilience requirements in normal and adverse situations. (12 controls)
Compute Engine instances should have Shielded VM enabled at launchGKE node pools should all have automatic node repair enabledGKE nodes should have automatic node upgrades enabledGKE cluster shielded nodes should have integrity monitoring enabledGKE cluster shielded nodes should have secure boot enabledGKE clusters should have shielded nodes enabledGKE clusters with less than three nodes should have auto upgrade enabledLog buckets should have retention policies configured using Bucket LockCloud SQL instances should have automated backups configuredCloud Storage buckets used for exporting logs should have object versioning enabledCloud Storage buckets used for exporting logs should have retention policies enabledCloud Storage buckets used for exporting logs should use Bucket Lock
PR.IR-04: Adequate resource capacity to ensure availability is maintained. (7 controls)
GKE node pools should all have automatic node repair enabledGKE nodes should have automatic node upgrades enabledGKE clusters with less than three nodes should have auto upgrade enabledCloud SQL instances should have automated backups configuredCloud Storage buckets used for exporting logs should have object versioning enabledCloud Storage buckets used for exporting logs should have retention policies enabledCloud Storage buckets used for exporting logs should use Bucket Lock
PR.PS-01: Configuration management practices are established and applied. (7 controls)
Compute Engine instances should all have OS Login enabled in the projectGKE clusters should have Binary Authorization enabledGKE cluster shielded nodes should have integrity monitoring enabledGKE cluster shielded nodes should have secure boot enabledGKE clusters should have shielded nodes enabledProjects should have log metric filters and alerts configured for Audit Configuration changesProjects should have log metric filters and alerts configured for Cloud SQL instance configuration changes
PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. (3 controls)
PR.PS-03: Hardware is maintained, replaced, and removed commensurate with risk. (3 controls)
PR.PS-04: Log records are generated and made available for continuous monitoring. (19 controls)
Firewall rules should have logging enabledHTTP(S) load balancers should have logging enabledVPC networks should all have Cloud DNS logging enabledVPC subnets should all have VPC Flow Logs enabledGKE clusters should have monitoring enabledLog buckets should have retention policies configured using Bucket LockProjects should have log metric filters and alerts configured for Audit Configuration changesProjects should have log metric filters and alerts configured for Custom Role changesProjects should have log metric filters and alerts configured for Custom Role changes, including undeleteProjects should have log metric filters and alerts configured for VPC Network Firewall rule changesProjects should have log metric filters and alerts configured for VPC network changesProjects should have log metric filters and alerts configured for VPC network route changesProjects should have log metric filters and alerts configured for project ownership assignments and changesProjects should have log metric filters and alerts configured for Cloud SQL instance configuration changesProjects should have log metric filters and alerts configured for Cloud Storage IAM permission changesProjects should have log sinks configured for all log entriesCloud Storage buckets used for exporting logs should have object versioning enabledCloud Storage buckets used for exporting logs should have retention policies enabledCloud Storage buckets used for exporting logs should use Bucket Lock
PR.PS-05: Installation and execution of unauthorized software are prevented. (3 controls)
PR.PS-06: Secure software development practices are integrated, and their performance is monitored throughout the software development life cycle. (2 controls)
RC.CO-03: Recovery activities and progress in restoring operational capabilities are communicated to designated internal and external stakeholders. (1 control)
RC.CO-04: Public updates on incident recovery are shared using approved methods and messaging. (1 control)
RC.RP-01: The recovery portion of the incident response plan is executed once initiated from the incident response process. (1 control)
RC.RP-02: Recovery actions are selected, scoped, prioritized, and performed. (3 controls)
RC.RP-03: The integrity of backups and other restoration assets is verified before using them for restoration. (3 controls)
RC.RP-04: Critical mission functions and cybersecurity risk management are considered to establish post-incident operational norms. (2 controls)
RC.RP-05: The integrity of restored assets is verified, systems and services are restored, and normal operating status is confirmed. (3 controls)
RC.RP-06: The end of incident recovery is declared based on criteria, and incident-related documentation is completed. (2 controls)
RS.AN-03: Analysis is performed to establish what has taken place during an incident and the root cause of the incident. (9 controls)
Projects should have Cloud Audit Logs properly configured across all services and all usersProjects should have log metric filters and alerts configured for Audit Configuration changesProjects should have log metric filters and alerts configured for Custom Role changesProjects should have log metric filters and alerts configured for VPC Network Firewall rule changesProjects should have log metric filters and alerts configured for VPC network changesProjects should have log metric filters and alerts configured for VPC network route changesProjects should have log metric filters and alerts configured for project ownership assignments and changesProjects should have log metric filters and alerts configured for Cloud SQL instance configuration changesProjects should have log metric filters and alerts configured for Cloud Storage IAM permission changes
RS.AN-06: Actions performed during an investigation are recorded, and the records' integrity and provenance are preserved. (2 controls)
RS.AN-07: Incident data and metadata are collected, and their integrity and provenance are preserved. (2 controls)
RS.AN-08: An incident's magnitude is estimated and validated. (9 controls)
Projects should have Cloud Audit Logs properly configured across all services and all usersProjects should have log metric filters and alerts configured for Audit Configuration changesProjects should have log metric filters and alerts configured for Custom Role changesProjects should have log metric filters and alerts configured for VPC Network Firewall rule changesProjects should have log metric filters and alerts configured for VPC network changesProjects should have log metric filters and alerts configured for VPC network route changesProjects should have log metric filters and alerts configured for project ownership assignments and changesProjects should have log metric filters and alerts configured for Cloud SQL instance configuration changesProjects should have log metric filters and alerts configured for Cloud Storage IAM permission changes
RS.CO-02: Internal and external stakeholders are notified of incidents. (1 control)
RS.CO-03: Information is shared with designated internal and external stakeholders. (1 control)
RS.MA-01: The incident response plan is executed in coordination with relevant third parties once an incident is declared. (1 control)
RS.MA-02: Incident reports are triaged and validated. (9 controls)
Projects should have Cloud Audit Logs properly configured across all services and all usersProjects should have log metric filters and alerts configured for Audit Configuration changesProjects should have log metric filters and alerts configured for Custom Role changesProjects should have log metric filters and alerts configured for VPC Network Firewall rule changesProjects should have log metric filters and alerts configured for VPC network changesProjects should have log metric filters and alerts configured for VPC network route changesProjects should have log metric filters and alerts configured for project ownership assignments and changesProjects should have log metric filters and alerts configured for Cloud SQL instance configuration changesProjects should have log metric filters and alerts configured for Cloud Storage IAM permission changes
RS.MA-03: Incidents are categorized and prioritized. (9 controls)
Projects should have Cloud Audit Logs properly configured across all services and all usersProjects should have log metric filters and alerts configured for Audit Configuration changesProjects should have log metric filters and alerts configured for Custom Role changesProjects should have log metric filters and alerts configured for VPC Network Firewall rule changesProjects should have log metric filters and alerts configured for VPC network changesProjects should have log metric filters and alerts configured for VPC network route changesProjects should have log metric filters and alerts configured for project ownership assignments and changesProjects should have log metric filters and alerts configured for Cloud SQL instance configuration changesProjects should have log metric filters and alerts configured for Cloud Storage IAM permission changes
RS.MA-04: Incidents are escalated or elevated as needed. (9 controls)
Projects should have log metric filters and alerts configured for Audit Configuration changesProjects should have log metric filters and alerts configured for Custom Role changesProjects should have log metric filters and alerts configured for VPC Network Firewall rule changesProjects should have log metric filters and alerts configured for VPC network changesProjects should have log metric filters and alerts configured for VPC network route changesProjects should have log metric filters and alerts configured for project ownership assignments and changesProjects should have log metric filters and alerts configured for Cloud SQL instance configuration changesProjects should have log metric filters and alerts configured for Cloud Storage IAM permission changesOrganizations should have Essential Contacts configured
RS.MA-05: The criteria for initiating incident recovery are applied. (9 controls)
Projects should have Cloud Audit Logs properly configured across all services and all usersProjects should have log metric filters and alerts configured for Audit Configuration changesProjects should have log metric filters and alerts configured for Custom Role changesProjects should have log metric filters and alerts configured for VPC Network Firewall rule changesProjects should have log metric filters and alerts configured for VPC network changesProjects should have log metric filters and alerts configured for VPC network route changesProjects should have log metric filters and alerts configured for project ownership assignments and changesProjects should have log metric filters and alerts configured for Cloud SQL instance configuration changesProjects should have log metric filters and alerts configured for Cloud Storage IAM permission changes
RS.MI-01: Incidents are contained. (9 controls)
Projects should have Cloud Audit Logs properly configured across all services and all usersProjects should have log metric filters and alerts configured for Audit Configuration changesProjects should have log metric filters and alerts configured for Custom Role changesProjects should have log metric filters and alerts configured for VPC Network Firewall rule changesProjects should have log metric filters and alerts configured for VPC network changesProjects should have log metric filters and alerts configured for VPC network route changesProjects should have log metric filters and alerts configured for project ownership assignments and changesProjects should have log metric filters and alerts configured for Cloud SQL instance configuration changesProjects should have log metric filters and alerts configured for Cloud Storage IAM permission changes
RS.MI-02: Incidents are eradicated. (9 controls)
Projects should have Cloud Audit Logs properly configured across all services and all usersProjects should have log metric filters and alerts configured for Audit Configuration changesProjects should have log metric filters and alerts configured for Custom Role changesProjects should have log metric filters and alerts configured for VPC Network Firewall rule changesProjects should have log metric filters and alerts configured for VPC network changesProjects should have log metric filters and alerts configured for VPC network route changesProjects should have log metric filters and alerts configured for project ownership assignments and changesProjects should have log metric filters and alerts configured for Cloud SQL instance configuration changesProjects should have log metric filters and alerts configured for Cloud Storage IAM permission changes
Related Frameworks
CIS GCP Benchmark v2.0.0 — 🟡 Medium overlap (47%)
CIS GCP Benchmark v4.0.0 — 🟡 Medium overlap (47%)
CIS GCP Benchmark v3.0.0 — 🟡 Medium overlap (46%)