> [!NOTE]
> Premium and Enterprise (Deprecated) [service tiers](https://docs.cloud.google.com/security-command-center/docs/service-tiers.md.txt)

> [!CAUTION]
> The Security Command Center Enterprise service tier will shut down on May 21, 2027. If your organization uses the Enterprise service tier, then the organization will automatically move to the Premium service tier on or after May 21, 2027. Contact your account representative or a [Google Cloud sales specialist](https://cloud.google.com/contact) if you have questions.

This document describes a threat finding type in Security Command Center. Threat findings are generated by
[threat detectors](https://docs.cloud.google.com/security-command-center/docs/concepts-security-sources.md.txt#threats) when they detect
a potential threat in your cloud resources. For a full list of available threat findings, see [Threat findings index](https://docs.cloud.google.com/security-command-center/docs/threat-findings-index.md.txt).

## Overview

Event Threat Detection examines audit logs to detect the IP filtering config has
been updated on a Cloud Storage bucket.

[Event Threat Detection](https://docs.cloud.google.com/security-command-center/docs/concepts-event-threat-detection-overview.md.txt) is the source of
this finding.

## How to respond

To respond to this finding, do the following:

### Step 1: Review finding details

1. Open the `Defense Evasion: GCS Bucket IP Filtering Modified` finding, as detailed in [Reviewing findings](https://docs.cloud.google.com/security-command-center/docs/how-to-investigate-threats.md.txt#reviewing_findings). The details panel for the finding opens to the **Summary** tab.
2. On the **Summary** tab, review the information in the following sections:
   - **What was detected** , especially the following fields:
     - **Description**: information about the detection
     - **Principal subject**: a user or service account that has successfully executed an action
   - **Affected resource**
     - **Resource display name**: the bucket in which the config has been updated.
   - **Related links** , especially the following fields:
     - **MITRE ATTACK method**: link to the MITRE ATT\&CK documentation.
     - **Logging URI** : link to open the **Logs Explorer**.

### Step 2: Research attack and response methods

Contact the owner of the service account or user account in the **Principal subject** field.
Confirm whether the legitimate owner conducted the action.

## What's next

- Learn [how to work with threat
  findings in Security Command Center](https://docs.cloud.google.com/security-command-center/docs/how-to-investigate-threats).
- Refer to the [Threat findings index](https://docs.cloud.google.com/security-command-center/docs/threat-findings-index.md.txt).
- Learn how to [review a
  finding](https://docs.cloud.google.com/security-command-center/docs/how-to-investigate-threats#reviewing_findings) through the Google Cloud console.
- Learn about the [services that
  generate threat findings](https://docs.cloud.google.com/security-command-center/docs/concepts-security-sources#threats).