Skip to main content

🛡️ Google Logging Log Metric Filter and Alerts for VPC Network Route Changes do not exist🟢

  • Contextual name: 🛡️ Log Metric Filter and Alerts for VPC Network Route Changes do not exist🟢
  • ID: /ce/ca/google/logging/vpc-network-route-changes-monitoring
  • Tags:
  • Policy Type: COMPLIANCE_POLICY
  • Policy Categories: SECURITY

Logic​

Similar Policies​

Description​

Open File

Description​

It is recommended that a metric filter and alarm be established for Virtual Private Cloud (VPC) network route changes.

Rationale​

Google Cloud Platform (GCP) routes define the paths network traffic takes from a VM instance to another destination. The other destination can be inside the organization VPC network (such as another VM) or outside of it. Every route consists of a destination and a next hop. Traffic whose destination IP is within the destination range is sent to the next hop for delivery.

Monitoring changes to route tables will help ensure that all VPC traffic flows through an expected path.

Impact​

Enabling of logging may result in your project being charged for the additional logs usage. These charges could be significant depending on the size of the organization.

Audit​

From Google Cloud Console​

Ensure that the prescribed Log metric is present:

  1. Go to Logging/Logs-based Metrics by visiting https://console.cloud.google.com/logs/metrics.
  2. In the User-defined Metrics section, ensure that at least one metric <Log_Metric_Name> is present with the filter text:

... see more

Remediation​

Open File

Remediation​

From Google Cloud Console​

Create the prescribed Log Metric:

  1. Go to Logging/Logs-based Metrics by visiting https://console.cloud.google.com/logs/metrics and click "CREATE METRIC".

  2. Click the down arrow symbol on the Filter Bar at the rightmost corner and select Convert to Advanced Filter

  3. Clear any text and add:

     resource.type="gce_route" 
     AND (protoPayload.methodName:"compute.routes.delete" 
     OR protoPayload.methodName:"compute.routes.insert")

  4. Click Submit Filter. Display logs appear based on the filter text entered by the user.

  5. In the Metric Editor menu on the right, fill out the name field. Set Units to 1 (default) and Type to Counter. This ensures that the log metric counts the number of log entries matching the user's advanced logs query.

  6. Click Create Metric.

Create the prescribed alert policy:

  1. Identify the newly created metric under the section User-defined Metrics at https://console.cloud.google.com/logs/metrics.
  2. Click the 3-dot icon in the rightmost column for the new metric and select Create alert from Metric. A new page displays.

... see more

policy.yaml​

Open File

Linked Framework Sections​

SectionSub SectionsInternal RulesPoliciesFlagsCompliance
💼 CIS GCP v1.2.0 → 💼 2.8 Ensure that the log metric filter and alerts exist for VPC network route changes - Level 1 (Automated)1no data
💼 CIS GCP v1.3.0 → 💼 2.8 Ensure That the Log Metric Filter and Alerts Exist for VPC Network Route Changes - Level 1 (Automated)1no data
💼 CIS GCP v2.0.0 → 💼 2.8 Ensure That the Log Metric Filter and Alerts Exist for VPC Network Route Changes - Level 2 (Automated)1no data
💼 CIS GCP v3.0.0 → 💼 2.8 Ensure That the Log Metric Filter and Alerts Exist for VPC Network Route Changes - Level 2 (Automated)1no data
💼 Cloudaware Framework → 💼 Logging and Monitoring Configuration65no data
💼 FedRAMP High Security Controls → 💼 AU-2 Event Logging (L)(M)(H)17no data
💼 FedRAMP High Security Controls → 💼 AU-7 Audit Record Reduction and Report Generation (M)(H)118no data
💼 FedRAMP High Security Controls → 💼 AU-12 Audit Record Generation (L)(M)(H)265no data
💼 FedRAMP Low Security Controls → 💼 AU-2 Event Logging (L)(M)(H)17no data
💼 FedRAMP Low Security Controls → 💼 AU-12 Audit Record Generation (L)(M)(H)65no data
💼 FedRAMP Moderate Security Controls → 💼 AU-2 Event Logging (L)(M)(H)17no data
💼 FedRAMP Moderate Security Controls → 💼 AU-7 Audit Record Reduction and Report Generation (M)(H)118no data
💼 FedRAMP Moderate Security Controls → 💼 AU-12 Audit Record Generation (L)(M)(H)65no 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 sources50no 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 events145no data
💼 NIST CSF v2.0 → 💼 DE.CM-03: Personnel activity and technology usage are monitored to find potentially adverse events85no data
💼 NIST CSF v2.0 → 💼 DE.CM-09: Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events142no 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 Logging417no data
💼 NIST SP 800-53 Revision 5 → 💼 AU-7 Audit Record Reduction and Report Generation2118no data
💼 NIST SP 800-53 Revision 5 → 💼 AU-12 Audit Record Generation44765no 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.7628no 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.9no data
💼 PCI DSS v4.0.1 → 💼 10.2.1 Audit logs are enabled and active for all system components and cardholder data.727no 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.9no data
💼 PCI DSS v4.0 → 💼 10.2.1 Audit logs are enabled and active for all system components and cardholder data.7127no 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