🛡️ Google Logging Log Metric Filter and Alerts Cloud Storage IAM Permission Changes do not exist🟢

• Contextual name: 🛡️ Log Metric Filter and Alerts Cloud Storage IAM Permission Changes do not exist🟢
• ID: /ce/ca/google/logging/iam-permission-changes-monitoring
• Tags:
  • 🟢 Policy with categories
  • 🟢 Policy with type
  • 🟢 Production policy
• Policy Type: COMPLIANCE_POLICY
• Policy Categories: SECURITY

Logic

• 🧠 prod.logic.yaml🟢
  • 📗 Google Project
  • 🔌 Google Project - object.extracts.yaml
  • 🔌 Google Monitoring Alert Policy - object.extracts.yaml
  • 🔌 Google Logging Log Metric - object.extracts.yaml
  • 🧪 test-data.json

Similar Policies

• Cloud Conformity: Enable Monitoring for Bucket Permission Changes

Description

Open File

Description

It is recommended that a metric filter and alarm be established for Cloud Storage Bucket IAM changes.

Rationale

Monitoring changes to cloud storage bucket permissions may reduce the time needed to detect and correct permissions on sensitive cloud storage buckets and objects inside the bucket.

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 the prescribed log metric is present:

1. For each project that contains cloud storage buckets, go to Logging/Logs-based Metrics by visiting https://console.cloud.google.com/logs/metrics.

2. In the User-defined Metrics section, ensure at least one metric <Log_Metric_Name> is present with the filter text:

        resource.type="gcs_bucket" 
        AND protoPayload.methodName="storage.setIamPermissions"

   Ensure that the prescribed alerting policy is present:

3. Go to Alerting by visiting https://console.cloud.google.com/monitoring/alerting.

... 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="gcs_bucket" 
        AND protoPayload.methodName="storage.setIamPermissions"

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

5. In the Metric Editor menu on 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 appears.

... see more

policy.yaml

Open File

Linked Framework Sections

Section	Sub Sections	Internal Rules	Policies	Flags	Compliance
💼 CIS GCP v1.2.0 → 💼 2.10 Ensure that the log metric filter and alerts exist for Cloud Storage IAM permission changes - Level 1 (Automated)			1		no data
💼 CIS GCP v1.3.0 → 💼 2.10 Ensure That the Log Metric Filter and Alerts Exist for Cloud Storage IAM Permission Changes - Level 1 (Automated)			1		no data
💼 CIS GCP v2.0.0 → 💼 2.10 Ensure That the Log Metric Filter and Alerts Exist for Cloud Storage IAM Permission Changes - Level 2 (Automated)			1		no data
💼 CIS GCP v3.0.0 → 💼 2.10 Ensure That the Log Metric Filter and Alerts Exist for Cloud Storage IAM Permission Changes - Level 2 (Automated)			1		no data
💼 Cloudaware Framework → 💼 Logging and Monitoring Configuration			60		no data