Skip to main content

🛡️ Google GCE Firewall Rule logging is disabled🟢

Stats​

not available

Logic​

Description​

Open File

Description​

This policy identifies Google GCE Firewall Rules that do not have logging enabled. Enabling firewall rule logging allows you to audit, verify, and analyze the effects of your firewall rules within Google Cloud VPC networks.

Rationale​

Firewall rule logging provides visibility into the network traffic that is allowed or denied by your firewall rules. Capturing these logs is critical for security auditing, monitoring unauthorized access attempts, and troubleshooting connectivity issues. Without logging, it becomes difficult to perform forensic analysis during security incidents or to validate that firewall rules are functioning as intended.

Impact​

Enabling logging may result in additional costs for log storage and processing within Cloud Logging.

Audit​

This policy flags a Google GCE Firewall Rule as INCOMPLIANT if its Log State is set to Disabled.

Remediation​

Open File

Remediation​

Enable Firewall Rule Logging​

Enabling logging on firewall rules allows you to capture traffic information for auditing, monitoring, and troubleshooting purposes.

From Google Cloud CLI​
gcloud compute firewall-rules update {{firewall-rule-name}} \
    --enable-logging
Considerations​

After enabling logging, traffic matching this rule will be captured in Cloud Logging, which may incur additional costs.

policy.yaml​

Open File

Linked Framework Sections​

SectionSub SectionsInternal RulesPoliciesFlagsCompliance
💼 Cloudaware Framework → 💼 Logging and Monitoring Configuration79no data
💼 ISO/IEC 27001:2013 → 💼 A.13.1.1 Network controls65no data
💼 NIST CSF v1.1 → 💼 DE.AE-1: A baseline of network operations and expected data flows for users and systems is established and managed1179no data
💼 NIST CSF v1.1 → 💼 DE.AE-2: Detected events are analyzed to understand attack targets and methods2126no data
💼 NIST CSF v1.1 → 💼 DE.AE-3: Event data are collected and correlated from multiple sources and sensors2140no data
💼 NIST CSF v1.1 → 💼 DE.AE-4: Impact of events is determined1415no data
💼 NIST CSF v1.1 → 💼 DE.CM-1: The network is monitored to detect potential cybersecurity events2165no data
💼 NIST CSF v1.1 → 💼 DE.CM-5: Unauthorized mobile code is detected1213no data
💼 NIST CSF v1.1 → 💼 DE.CM-6: External service provider activity is monitored to detect potential cybersecurity events78no data
💼 NIST CSF v1.1 → 💼 DE.CM-7: Monitoring for unauthorized personnel, connections, devices, and software is performed2126no data
💼 NIST CSF v1.1 → 💼 DE.DP-2: Detection activities comply with all applicable requirements78no data
💼 NIST CSF v1.1 → 💼 DE.DP-3: Detection processes are tested1415no data
💼 NIST CSF v1.1 → 💼 DE.DP-4: Event detection information is communicated3235no data
💼 NIST CSF v1.1 → 💼 DE.DP-5: Detection processes are continuously improved1417no data
💼 NIST CSF v1.1 → 💼 ID.RA-1: Asset vulnerabilities are identified and documented1417no data
💼 NIST CSF v1.1 → 💼 PR.AC-3: Remote access is managed66no data
💼 NIST CSF v1.1 → 💼 PR.AC-5: Network integrity is protected (e.g., network segregation, network segmentation)1184no data
💼 NIST CSF v1.1 → 💼 PR.DS-2: Data-in-transit is protected1797no data
💼 NIST CSF v1.1 → 💼 PR.DS-5: Protections against data leaks are implemented89152no data
💼 NIST CSF v1.1 → 💼 PR.IP-8: Effectiveness of protection technologies is shared78no data
💼 NIST CSF v1.1 → 💼 PR.PT-4: Communications and control networks are protected1184no data
💼 NIST CSF v1.1 → 💼 RS.AN-1: Notifications from detection systems are investigated2126no data
💼 NIST CSF v1.1 → 💼 RS.CO-3: Information is shared consistent with response plans1718no data
💼 NIST CSF v2.0 → 💼 DE.AE-02: Potentially adverse events are analyzed to better understand associated activities53no data
💼 NIST CSF v2.0 → 💼 DE.AE-03: Information is correlated from multiple sources68no data
💼 NIST CSF v2.0 → 💼 DE.AE-04: The estimated impact and scope of adverse events are understood15no data
💼 NIST CSF v2.0 → 💼 DE.AE-06: Information on adverse events is provided to authorized staff and tools35no data
💼 NIST CSF v2.0 → 💼 DE.AE-07: Cyber threat intelligence and other contextual information are integrated into the analysis40no data
💼 NIST CSF v2.0 → 💼 DE.CM-01: Networks and network services are monitored to find potentially adverse events187no data
💼 NIST CSF v2.0 → 💼 DE.CM-03: Personnel activity and technology usage are monitored to find potentially adverse events107no data
💼 NIST CSF v2.0 → 💼 DE.CM-06: External service provider activities and services are monitored to find potentially adverse events53no data
💼 NIST CSF v2.0 → 💼 DE.CM-09: Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events185no data
💼 NIST CSF v2.0 → 💼 ID.AM-03: Representations of the organization's authorized network communication and internal and external network data flows are maintained128no data
💼 NIST CSF v2.0 → 💼 ID.IM-02: Improvements are identified from security tests and exercises, including those done in coordination with suppliers and relevant third parties63no data
💼 NIST CSF v2.0 → 💼 ID.IM-03: Improvements are identified from execution of operational processes, procedures, and activities63no data
💼 NIST CSF v2.0 → 💼 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded48no data
💼 NIST CSF v2.0 → 💼 PR.AA-03: Users, services, and hardware are authenticated102no data
💼 NIST CSF v2.0 → 💼 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 duties199no data
💼 NIST CSF v2.0 → 💼 PR.AA-06: Physical access to assets is managed, monitored, and enforced commensurate with risk84no data
💼 NIST CSF v2.0 → 💼 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected248no data
💼 NIST CSF v2.0 → 💼 PR.DS-02: The confidentiality, integrity, and availability of data-in-transit are protected219no data
💼 NIST CSF v2.0 → 💼 PR.DS-10: The confidentiality, integrity, and availability of data-in-use are protected249no data
💼 NIST CSF v2.0 → 💼 PR.IR-01: Networks and environments are protected from unauthorized logical access and usage165no data
💼 NIST CSF v2.0 → 💼 RS.CO-02: Internal and external stakeholders are notified of incidents33no data
💼 NIST CSF v2.0 → 💼 RS.CO-03: Information is shared with designated internal and external stakeholders19no data
💼 NIST CSF v2.0 → 💼 RS.MA-02: Incident reports are triaged and validated27no data
💼 NIST SP 800-53 Revision 4 → 💼 SI-4 INFORMATION SYSTEM MONITORING241no data
💼 PCI DSS v3.2.1 → 💼 10.1 Implement audit trails to link all access to system components to each individual user.58no data
💼 PCI DSS v3.2.1 → 💼 10.2 Implement automated audit trails for all system components.7733no 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 → 💼 10.2.1 Audit logs are enabled and active for all system components and cardholder data.7132no data