Google Cloud Compliance ControlsGoogle Cloud Logging
Projects should have Cloud Audit Logs properly configured across all services and all users
Cloud Audit Logging is configured to track all admin activities and read, write access to user data. The project has Cloud Audit Logs configured for services and principals, including ADMIN_READ, DATA_READ, DATA_WRITE.
What this control checks
Checks the project's audit logging setup for every service and every user
Framework mappings
The clauses this control is mapped to in each framework.
- CC7.2: The entity monitors system components and the operation of those components for anomalies that are indicative of malicious acts, natural disasters, and errors affecting the entity's ability to meet its objectives; anomalies are analyzed to determine whether they represent security events.
- 1.5.1 Security controls are implemented on any computing devices, including company- and employee-owned devices, that connect to both untrusted networks
- 5.3.4: Anti-malware mechanisms and processes are active, maintained, and monitored.
- 7.2.1: Access to system components and data is appropriately defined and assigned.
- 7.2.2: Access to system components and data is appropriately defined and assigned.
- 7.2.5: Access to system components and data is appropriately defined and assigned.
26 more clauses
- 7.3.1: Access to system components and data is managed via an access control system(s).
- 7.3.2: Access to system components and data is managed via an access control system(s).
- 7.3.3: Access to system components and data is managed via an access control system(s).
- 8.2.8: If a user session has been idle for more than 15 minutes, the user is required to re-authenticate to re-activate the terminal or session
- 10.2.1: Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events.
- 10.2.1.1: Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events.
- 10.2.1.2: Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events.
- 10.2.1.3: Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events.
- 10.2.1.4: Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events.
- 10.2.1.5: Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events.
- 10.2.1.6: Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events.
- 10.2.1.7: Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events.
- 10.2.2: Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events.
- 10.3.1: Audit logs are protected from destruction and unauthorized modifications.
- 10.3.2: Audit logs are protected from destruction and unauthorized modifications.
- 10.3.3: Audit log files, including those for externalfacing technologies, are promptly backed up to a secure, central, internal log server(s) or other media that is difficult to modify
- 10.3.4: File integrity monitoring or change-detection mechanisms is used on audit logs to ensure that existing log data cannot be changed without generating alerts
- 10.4.1.1: Audit logs are reviewed to identify anomalies or suspicious activity.
- 10.5.1: Retain audit log history for at least 12 months, with at least the most recent three months immediately available for analysis
- 10.6.3: Time-synchronization mechanisms support consistent time settings across all systems.
- 11.5.2: A change-detection mechanism (for example, file integrity monitoring tools) is deployed
- 11.6.1: Unauthorized changes on payment pages are detected and responded to.
- 12.10.5: The security incident response plan includes monitoring and responding to alerts from security monitoring systems
- A1.2.1: Multi-tenant service providers facilitate logging and incident response for all customers.
- A3.3.1: PCI DSS is incorporated into business-as-usual (BAU) activities.
- A3.5.1: Suspicious events are identified and responded to.
- A.8.16 Monitoring activities
- 3 Incident handling
- 7 Policies and procedures to assess the effectiveness of cybersecurity risk-management measures
- 11 Access control
- AU-6 Audit Record Review, Analysis And Reporting
- AU-7 Audit Record Reduction And Report Generation
NIST Cybersecurity Framework v2.0
- DE.AE-02: Potentially adverse events are analyzed to better understand associated activities.
- DE.AE-04: The estimated impact and scope of adverse events are understood.
- DE.CM-03
- DE.CM-06
- DE.CM-09
32 more clauses
- GV.OV-01: Cybersecurity risk management strategy outcomes are reviewed to inform and adjust strategy and direction.
- GV.OV-02: The cybersecurity risk management strategy is reviewed and adjusted to ensure coverage of organizational requirements and risks.
- GV.OV-03: Organizational cybersecurity risk management performance is evaluated and reviewed for adjustments needed.
- GV.PO-01: Policy for managing cybersecurity risks is established based on organizational context, cybersecurity strategy, and priorities and is communicated and enforced.
- GV.PO-02: Policy for managing cybersecurity risks is reviewed, updated, communicated, and enforced to reflect changes in requirements, threats, technology, and organizational mission.
- GV.RM-03: Cybersecurity risk management activities and outcomes are included in enterprise risk management processes.
- GV.RM-06: A standardized method for calculating, documenting, categorizing, and prioritizing cybersecurity risks is established and communicated.
- GV.RM-07: Strategic opportunities (i.e., positive risks) are characterized and are included in organizational cybersecurity risk discussions.
- GV.RR-01: Organizational leadership is responsible and accountable for cybersecurity risk and fosters a culture that is risk-aware, ethical, and continually improving.
- GV.RR-03: Adequate resources are allocated commensurate with the cybersecurity risk strategy, roles, responsibilities, and policies.
- GV.SC-01: A cybersecurity supply chain risk management program, strategy, objectives, policies, and processes are established and agreed to by organizational stakeholders.
- GV.SC-03: Cybersecurity supply chain risk management is integrated into cybersecurity and enterprise risk management, risk assessment, and improvement processes.
- 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.
- GV.SC-08: Relevant suppliers and other third parties are included in incident planning, response, and recovery activities.
- 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.
- GV.SC-10: Cybersecurity supply chain risk management plans include provisions for activities that occur after the conclusion of a partnership or service agreement.
- ID.AM-02
- ID.AM-04: Inventories of services provided by suppliers are maintained.
- ID.IM-01: Improvements are identified from evaluations.
- ID.IM-02
- ID.IM-03: Improvements are identified from execution of operational processes, procedures, and activities.
- ID.RA-10: Critical suppliers are assessed prior to acquisition.
- RC.RP-06
- RS.AN-03: Analysis is performed to establish what has taken place during an incident and the root cause of the incident.
- RS.AN-06: Actions performed during an investigation are recorded, and the records' integrity and provenance are preserved.
- RS.AN-07
- RS.AN-08
- RS.MA-02: Incident reports are triaged and validated.
- RS.MA-03: Incidents are categorized and prioritized.
- RS.MA-05: The criteria for initiating incident recovery are applied.
- RS.MI-01: Incidents are contained.
- RS.MI-02
- 2.1 Ensure That Cloud Audit Logging Is Configured Properly
- 2.1 Ensure That Cloud Audit Logging Is Configured Properly
- AM-01.01AC The information collected about assets is considered in logging and monitoring applications to identify the impact on cloud services and functions in case of events that could lead to a breach of protection objectives, and to support information provided to affected cloud service...
- AM-09.03AC Logging and monitoring applications take the asset protection needs into account in order to inform the responsible stakeholder of events that could lead to a violation of the protection goals, so that the necessary measures are taken with an appropriate priority.
- DEV-08.02B The configuration of these system components ensures that all changes to system components in the production environment are recorded and can be traced back to the individuals or system components contributing to their development, deployment or implementation.
- IAM-03.01AC The cloud service provider monitors the context of authentication attempts, e.g. IP addresses, the date and time or the device used, and flags suspicious events to authorised persons, as relevant.
- IAM-06.04B Activities of users with privileged access rights are logged in order to detect any misuse of privileged access in suspicious cases.
16 more clauses
- IAM-07.04B Unless contractually agreed otherwise, the information contains the cause, time, duration, geographic location, type and scope of the access, as well as the retention time of other data generated during access, such as logs or copies containing cloud service customer data. The...
- INQ-04.01AC The cloud service provider monitors the access and activities performed by or on behalf of investigators as determined by the process described in INQ-01.
- OIS-05.01B The cloud service provider collects information from selected internal and external sources to gain a comprehensive view of the threat landscape that lead to cybersecurity risks.
- OPS-11.02AC Cloud service derived data, including log data, is taken into consideration in regulatory compliance assessments.
- OPS-12.01B The requirements for the logging and monitoring of events and for the secure handling of cloud service derived data and cloud service provider data are implemented by technically supported procedures with regard to the following restrictions: - Access only for authorised users and...
- OPS-13.01B The cloud service provider integrates relevant log data (cloud service derived data and cloud service provider data) into a Security Information and Event Management (SIEM) system to establish a seamless connection between logging, monitoring, and security incident management.
- OPS-13.02B The SIEM system can be deployed within the cloud environment or externally and shall include the following capabilities: - Standardisation of log data;- Automated analysis to identify and correlate potential security incidents;- Capabilities to detect unusual behaviour and potential...
- OPS-15.01B The log data generated (cloud service derived data and cloud service provider data) allows an unambiguous identification of user accesses at tenant level to support (forensic) analysis in the event of an incident.
- OPS-15.02B Each logged event shall include a time/date stamp to ensure accurate and traceable records.
- OPS-15.03B The cloud service provider is able to support forensic analysis of incidents and to retain a chain of evidence. This implies that the cloud service provider capture the state of infrastructure components and network communication during security events.
- OPS-26.01AS System components in the cloud service provider's area of responsibility are automatically monitored for compliance with hardening specifications.
- OPS-26.05B The cloud service provider implements monitoring measures to ensure system components comply with hardening specifications.
- PSS-04.01B The cloud service provided is equipped with error handling and logging mechanisms for system components under the responsibility of the cloud service customer. These enable cloud users to obtain security-related information about the security status of the cloud service as well as the...
- PSS-04.05B If the cloud service customer is responsible for the activation or type and scope of logging, the cloud service provider has provide appropriate logging capabilities.
- SIM-01.02AC In addition, there are analysis plans for typical security incidents and an evaluation methodology which ensures the collected information does not lose its evidential value in any subsequent legal assessment.
- SSO-05.01AC The procedures for monitoring compliance with the requirements are supplemented by automatic procedures relating to the following aspects: - Configuration of system components;- Performance and availability of system components;- Response time to malfunctions and security incidents;...
- 2.1 Ensure that Cloud Audit Logging is configured properly across all services and all users from a project
- 2.1 Ensure that Cloud Audit Logging is configured properly across all services and all users from a project
- 2.1 Ensure that Cloud Audit Logging is configured properly
- 164.308(a)(1)(ii) Implementation specifications
- 164.312(b) Audit controls
NIST Cybersecurity Framework v1.0
- DE.AE-2: Detected events are analyzed to understand attack targets and methods.
- PR.PT-1: Audit/log records are determined, documented, implemented, and reviewed in accordance with policy.
- RS.AN-1: Notifications from detection systems are investigated.
- 10.1 Implement audit trails to link all access to system components to each individual user
- Through interviews of responsible personnel, observation of audit logs, and examination of audit log settings
Tool mappings
Use these identifiers to cross-reference this control across tools, reports, and evidence.
- Compliance.tf Control:
audit_logging_configured_for_all_service - Powerpipe Control:
gcp_compliance.control.audit_logging_configured_for_all_service - Prowler Check:
iam_audit_logs_enabled
Last reviewed: 2026-10-09