# Review alerts

Supported in: This guide shows how to investigate an alert and its associated entities using Google Security Operations.

<br />

### What is an alert?

An [alert](https://docs.cloud.google.com/chronicle/docs/investigation/alerts-iocs.md.txt) is an Indicator of
Compromise (IOC) or rule detection flagged by
[Google SecOps](https://docs.cloud.google.com/chronicle/docs/overview.md.txt), indicating an anomaly
in the normal workflow of traffic within your enterprise. You should
investigate alerts as a possible breach of security.

### How do alerts get to Google SecOps?

Google SecOps taps into various external sources within the
security community using industry-wide databases updated continuously.
Google SecOps also has a feature-rich programming language,
YARA-L, so you can craft your own custom rules.

For more information about YARA-L, see
[Overview of the YARA-L 2.0 language](https://docs.cloud.google.com/chronicle/docs/detection/yara-l-2-0-syntax).
For more information about rules, see
[View and manage rules](https://docs.cloud.google.com/chronicle/docs/detection/manage-all-rules.md.txt).

## Before you begin

You can perform these steps from your company's Google SecOps
instance or from the Google SecOps demo environment.

Google Security Operations supports the Google Chrome and Mozilla Firefox browsers. Upgrade your browser to the most current version for optimal performance and security. The latest Chrome version is available for download at <https://www.google.com/chrome/>. Mobile operating systems (iOS/Android) and mobile browsers are not supported.

> [!NOTE]
> **Note:** You can access multiple Google SecOps instances within the same browser profile as long as you log in using the same user identity (the same Cloud Identity account or the same workforce identity pool). However, your active session is invalidated if you switch user accounts or access an instance configured with different workforce pool or different Google Cloud organization. To maintain concurrent sessions across different identities or authentication setups, use a separate browser profile or an incognito/private window for each session.

## Authentication and access

Google SecOps integrates with SSO solutions. Access to the Google SecOps platform requires valid enterprise credentials.

1. Launch Chrome or Firefox.

2. Verify you have active access to the corporate account.

3. Go to the following URL and replace <var translate="no">customer_subdomain</var> with the customer-specific identifier to access the Google SecOps application:

   `https://customer_subdomain.backstory.chronicle.security`

## View alerts and IOC matches

In the navigation bar, select **Detection** \> **Alerts \& IOCs**.

The page displays the **Alerts** and **IOC Matches** tabs. You can adjust the
time range using the time range selector so that matches and alerts appear.

## Investigate an asset using SIEM Search

Next, drill down to a particular domain and asset that might have been
compromised:

1. From the **IOC Matches** tab, click a domain in the **IOC** column to open
   the **Entity context** panel, or click an asset in the **Assets** column to
   open **SIEM Search** directly for that asset.

2. If you opened the **Entity context** panel for a domain, review the domain
   details and click **Run new search** to open **SIEM Search** with a UDM
   search query for that domain.

3. On the **Overview** tab in **SIEM Search** , review the **Entity summary** ,
   **Prevalence of Assets** , **Resolved IPs** , **Sub-domains and sibling
   domains** , and **Associated Entities** panels to identify assets in your
   enterprise that interacted with the domain.

4. Click an asset in the **Associated Entities** panel to open its **Entity
   context** panel, and then click **Run new search** to pivot to a UDM search
   for that asset around the timeline of the activity.

5. Click the **Results** tab to view the **Activity Over Time** chart, the
   **Prevalence** tab, and the **Events** table for the asset:

   - Click the **Prevalence** tab to view the prevalence of domains associated with your search results, including the **Low prevalence
     domains** and **Prevalence ≤ 10** columns. Low-prevalence domains are less common in your environment and can warrant closer investigation.
   - Use the **Aggregations** panel or click **Add filter** to narrow the search results by UDM fields such as `metadata.event_type` or `metadata.log_type`. Hold the pointer over a field value and select **Show only** or **Filter out**.

## Investigate what triggered the alert

You can gain more insight into the triggering event and related alerts in
several ways:

- On the **Overview** tab, the **Entity summary** panel displays a chart of
  alerts over time and lists the rules with the highest alert counts for the
  entity. Click **View in Alerts Tab** to switch to the **Alerts \&
  Detections** tab in **SIEM Search** , or click **Open Alerts \& IOCs** to view
  all alerts generated during the search time range.

- On the **Alerts \& Detections** tab, click an alert in the table to open the
  **Alert Viewer** and inspect the alert summary, or click **View details** to
  open the **Alert** view. For more information, see
  [Investigate an alert](https://docs.cloud.google.com/chronicle/docs/investigation/investigate-alert.md.txt).

- On the **Results** tab, click an event in the **Events** table to open the
  **Event Viewer** panel. The **Event Viewer** displays detailed information
  about the event across the **Event Fields** , **Raw Log** , **Alerts** ,
  **Entities** , and **Tags** tabs.

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