This document explains how to investigate case-related entities and alerts
using the Explore page in Google Security Operations. The Explore page
provides a visual representation of entity relationships and alert activity,
helping you understand the context, sequence, and impact of suspicious events.
This document also explains how to interpret entity types, explore correlations,
and perform follow-up actions based on the visual analysis.
You can explore the entities and alerts associated with a case using the Explore
page. In the center of the page, a visual representation—called a visual
family—displays how alerts and entities relate to one another.
This view helps you:
Understand the cause-and-effect relationships between entities and alerts
See the chronological order of events
Identify connections between suspicious activities
events
Identify visual family elements
The visual family includes two types of nodes:
Entities: Displayed as hexagons
Artifacts: Displayed as circles
Color is used to convey meaning:
Blue hexagons: Internal entities
Green circles: Internal artifacts
Red: Indicates suspicious items
Identify internal and external entities
Entities can appear in two styles:
Color-filled shapes represent internal entities
Outlined-only shapes represent external entities
For example, an IP address that belongs to a known internal network would
appear as a color-filled hexagon, signaling it's internal. Conversely, an IP
from outside the network appears as an outlined hexagon, indicating it's external.
Understand entity relationships in the visual family
The Explore page shows how entities and artifacts relate to each other
using visual cues and connections. To identify different types of entities and
artifacts, click helpHelp.
This opens the Entity Legend, which defines each shape and color used in
the visual.
Relationship types
Entities and artifacts may be linked by lines that represent their relationships.
There are two types of relationships:
Actions: Displayed as arrows; indicate a direct action (for example,
sending an email)
Connections: Displayed as dotted lines; show general associations
(for example, a user tied to a machine hostname)
For example:
An arrow may connect two user entities if one sends an email to the other.
A dotted line might connect a user entity with a host entity they've accessed
Visual families and mapping rules
Entities and artifacts are derived from mapping rules, and their relationships (connected by lines) are defined by visual families.
If visual families aren't configured, entities and artifacts still appear in the center workspace. However, no connecting lines are displayed between them.
Configure mapping and visual families
To configure mapping rules or assign visual families on the Event Configuration page, click settings Settings in one of the following places in the Google SecOps platform:
To analyze entities and alerts visually, open a case and on the Cases page, click Explore. The Explore page contains the following workspace elements:
Left pane: displays the alerts associated with the selected case and their corresponding timestamps.
Middle pane: displays a graph of interconnected entities, a graphical alert timeline, and playback controls.
Side drawer: shows details of the selected alerts or
entities, including raw enrichment data (if available). When you select an alert or
an event, the side drawer displays the relevant information.
If you're a Google SecOps user, you'll see an Explore
button at the bottom of this drawer. Click it to continue investigating the alert
on a dedicated page. For more information,
see Investigation views.
Bottom of page: displays video control buttons to play the
events, together with a visual time range (which can be manipulated further
using
add
Add and
remove
Remove). Click
play_arrow
Play Event to go through the events in chronological
order on the graph.
Click an alert in the left pane to highlight the related entities highlighted in the
middle pane. The node indicating this alert appears bigger than the other nodes
(alerts) on the graph. Hold the pointer over the nodes to see their
respective alert names. Entities not involved in the selected alert appear dimmed (unavailable).
The following options are available on the Explore page:
Options
Descriptions
Fit to Screen: autofits
the graph to fit the entire visible area.
Circular layout: default graph layout. Click Change Graph Layout for other options.
Play Event: plays all alerts of the case in sequence.
Highlights associated entities for each step. The graph displays the alert flow, highlighting each played alert with a larger node.
Next Event: plays the next alert in order. Starts from the top of the list.
Previous Event: steps back to the previous alert. Disabled until the first alert is played.
Fast Forward and Fast Backward: plays alerts at 3× speed, in chronological (ascending) or reverse chronological (descending) order, respectively.
Time Range Slider: expands or narrows the visible time range on the X-axis.
This opens an entity legend.
Take manual action after investigation
After reviewing the visual timeline, you can take further manual actions for
further investigation. For example, you can scan IP addresses to check for
known threats or investigate downstream effects like data exfiltration.
Common follow-up actions include:
Quarantine computers
Check and scan infected systems
Investigate suspicious emails
Identify missing or exfiltrated data.
Supported entity types in Google SecOps
This section provides a list of the supported entity types that can be utilized within the Google Security Operations platform for security investigation, analysis, and enrichment.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-29 UTC."],[[["\u003cp\u003eThe Explore page in Google SecOps visually displays alerts and entities of a case, illustrating cause-and-effect relationships and the sequence of events.\u003c/p\u003e\n"],["\u003cp\u003eEntities (hexagons) and artifacts (circles) are shown in the middle pane, with color-coding to distinguish internal (filled) vs.external (outlined) and suspicious (red) items.\u003c/p\u003e\n"],["\u003cp\u003eRelationships between entities and artifacts are depicted by lines, with arrows indicating actions and dotted lines signifying connections.\u003c/p\u003e\n"],["\u003cp\u003eThe left pane lists alerts and their timestamps, the middle pane shows the interconnected entities with playback controls, and the side drawer provides detailed information on selected alerts or entities, including an option to explore further.\u003c/p\u003e\n"],["\u003cp\u003eThe Explore page offers various tools like Fit to Screen, Change Graph Layout, and Play/Next/Previous Event buttons, along with a Time Range Slider, to navigate and analyze the events and their relationships effectively.\u003c/p\u003e\n"]]],[],null,["# Investigate entities and alerts\n===============================\n\nSupported in: \nGoogle secops [SOAR](/chronicle/docs/secops/google-secops-soar-toc) \nThis document explains how to investigate case-related entities and alerts\nusing the **Explore** page in Google Security Operations. The **Explore** page\nprovides a visual representation of entity relationships and alert activity,\nhelping you understand the context, sequence, and impact of suspicious events.\nThis document also explains how to interpret entity types, explore correlations,\nand perform follow-up actions based on the visual analysis.\n\n\nYou can explore the entities and alerts associated with a case using the **Explore**\npage. In the center of the page, a visual representation---called a visual\nfamily---displays how alerts and entities relate to one another.\n\nThis view helps you:\n\n- Understand the cause-and-effect relationships between entities and alerts\n- See the chronological order of events\n- Identify connections between suspicious activities events\n\nIdentify visual family elements\n-------------------------------\n\n\nThe visual family includes two types of nodes:\n\n- **Entities**: Displayed as hexagons\n- **Artifacts**: Displayed as circles\n\nColor is used to convey meaning:\n\n- **Blue hexagons**: Internal entities\n- **Green circles**: Internal artifacts\n- **Red**: Indicates suspicious items\n\nIdentify internal and external entities\n---------------------------------------\n\nEntities can appear in two styles:\n\n- Color-filled shapes represent internal entities\n- Outlined-only shapes represent external entities\n\nFor example, an IP address that belongs to a known internal network would\nappear as a color-filled hexagon, signaling it's internal. Conversely, an IP\nfrom outside the network appears as an outlined hexagon, indicating it's external.\n| **Note:** Artifacts are always internal and are always displayed as a color-filled circle.\n\nUnderstand entity relationships in the visual family\n----------------------------------------------------\n\nThe **Explore** page shows how entities and artifacts relate to each other\nusing visual cues and connections. To identify different types of entities and\nartifacts, click help **Help** .\nThis opens the **Entity Legend**, which defines each shape and color used in\nthe visual.\n\n### Relationship types\n\n\nEntities and artifacts may be linked by lines that represent their relationships.\nThere are two types of relationships:\n\n- **Actions**: Displayed as arrows; indicate a direct action (for example, sending an email)\n- **Connections**: Displayed as dotted lines; show general associations (for example, a user tied to a machine hostname)\n\nFor example:\n\n- An arrow may connect two user entities if one sends an email to the other.\n- A dotted line might connect a user entity with a host entity they've accessed\n\n### Visual families and mapping rules\n\n\nEntities and artifacts are derived from mapping rules, and their relationships (connected by lines) are defined by visual families.\n\nIf visual families aren't configured, entities and artifacts still appear in the center workspace. However, no connecting lines are displayed between them.\n\n### Configure mapping and visual families\n\nTo configure mapping rules or assign visual families on the **Event Configuration** page, click settings **Settings** in one of the following places in the Google SecOps platform:\n\n- [Alerts Events tab](/chronicle/docs/soar/admin-tasks/ontology/deciding-what-events-to-configure)\n- [Ontology Status page](/chronicle/docs/soar/admin-tasks/ontology/viewing-model-family-and-field-mapping)\n\n\nFor more details about how to configure mapping and assign visual families,\nsee [Configure mapping and assign visual families](/chronicle/docs/soar/admin-tasks/ontology/configure-mapping-and-assign-visual-families).\n\nUse the Explore page\n--------------------\n\n\nTo analyze entities and alerts visually, open a case and on the **Cases** page, click **Explore** . The **Explore** page contains the following workspace elements:\n\n- **Left pane**: displays the alerts associated with the selected case and their corresponding timestamps.\n- **Middle pane**: displays a graph of interconnected entities, a graphical alert timeline, and playback controls.\n- **Side drawer** : shows details of the selected alerts or entities, including raw enrichment data (if available). When you select an alert or an event, the side drawer displays the relevant information. \n If you're a Google SecOps user, you'll see an **Explore** button at the bottom of this drawer. Click it to continue investigating the alert on a dedicated page. For more information, see [Investigation views](/chronicle/docs/investigation/investigation-views).\n- **Bottom of page** : displays video control buttons to play the events, together with a visual time range (which can be manipulated further using add **Add** and remove **Remove** ). Click play_arrow **Play Event** to go through the events in chronological order on the graph.\n\n\nClick an alert in the left pane to highlight the related entities highlighted in the\nmiddle pane. The node indicating this alert appears bigger than the other nodes\n(alerts) on the graph. Hold the pointer over the nodes to see their\nrespective alert names. Entities not involved in the selected alert appear dimmed (unavailable).\n\n\nThe following options are available on the **Explore** page:\n\nTake manual action after investigation\n--------------------------------------\n\n\nAfter reviewing the visual timeline, you can take further manual actions for\nfurther investigation. For example, you can scan IP addresses to check for\nknown threats or investigate downstream effects like data exfiltration.\n\n\nCommon follow-up actions include:\n\n- Quarantine computers\n- Check and scan infected systems\n- Investigate suspicious emails\n- Identify missing or exfiltrated data.\n\n| **Note:** For more information on how mapping rules and visual families are configured, see [Ontology overview](/chronicle/docs/soar/admin-tasks/ontology/ontology-overview).\n\nSupported entity types in Google SecOps\n---------------------------------------\n\nThis section provides a list of the supported entity types that can be utilized within the Google Security Operations platform for security investigation, analysis, and enrichment.\n\n\n0: \"SourceHostName\" \n1: \"SourceAddress\" \n2: \"SourceUserName\" \n3: \"SourceProcessName\" \n4: \"SourceMacAddress\" \n5: \"DestinationHostName\" \n6: \"DestinationAddress\" \n7: \"DestinationUserName\" \n8: \"DestinationProcessName\" \n9: \"DestinationMacAddress\" \n10: \"DestinationURL\" \n11: \"Process\" \n12: \"FileName\" \n13: \"FileHash\" \n14: \"EmailSubject\" \n15: \"ThreatSignature\" \n16: \"USB\" \n17: \"Deployment\" \n18: \"CreditCard\" \n19: \"PhoneNumber\" \n20: \"CVE\" \n21: \"ThreatActor\" \n22: \"ThreatCampaign\" \n23: \"GenericEntity\" \n24: \"ParentProcess\" \n25: \"ParentHash\" \n26: \"ChildProcess\" \n27: \"ChildHash\" \n28: \"SourceDomain\" \n29: \"DestinationDomain\" \n30: \"IPSET\" \n31: \"Cluster\" \n32: \"Application\" \n33: \"Database\" \n34: \"Pod\" \n35: \"Container\" \n36: \"Service\"\n\n**Need more help?** [Get answers from Community members and Google SecOps professionals.](https://security.googlecloudcommunity.com/google-security-operations-2)"]]