# Manage alerts and IOC matches

Supported in:

> [!CAUTION]
> **Caution:** The Ingestion API is [deprecated](https://docs.cloud.google.com/chronicle/docs/deprecations) and will be discontinued on July 20, 2027. To ingest logs into Google SecOps, use the [Chronicle API](https://docs.cloud.google.com/chronicle/docs/reference/rest) instead. For details on how to migrate, see [Migrate from legacy SIEM API to Chronicle API](https://docs.cloud.google.com/chronicle/docs/administration/migrate-from-legacy-api-to-chronicle-api).

The **Alerts \& IOCs** page displays all the alerts and Indicators of Compromise (IOCs) that are impacting your enterprise.

- To open the **Alerts \& IOCs** page, click **Detection** \> **Alerts \& IOCs**.

The page contains the **Alerts** tab and the **IOC Matches** tab:

- Use the **Alerts** tab to view the current alerts in your enterprise.

  Alerts can be generated by security infrastructure, by security personnel, or by Google Security Operations rules.

  In systems with data RBAC enabled, you can only view alerts and detections that originate from rules that are associated with your assigned scopes. For more information about data RBAC impact on detections, see [Detections](https://docs.cloud.google.com/chronicle/docs/administration/datarbac-impact#detections).
- Use the **IOC Matches** tab to view the IOCs that have been flagged as suspicious and have been seen in your enterprise.

  Google Security Operations continuously ingests data from your infrastructure and other security data sources, and automatically correlates suspicious security indicators with your security data. If a match is found (for example, a suspicious domain is seen in your enterprise), Google SecOps labels the event as an IOC and displays it on the **IOC Matches** tab. For more information, see [How Google SecOps automatically matches IOCs](https://docs.cloud.google.com/chronicle/docs/investigation/alerts-iocs#secops-matches-iocs).

  In systems with data RBAC enabled, you can only view IOC matches for assets that you have permission to access. For more information, see [Impact of data RBAC on Google SecOps features](https://docs.cloud.google.com/chronicle/docs/administration/datarbac-impact#breach_analytics_and_iocs).

  On the [**IoC matches** dashboard](https://docs.cloud.google.com/chronicle/docs/reports/dashboards-overview#ioc), you can view IOC details, such as the confidence score, severity, feed name, and category.

## Configure common view options on the Alerts \& IOCs page

This section describes the common view options that you can configure on the **Alerts** and **IOC Matches** tabs of the **Alerts \& IOCs** page.

### Specify columns to display

Use the **Column manager** to specify the columns that you want the tab to display.

### Configure date and time range

To specify the date and time range for the alerts and IOC matches that you want the **Alerts** and **IOC Matches** tabs to display, do the following:

1. Click the **Calendar** icon. The **Set Date and Time Range** dialog opens. You can specify the date and time range using the pre-set time ranges on the **Range** tab or choose a specific time of event occurrence on the **Event Time** tab.
2. To specify the date and time range using pre-set options, click the **Range** tab and select one of the following options:

   - **Today**
   - **Last Hour**
   - **Last 12 Hours**
   - **Last Day**
   - **Last Week**
   - **Last 2 Weeks**
   - **Last Month**
   - **Last 2 Months**
   - **Custom** : select the start and end date on the calendar, and then click the **Start time** and **End time** fields to select the time.
3. To specify the date and time range based on events, click the **Event Time** tab, select the date on the calendar, and then select one of the following options:

   - **Exact Time** : click the **Event Time** field and select the specific time the events occurred.
   - **+/- 1 Minute**
   - **+/- 3 Minutes**
   - **+/- 5 Minutes**
   - **+/- 10 Minutes**
   - **+/- 15 Minutes**
   - **+/- 1 Hour**
   - **+/- 2 Hours**
   - **+/- 6 Hours**
   - **+/- 12 Hours**
   - **+/- 1 Day**
   - **+/- 3 Days**
   - **+/- 1 Week**

### Sort alerts and IOC matches

You can sort the alerts and IOC matches that are displayed in ascending or descending order. Click the column headings to sort the list.

## View alerts

The **Alerts** tab displays a list of the alerts that have been detected in your enterprise within the specified date and time range. You can use this tab to view, at a glance, information about the alerts such as severity, priority, risk score, and verdict. Color-coded icons and symbols help you to quickly identify alerts that need your immediate attention.

### View additional information

To view additional information about an alert:

- Expand the alert row to view the event timestamp, type, and summary.
- Click the alert **Name** in the list to pivot to the *[Alert view](https://docs.cloud.google.com/chronicle/docs/investigation/investigate-alert)* and view additional information about the alert and its status.

### Refresh the Alerts table

Use the *refresh time* menu in the header of the **Alerts** table to select how often the **Alerts** table should be refreshed. The following options are available:

- **Refresh now**
- **No auto refresh (default)**
- **Refresh every 5 minutes**
- **Refresh every 15 minutes**
- **Refresh every hour**

### Alerts generated by composite detections

Alerts can be generated by [composite detections](https://docs.cloud.google.com/chronicle/docs/detection/composite-detections), which use composite rules that consume outputs (detections) from other rules combined with events, metrics, or entity risk signals. These rules detect complex, multistage threats that individual rules can miss.

Composite detections can help analyze events through defined rule interactions and triggers. This improves accuracy, reduces false positives, and provides a comprehensive view of security threats by correlating data from different sources and attack stages.

The **Alerts** tab displays the source of the alert in the **Inputs** column. When the alert is from composite detections, the column displays `Detection`.

To view the composite detections that triggered the alert, do one of the following on the **Alerts** tab:

- Expand the alert row and view the composite detections in the **Detections** table.
- Click the **Rule name** to open the **Detections** page.
- Click the alert **Name** to open the **Alert details** tab.

### Filter alerts

You can narrow down the list of alerts that are displayed using filters.

Perform the following steps to add filters for the list of alerts:

1. Click the **Filter** icon or **Add filter** in the upper-left corner of the tab to open the **Add filter** dialog.
2. Specify the following information:

   - **Field**: enter the object you want to filter or start typing it in the field and select it from the list.
   - **Operator** : enter **=** (Show only) or **!=** (Filter out) to indicate how the value should be treated.
   - **Value** : select the check boxes for the fields you want to match or filter out. The list that is displayed is based on the **Field** value.
3. Click **Apply** . The filter is displayed as a chip on the filter bar above the **Alerts** table. You can add multiple filters, as needed.

To clear a filter, click the **x** on the filter chip to remove it.

## View IOC matches

The **IOC Matches** tab displays the IOCs that have been detected in your network and matched against a list of known suspicious IOCs in intelligent threat feeds. You can view information about the IOCs, such as type, priority, status, categories, assets, campaigns, sources, IOC ingest time, first seen, and last seen. The color-coded icons and symbols help you to quickly identify which IOCs need your attention.

### How Google SecOps automatically matches IOCs

Google SecOps automatically correlates your ingested security data against known threat indicators from various threat intelligence feeds. When security data is ingested, it is first normalized into the Unified Data Model (UDM). The IOC matching engine continuously compares these normalized UDM events against threat indicators from all configured feeds. When a match is found, Google SecOps generates an IOC match alert. This automated matching process is particularly effective for domains and IPv4 addresses.

The following diagram illustrates the end-to-end process:

![IOC-matching process](https://docs.cloud.google.com/static/chronicle/images/investigation/ioc-matching.png)

For more information about ingesting data, see [Google SecOps data ingestion](https://docs.cloud.google.com/chronicle/docs/secops/secops-ingestion).

### IOC versions

Google SecOps retains all ingested IOC versions and uses the most
recently ingested version that is active until a given end date. If you ingest an
IOC with no end date, it remains active indefinitely. If you later ingest the
same IOC with a specific time range (start and end dates), it
overrides the indefinite version during its active period, which includes a
five-day lookback before its start date.

After this time-limited IOC expires, Google SecOps automatically reverts to using the previous IOC version if it's still active (for example, the indefinite active version).
Ingesting a time-limited IOC doesn't delete or permanently expire a previously
ingested indefinite IOC.

After the data is ingested, the UDM event data is continuously analyzed to find IOCs that match known malicious domain names, IP addresses, and file hashes (MD5, SHA-256, and SHA-1). When a match is found, the IOC is displayed on the **IOC Matches** tab.

### Threat intelligence sources

Google SecOps uses multiple sources for IOC matching:

- **Google-provided intelligence**: Google SecOps includes integrated threat intelligence from Google's Mandiant, VirusTotal, and Google Threat Intelligence. These feeds are automatically available and provide a wide range of indicators from global threat analysis. Customers with the Enterprise Plus package also gain access to more advanced feeds like Mandiant Breach Analytics.
- **Customer-provided feeds** : you can ingest your own proprietary or third-party threat intelligence feeds into Google SecOps. These feeds, such as `MISP_IOC`, are normalized and included in the same IOC matching process, enabling you to correlate your security data with indicators that are relevant to your organization.

The following threat-intelligence sources are available in Google SecOps out-of-box:

| Google SecOps Enterprise package | Google SecOps Enterprise Plus package |
|---|---|
| Enriched open-source intelligence (OSINT) | Enriched open-source intelligence (OSINT) |
|   | Mandiant Fusion |
|   | VirusTotal |

### Real-time and retroactive matching

Google SecOps performs IOC matching in two ways:

- **Real-time matching**: when new security telemetry is ingested and normalized, it is immediately checked against all available IOC feeds. Any matches trigger alerts in near real time.
- **Retroactive matching**: when new IOCs are added to any integrated threat intelligence feed (either Google-provided or customer-provided), Google SecOps automatically scans your historical data (up to your full data retention period, typically one year) for any past occurrences of these new indicators. This ensures that historical activities are analyzed for potential compromise, even if the indicator was not known at the time of ingestion.

### UDM fields used for matching

The automated IOC matching engine primarily focuses on matching against domain names and IP addresses found in UDM events. The following table details which specific UDM fields are used for automatic IOC matching based on your package:

| **Enterprise** package | **Enterprise Plus** package |
|---|---|
|   | `about.file` |
| `network.dns.answers` |   |
| `network.dns.questions` | `network.dns.questions` |
|   | `principal.administrative_domain` |
|   | `principal.asset` |
|   | `principal.ip` |
| `principal.process.file` | `principal.process.file` |
| `principal.process.parent_process.file` | `principal.process.parent_process.file` |
| `security_result.about.file` | `security_result.about.file` |
| `src.file` | `src.file` |
|   | `src.ip` |
|   | `target.asset.ip` |
|   | `target.domain.name` |
| `target.file` | `target.file` |
| `target.hostname` | `target.hostname` |
| `target.ip` | `target.ip` |
| `target.process.file` | `target.process.file` |
|   | `target.process.parent_process.file` |

Understanding which UDM fields are used helps ensure your data parsers correctly map raw log fields to the appropriate UDM fields for effective IOC matching.

If you have a Google SecOps Enterprise Plus package and the [Applied Threat Intelligence](https://docs.cloud.google.com/chronicle/docs/detection/ati-view-ioc-page) (ATI) feature is enabled, IOCs are analyzed and prioritized based on GTI Score. For more information, see [Applied Threat Intelligence priority overview](https://docs.cloud.google.com/chronicle/docs/detection/ati-prioritization) and [Applied Threat Intelligence Fusion Feed](https://docs.cloud.google.com/chronicle/docs/detection/ati-fusion-feed).

### Advanced IOC matching techniques

Beyond the automated IOC matching visible in the **IOC Matches** tab, Google SecOps offers several powerful methods for more granular or custom IOC correlation.

#### Using entity graphs and YARA-L rules

An [entity graph](https://docs.cloud.google.com/chronicle/docs/event-processing/data-enrichment#enrich-entities-merging) lets you ingest various types of contextual entities---including those representing IOCs---and join them with event data using YARA-L detection rules. This enables multi-dimensional IOC matching.

Common entity types used for IOC matching in an entity graph include: `IP_ADDRESS`, `DOMAIN_NAME`, `FILE` (for hashes), and `URL`.

An entity graph can use two contexts:

- **Google-provided context (`GLOBAL_CONTEXT`)** : Google SecOps pre-populates the entity graph with feeds like GCTI, Safe Browsing, and VirusTotal, which are labeled with `source_type = "GLOBAL_CONTEXT"`.
- **Customer-provided context (`ENTITY_CONTEXT`)** : you can ingest your own IOC feeds (for example, from Anomali, Recorded Future, STIX) or use the [Ingestion API](https://docs.cloud.google.com/chronicle/docs/reference/ingestion-api) to add custom IOCs. These are generally labeled with `source_type = "ENTITY_CONTEXT"`.

**Important consideration for Entity Graph validity** : by default, an entity graph entry is only valid for approximately +/- 5 days from its ingestion timestamp. This means that for continuous matching, context data must be re-ingested at least every five days. However, if the entity includes a `metadata.threat` field, this +/- 5-day expiration no longer applies, making it suitable for historical IOC matching.

Example YARA-L rule using `GLOBAL_CONTEXT`:

    rule google_safebrowsing_process_launch {
      meta:
        author      = "noam@"
        description = "Detects Process Launch events against Critical or High severity Google's SafeBrowsing database."

      events:
        $e.metadata.event_type = "PROCESS_LAUNCH"
        $e.target.process.file.sha256 = $hash

        $g.graph.metadata.entity_type = "FILE"
        $g.graph.entity.file.sha256 = $hash
        $g.graph.metadata.source_type = "GLOBAL_CONTEXT"
        $g.graph.metadata.threat.severity = "CRITICAL" or
        $g.graph.metadata.threat.severity = "HIGH"

      match:
        $hash over 10m

      condition:
        $e and $g
    }

For detailed examples of context-aware analytics and IOC matching using YARA-L, see [IP address matching against indicators of compromise](https://docs.cloud.google.com/chronicle/docs/yara-l/yara-l-2-0-examples#ioc-ip-matching).

#### IOC matching with data tables and YARA-L rules

You can use [data tables](https://docs.cloud.google.com/chronicle/docs/investigation/data-tables) within [YARA-L rules](https://docs.cloud.google.com/chronicle/docs/detection/yara-l-2-0-syntax) to match against lists of IOCs. Data tables replace reference lists, which are deprecated. Data tables support multiple columns and data types like string, regex, and CIDR, letting you match on multiple IOCs in a single rule.

[Column-based comparison](https://docs.cloud.google.com/chronicle/docs/investigation/data-tables#link_udm_events_to_data_tables_using_column-based_comparison) and [row-based comparison](https://docs.cloud.google.com/chronicle/docs/investigation/data-tables#link_udm_events_to_data_tables_using_row-based_comparison) are two methods for using Data Tables within YARA-L rules:

- Column-based comparison checks if a field's value exists in any row of a specific data table column using the `in` keyword. This is useful for checking against a list of values in a single column.
- Row-based comparison joins UDM event fields to data table columns using [equality or comparison operators](https://docs.cloud.google.com/chronicle/docs/investigation/data-tables#row-based). When multiple comparisons are made, all conditions must match on the same row in the data table. This process lets you do multi-column IOC matching. Rules that use row-based comparison require a [`match` section](https://docs.cloud.google.com/chronicle/docs/detection/yara-l-2-0-syntax#match_section_syntax).

**Example: YARA-L rule matching IPs from a data table column**

    rule ioc_ip4_matches {
      meta:
        description = "IOC IPv4 matching using data tables"
      events:
        $ioc.metadata.event_type = "NETWORK_CONNECTION"
        $ioc.target.ip = $dip
        // checks if the IP address is in the ip_address column of data table "string_demo_list"
        $dip in %string_demo_list.ip_address

      condition:
        $ioc
    }

For multi-dimensional matching (for example, IP address + port), you can use row-based comparison against a data table with multiple columns. The following example uses a data table called `connections_watchlist` with columns `ip` and `port`:

    rule ioc_ip4_and_port_matches {
      meta:
        description = "Matches on IP address and port using a data table"
      events:
        $ioc.metadata.event_type = "NETWORK_CONNECTION"
        $ioc.target.ip = $dip
        $ioc.target.port = $dport

        // row-based join: both ip and port must match same row in data table "connections_watchlist"
        %connections_watchlist.ip = $dip
        %connections_watchlist.port = $dport

      match:
        $dip, $dport over 5m

      condition:
        $ioc
    }

#### BigQuery for historical IOC analysis

The `datalake.ioc_matches` table in Google SecOps's data lake (BigQuery) provides a powerful way to query historical IOC match data. While the Google SecOps **IOC Matches** tab focuses on domains, you can use BigQuery to analyze IP-address matches and more.

Example SQL to query for specific IP-address IOC matches:

    -- Add your IP IOC Matches here
    DECLARE __IP_IOCS__ ARRAY <STRING>;
    SET __IP_IOCS__ = ['40.79.150.120'];
    ---
    SELECT
      MIN(DATE(TIMESTAMP_SECONDS(CAST(day_bucket_seconds AS INT64)), 'UTC')) AS first_observed,
      MAX(DATE(TIMESTAMP_SECONDS(CAST(day_bucket_seconds AS INT64)), 'UTC')) AS last_observed,
      COUNT(4) AS hits,
      ioc_value,
      feed_log_type,
      is_global,
      CONCAT(COALESCE(asset.namespace, "untagged"),":",COALESCE(asset.hostname, asset.asset_ip_address, asset.mac, "-")) AS asset
    FROM
      `datalake.ioc_matches`
    WHERE
      ioc_value IN UNNEST(__IP_IOCS__)
      AND ioc_type = "IOC_TYPE_IP"
    GROUP BY
      4,
      5,
      6,
      7

Here are the truncated results:

| Row | first_observed | last_observed | hits | ioc_value | feed_log_type | is_global | asset |   |
|---|---|---|---|---|---|---|---|---|
| 1 | 2025-02-23 | 2025-03-05 | 64 | 40.79.150.120 | CATCH_ALL | false | untagged:192.168.12.16 |   |
| 2 | 2025-02-27 | 2025-03-05 | 29 | 40.79.150.120 | CATCH_ALL | false | untagged:192.168.12.129 |   |
|   |   |   |   |   |   |   |   |   |

You can also query the `datalake.events` table for multi-dimensional IOC matching by constructing a concatenated string, for example:

    DECLARE
      __IOC_MULTIPLE_ATTRIBUTES__ ARRAY <STRING>;
    SET
      __IOC_MULTIPLE_ATTRIBUTES__ = ['1.2.3.4,80', '1.2.3.4,443'];
    SELECT
      MIN(TIMESTAMP_SECONDS(metadata.event_timestamp.seconds)) AS first_seen,
      MAX(TIMESTAMP_SECONDS(metadata.event_timestamp.seconds)) AS last_seen,
      target_ip,
      target.port
    FROM
      `datalake.events`,
      UNNEST(target.ip) target_ip
    WHERE
      DATE(hour_time_bucket) BETWEEN DATE_SUB(CURRENT_DATE, INTERVAL 60 DAY)
      AND DATE_SUB(CURRENT_DATE, INTERVAL 1 DAY)
      AND target_ip != ""
      AND target.port > 0
      AND CONCAT(target_ip,",",CAST(target.port AS STRING)) IN UNNEST(__IOC_MULTIPLE_ATTRIBUTES__)
    GROUP BY 3,4

> [!NOTE]
> **Note:** The Google SecOps Data Lake typically retains data for six months.

#### UDM Search and Search API

- **[UDM Search](https://docs.cloud.google.com/chronicle/docs/reference/rest/v1alpha/projects.locations.instances/udmSearch)** : Supports using data tables (previously called *reference lists* ) for single-dimension searches (for example, a list of hashes). However, it doesn't support complex `OR` logic across multiple distinct groups (for example, `(IP1 AND Port1) OR (IP2 AND Port2)`).
- **[Search API](https://docs.cloud.google.com/chronicle/docs/reference/search-api)**: The older Search API can be effective for IOC matching on hashes, IP addresses, and domain names, returning matching assets.

### Filter IOC matches

You can use filters to narrow down the list of IOCs that are displayed in the **IOCs** table.

Perform the following steps to add filters for the list of IOCs:

1. Click the **Filter** icon in the upper-left corner of the **IOCs** table to open the **Filters** dialog.
2. Configure the following:

   - **Logical Operator** : select **OR** to match any of the combined conditions (disjunction) or **AND** to match all of the combined conditions (conjunction).
   - **Column**: select the column to filter by.
   - **Show Only** or **Filter Out** : in the middle column, select **Show Only** or **Filter Out** to specify how the value should be treated.
   - **Value** : select the check boxes for the values to show or filter out based on the **Column** value.  
3. Click **Apply** . The filter is displayed as a chip on the filter bar above the **IOCs** table. You can add multiple filters, as needed.

To clear a filter, click the **x** on the filter chip to remove it or **Clear All**.

#### Example of filtering for critical IOCs

If you're looking for IOCs that have been identified as critically
severe, select **Severity** in the left column, **Show only** in the middle column, and **Critical** in the right column.

#### Example of filtering for Applied Threat Intelligence IOCs

If you want to view only Applied Threat Intelligence IOCs,
select **Sources** in the left column, **Show only** in the middle column, and **Mandiant** in the right column.

You can also filter IOCs using the **Filters** flyout panel on the left side of the tab. Expand the column name, find the value, and click the **More** icon to select **Show only** or **Filter out**.

### View and manage IOC-match details

To view the details about an incident, such as priority, type, source, IC-Score, and category, click the IOC to open the **IOC details** page. On this page, you can do the following:

- View event prioritization
- View associations

#### View event prioritization

Use the **Events** tab to view how the events where the IOC was seen is prioritized.

Click the event to open the **Event viewer**, which displays the priority and rationale and event details.

> [!NOTE]
> **Note:** If you are getting IOC mappings but there are no events, then there may be a mistake in the field mapping or no rules. For more information, contact Google SecOps Support.

#### View associations

Use the **Associations** tab to view associations for any actor or malware to help investigate breaches and prioritize alerts.

## SOAR alerts

For Google SecOps unified customers, SOAR alerts are shown on this page, and include a case ID. Click the case ID to open the **Cases** page. On the **Cases** page, you can get information on both the alert and its associated case and take response actions. For more information, see [Cases Overview](https://docs.cloud.google.com/chronicle/docs/soar/investigate/working-with-cases/cases-overview).

To manage alert status or close an alert, do the following:

1. Go to the **Cases** page.
2. In the **Case details** section \> alert overview, click **Go to case** to access the case.

## Limitations

Google SecOps can handle up to 10,000 IOC matches at any one time. This limit applies to all search parameters that the **Alerts \& IOCs** page exposes.

**Need more help?** [Get answers from Community members and Google SecOps professionals.](https://security.googlecloudcommunity.com/)