Skip to main content

💼 2.5 Ensure That the Log Metric Filter and Alerts Exist for Audit Configuration Changes - Level 1 (Automated)

  • ID: /frameworks/cis-gcp-v1.3.0/02/05

Description

Google Cloud Platform (GCP) services write audit log entries to the Admin Activity and Data Access logs to help answer the questions of, "who did what, where, and when?" within GCP projects.

Cloud audit logging records information includes the identity of the API caller, the time of the API call, the source IP address of the API caller, the request parameters, and the response elements returned by GCP services. Cloud audit logging provides a history of GCP API calls for an account, including API calls made via the console, SDKs, command-line tools, and other GCP services.

Similar

  • Sections
    • /frameworks/cis-gcp-v2.0.0/02/05
    • /frameworks/cis-gcp-v1.2.0/02/05
  • Internal
    • ID: dec-c-7f964e88

Similar Sections (Take Policies From)

SectionSub SectionsInternal RulesPoliciesFlagsCompliance
💼 CIS GCP v1.2.0 → 💼 2.5 Ensure that the log metric filter and alerts exist for Audit Configuration changes - Level 1 (Automated)1no data
💼 CIS GCP v2.0.0 → 💼 2.5 Ensure That the Log Metric Filter and Alerts Exist for Audit Configuration Changes - Level 1 (Automated)1no data

Similar Sections (Give Policies To)

SectionSub SectionsInternal RulesPoliciesFlagsCompliance
💼 CIS GCP v1.2.0 → 💼 2.5 Ensure that the log metric filter and alerts exist for Audit Configuration changes - Level 1 (Automated)1no data
💼 CIS GCP v2.0.0 → 💼 2.5 Ensure That the Log Metric Filter and Alerts Exist for Audit Configuration Changes - Level 1 (Automated)1no data

Sub Sections

SectionSub SectionsInternal RulesPoliciesFlagsCompliance

Policies (1)

PolicyLogic CountFlagsCompliance
🛡️ Google Logging Log Metric Filter and Alerts for Audit Configuration Changes do not exist🟢1🟢 x6no data