Skip to main content

🛡️ Google HTTP(S) Load Balancer Logging is not enabled🟢

Logic​

Similar Policies​

Description​

Open File

Description​

Logging on an HTTPS load balancer records network traffic and its destination.

Rationale​

Logging allows you to view HTTPS network traffic to your web applications.

Impact​

On high-use systems with a high sample rate, log files may grow quickly. Ensure the sample rate is set appropriately so that storage costs remain reasonable.

Audit​

From Google Cloud Console​
  1. From Google Cloud home, open the Navigation Menu in the top left.
  2. Under the Networking heading, select Network services.
  3. Select the HTTPS load balancer you want to audit.
  4. Select Edit, then Backend Configuration.
  5. Select Edit on the corresponding backend service.
  6. Ensure that Enable Logging is selected. Also ensure that Sample Rate is set to an appropriate level for your needs.
From Google Cloud CLI​

  1. Run the following command:

    gcloud compute backend-services describe {{service-name}}

  2. Ensure that enable-logging is enabled and sample rate is set to your desired level.

Default Value​

By default, logging for HTTPS load balancing is disabled. When logging is enabled, the default sample rate is 1.0 (100%). Ensure this value fits your organization’s needs to avoid high storage costs.

... see more

Remediation​

Open File

Remediation​

From Google Cloud Console​

  1. From Google Cloud home, open the Navigation Menu in the top left.
  2. Under the Networking heading, select Network services.
  3. Select the HTTPS load balancer you want to update.
  4. Select Edit, then Backend Configuration.
  5. Select Edit on the corresponding backend service.
  6. Click Enable Logging.
  7. Set Sample Rate to a desired value. This is a percentage as a decimal point. 1.0 is 100%.

From Google Cloud CLI​

  1. Run the following command:

    gcloud compute backend-services update {{service-name}} \
        --region={{region}} \
        --enable-logging \
        --logging-sample-rate={{percentage-as-a-decimal}}

policy.yaml​

Open File

Linked Framework Sections​

SectionSub SectionsInternal RulesPoliciesFlagsCompliance
💼 CIS GCP v2.0.0 → 💼 2.16 Ensure Logging is enabled for HTTP(S) Load Balancer - Level 2 (Automated)1no data
💼 CIS GCP v3.0.0 → 💼 2.16 Ensure Logging is enabled for HTTP(S) Load Balancer - Level 2 (Automated)1no data
💼 Cloudaware Framework → 💼 Logging and Monitoring Configuration77no data
💼 FedRAMP High Security Controls → 💼 AU-2 Event Logging (L)(M)(H)26no data
💼 FedRAMP High Security Controls → 💼 AU-7 Audit Record Reduction and Report Generation (M)(H)119no data
💼 FedRAMP High Security Controls → 💼 AU-12 Audit Record Generation (L)(M)(H)273no data
💼 FedRAMP Low Security Controls → 💼 AU-2 Event Logging (L)(M)(H)26no data
💼 FedRAMP Low Security Controls → 💼 AU-12 Audit Record Generation (L)(M)(H)73no data
💼 FedRAMP Moderate Security Controls → 💼 AU-2 Event Logging (L)(M)(H)26no data
💼 FedRAMP Moderate Security Controls → 💼 AU-7 Audit Record Reduction and Report Generation (M)(H)119no data
💼 FedRAMP Moderate Security Controls → 💼 AU-12 Audit Record Generation (L)(M)(H)73no data
💼 ISO/IEC 27001:2022 → 💼 8.15 Logging1834no data
💼 ISO/IEC 27001:2022 → 💼 8.20 Networks security514no data
💼 NIST CSF v1.1 → 💼 DE.AE-3: Event data are collected and correlated from multiple sources and sensors1838no data
💼 NIST CSF v1.1 → 💼 PR.PT-1: Audit/log records are determined, documented, implemented, and reviewed in accordance with policy1633no data
💼 NIST CSF v2.0 → 💼 DE.AE-03: Information is correlated from multiple sources65no data
💼 NIST CSF v2.0 → 💼 DE.AE-07: Cyber threat intelligence and other contextual information are integrated into the analysis38no data
💼 NIST CSF v2.0 → 💼 DE.CM-01: Networks and network services are monitored to find potentially adverse events180no data
💼 NIST CSF v2.0 → 💼 DE.CM-03: Personnel activity and technology usage are monitored to find potentially adverse events100no data
💼 NIST CSF v2.0 → 💼 DE.CM-09: Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events181no data
💼 NIST CSF v2.0 → 💼 RS.AN-03: Analysis is performed to establish what has taken place during an incident and the root cause of the incident17no data
💼 NIST CSF v2.0 → 💼 RS.AN-06: Actions performed during an investigation are recorded, and the records' integrity and provenance are preserved18no data
💼 NIST CSF v2.0 → 💼 RS.AN-07: Incident data and metadata are collected, and their integrity and provenance are preserved18no data
💼 NIST SP 800-53 Revision 5 → 💼 AU-2 Event Logging426no data
💼 NIST SP 800-53 Revision 5 → 💼 AU-7 Audit Record Reduction and Report Generation2119no data
💼 NIST SP 800-53 Revision 5 → 💼 AU-12 Audit Record Generation44773no data
💼 PCI DSS v3.2.1 → 💼 5.2 Ensure that all anti-virus mechanisms are maintained.9no data
💼 PCI DSS v3.2.1 → 💼 6.6 For public-facing web applications, address new threats and vulnerabilities on an ongoing basis and ensure these applications are protected against known attacks.11no data
💼 PCI DSS v3.2.1 → 💼 10.2 Implement automated audit trails for all system components.7633no data
💼 PCI DSS v3.2.1 → 💼 10.2.1 All individual user accesses to cardholder data.414no data
💼 PCI DSS v3.2.1 → 💼 10.2.2 All actions taken by any individual with root or administrative privileges.16no data
💼 PCI DSS v3.2.1 → 💼 10.2.3 Access to all audit trails.9no data
💼 PCI DSS v3.2.1 → 💼 10.2.4 Invalid logical access attempts.414no data
💼 PCI DSS v3.2.1 → 💼 10.2.5 Use of and changes to identification and authentication mechanisms.116no data
💼 PCI DSS v3.2.1 → 💼 10.2.6 Initialization, stopping, or pausing of the audit logs.9no data
💼 PCI DSS v3.2.1 → 💼 10.3 Record audit trail entries for all system components for each event.610no data
💼 PCI DSS v4.0.1 → 💼 5.3.1 The anti-malware solution(s) is kept current via automatic updates.9no data
💼 PCI DSS v4.0.1 → 💼 5.3.2 The anti-malware solution performs periodic scans and active or real-time scans or performs continuous behavioral analysis of systems or processes.19no data
💼 PCI DSS v4.0.1 → 💼 5.3.4 Audit logs for the anti-malware solution(s) are enabled and retained.9no data
💼 PCI DSS v4.0.1 → 💼 6.4.1 For public-facing web applications, new threats and vulnerabilities are addressed on an ongoing basis and these applications are protected against known attacks.11no data
💼 PCI DSS v4.0.1 → 💼 6.4.2 For public-facing web applications, an automated technical solution is deployed that continually detects and prevents web-based attacks.10no data
💼 PCI DSS v4.0.1 → 💼 10.2.1 Audit logs are enabled and active for all system components and cardholder data.732no data
💼 PCI DSS v4.0.1 → 💼 10.2.1.1 Audit logs capture all individual user access to cardholder data.14no data
💼 PCI DSS v4.0.1 → 💼 10.2.1.2 Audit logs capture all actions taken by any individual with administrative access, including any interactive use of application or system accounts.16no data
💼 PCI DSS v4.0.1 → 💼 10.2.1.3 Audit logs capture all access to audit logs.9no data
💼 PCI DSS v4.0.1 → 💼 10.2.1.4 Audit logs capture all invalid logical access attempts.14no data
💼 PCI DSS v4.0.1 → 💼 10.2.1.5 Audit logs capture all changes to identification and authentication credentials.16no data
💼 PCI DSS v4.0.1 → 💼 10.2.1.6 Audit logs capture all initialization of new audit logs, starting, stopping, or pausing of the existing audit logs.9no data
💼 PCI DSS v4.0.1 → 💼 10.2.1.7 Audit logs capture all creation and deletion of system-level objects.9no data
💼 PCI DSS v4.0.1 → 💼 10.2.2 Audit logs record the described details for each auditable event.9no data
💼 PCI DSS v4.0 → 💼 5.3.1 The anti-malware solution(s) is kept current via automatic updates.9no data
💼 PCI DSS v4.0 → 💼 5.3.2 The anti-malware solution performs periodic scans and active or real-time scans or performs continuous behavioral analysis of systems or processes.19no data
💼 PCI DSS v4.0 → 💼 5.3.4 Audit logs for the anti-malware solution(s) are enabled and retained.9no data
💼 PCI DSS v4.0 → 💼 6.4.1 For public-facing web applications, new threats and vulnerabilities are addressed on an ongoing basis and these applications are protected against known attacks.11no data
💼 PCI DSS v4.0 → 💼 6.4.2 For public-facing web applications, an automated technical solution is deployed that continually detects and prevents web-based attacks.10no data
💼 PCI DSS v4.0 → 💼 10.2.1 Audit logs are enabled and active for all system components and cardholder data.7132no data
💼 PCI DSS v4.0 → 💼 10.2.1.1 Audit logs capture all individual user access to cardholder data.114no data
💼 PCI DSS v4.0 → 💼 10.2.1.2 Audit logs capture all actions taken by any individual with administrative access, including any interactive use of application or system accounts.16no data
💼 PCI DSS v4.0 → 💼 10.2.1.3 Audit logs capture all access to audit logs.9no data
💼 PCI DSS v4.0 → 💼 10.2.1.4 Audit logs capture all invalid logical access attempts.114no data
💼 PCI DSS v4.0 → 💼 10.2.1.5 Audit logs capture all changes to identification and authentication credentials.16no data
💼 PCI DSS v4.0 → 💼 10.2.1.6 Audit logs capture all initialization of new audit logs, starting, stopping, or pausing of the existing audit logs.9no data
💼 PCI DSS v4.0 → 💼 10.2.1.7 Audit logs capture all creation and deletion of system-level objects.9no data
💼 PCI DSS v4.0 → 💼 10.2.2 Audit logs record the described details for each auditable event.9no data