Investigate Pane Overview
The Investigate Pane in the SenseOn platform is the primary workspace to review, analyse, and respond to security cases. It makes investigation workflows more efficient. It gives case management tools, detailed timelines, contextual visualisations, and actionable response options, all in one place.
Key Functions of the Investigate Pane
The pane has several functional areas. These areas help you to understand threats quickly and to take effective action:
1. Case Management
Track and manage the lifecycle of each case efficiently:
-
Case Prioritisation
The platform automatically prioritises the cases with High or Critical severity, and shows them to you. This makes sure that you focus on the cases that are most urgent. -
Case Scoring
Each case has three scores. Together, they describe how the platform assessed the threat: - Severity: overall danger level of the activity (Critical, High, Medium, Low)
- Confidence: how certain the platform is that the activity is genuinely malicious (High, Medium, Low)
- Score: a composite numeric value (0–100) that combines severity and confidence. You can use it to sort and filter.
If similar activity recurs in your environment, SenseOn can adjust the score of an observation after detection. For information about how to read those adjustments, refer to Automated Triage.
- Correlation Source
Each case records the engine that correlated its observations into the case. The SenseOn engine correlates most cases. An external engine can also group the observations, for example when Microsoft puts alerts into an incident. In this condition, the case has an amber External correlation badge on its case card and in the case header. The badge tells you that a different engine, not SenseOn, decided which observations belong together. This is useful context when you assess how the case was assembled.
The Correlated by row in the detail panel of an observation shows the engine for that observation. If a case contains observations that different engines correlated, each observation row shows the engine that correlated it. Thus, you can tell external correlation and SenseOn correlation apart in one case.
- Case States
Update the status of cases when investigations progress. This helps you to track key metrics such as MTTR: Open: Default state for new cases.In Progress: Work on the case is active.In Review: Case is under peer or managerial review.Closed: The case is resolved.
To change the status of a case, use the status menu in the case header. If you select an open status (Open, In Progress or In Review) on a closed case, the case opens again. If you select Close case… from the menu, the close form opens. The case does not close immediately (refer to Closing a Case in this section).
- Outcome Categorisation
When you close a case, assign an outcome. The outcome helps with metrics, and it helps to tune the models: True positive: Malicious activity detected.Benign true positive: Potential malicious activity but no threat.False positive (incorrect alert logic): No malicious activity detected, because of incorrect alert logic.False positive (incorrect data): No malicious activity detected, because of incorrect data.Undetermined: It was not possible to find the outcome of this case.
When you close a new case, the standalone False positive outcome can no longer be selected. Select one of the two false-positive variants or Undetermined. Cases previously closed as False positive continue to show that outcome in their history.
- Closing a Case
To open the close form at the top of the case side panel, select Close case in the case header. Select an outcome. If necessary, add a closing comment. Then select Save and close.
The form keeps a draft for each case. Thus, you can change between cases and not lose what you entered. Cancel discards the draft. You can also open the same form from the Close case… option in the status menu.
-
User Assignment
You can assign cases to a specific analyst. Use assignment to share the workload across your team and to make shift handover clear. Assigned cases show in the personal queue of the assignee on the Overview. -
Investigation Notes
Add comments to record your findings, decisions, or handover context. In the Investigate module, you add comments from the case header, and the case side panel lists them. For more information, refer to The Case View Side Panel.
1a. The Case View Side Panel
When you open a case in the Investigate module, its details show in a side panel next to the knowledge graph. On the case overview, the panel has these sections, from top to bottom:
-
Case Overview
The SenseOn AI case summary and the Comment history of the case. On a closed case, this section also has a Case closed summary with the closing category and closing comment. -
Resolve investigation
A collapsible section that shows the Resolve verdict for the case. By default, it is expanded. It collapses automatically when the case closes, and it expands again if the case opens again. It is hidden for cases that have no Resolve result. -
Observations
The observations that make up the case. -
Timeline
A collapsible section that holds the case history. By default, it is collapsed. The case history contains state changes, assignments and other events from the lifecycle of the case. This section is different from the observations timeline along the bottom of the pane. -
Response Overview
The response actions of the case. It opens automatically if the current view (the case overview or a selected observation) has response actions. If there are no response actions, it stays collapsed until you toggle it for that case.
Adding and reviewing comments
A Comment control in the case header opens a comment box at the top of the side panel:
- Type your comment. To save it, select Comment. To discard the draft, select Cancel.
- After the save, the button shows Comment added. After a few seconds, the box clears and closes. If the save does not work, Comment not added. Try again. shows, and the box keeps your draft. Thus, you can try again.
- The box stays open while you move between observations, graph nodes and edges. Thus, you can continue to collect detail and not lose your draft. Each case keeps its own draft. If you change to a different case and come back, the box is as you left it. If you select the control again, the box hides but it keeps the draft.
- Saved comments show in Comment history in the Case Overview, with the newest first. Each comment is a chat-style bubble that shows the author, the comment text and the time. If someone changed the comment later, the bubble has an "edited" marker. To show a menu to edit or delete one of your own comments, hover over it or focus it.
- Closing notes show in the same Comment history. Each closing note has a case close tag. If someone closed a case with an outcome but no closing comment, Comment history prompts you to Add a closing comment.
2. Case Investigation Workflow
Investigate incidents more efficiently with built-in intelligence and structured data views:
- SenseOn AI Case Summary
Each case includes a summary that the SenseOn AI LLM generates automatically. The summary gives: - Root cause analysis
- High-level impact description
-
Key entities involved
-
Observations Timeline
A chronological, to-scale view of the observations in the case. It helps you to: - Understand the sequence of events
- Correlate related activities
- Find dwell time or spread patterns
When you hover over an observation, a tooltip shows its source and how it was correlated. Thus, if a case mixes external and SenseOn correlation, you can read that attribution directly on the timeline.
An observation can trigger a Reflex or Endpoint Protection response action. In this condition, the single timeline node of that observation also has a response status icon. The icon shows next to the crosshairs marker above the node. The action shows on the node of its own observation, not as a separate point on the timeline. To go directly to that action in the response overview, select the status icon. There, you can read its current status and any notes.
- Shareable Investigate Links
When you open an observation, the browser address bar updates to point at it. Thus, the observation that you view has its own link. The link also captures your selection in the knowledge graph. This selection is the node that you have open, and the process tree if you drilled into one. Thus, a bookmarked, reloaded or shared link opens the case again with the same observation, graph node and process tree.
When you open a different observation, the browser history gets a new entry. Thus, the back button goes back through the observations that you opened. When you select a graph node or open the process tree, the link updates in place and the browser history gets no new entry. If you leave Investigate and come back from the left-hand menu, Investigate opens where you were. It does not open at the case overview.
If the linked observation is no longer part of the case, the link opens the case overview and shows a short notice. If the link cannot match a saved graph node, the link opens with nothing selected. For example, this occurs in an older case from before graph node links.
3. Knowledge Graph
Use an interactive visual graph to explore the relationships between the entities in a case:
-
Entity Relationship Mapping
View how users, processes, endpoints, and destinations interact. -
Process Tree Integration
Drill into an observation to trace the full execution lineage of a process. -
Collaboration Tools
Add comments to specific elements in the graph to share context across your team. -
Device Details
To see the details of a device, select it in the graph. You can also open it in the devices list of a case. The details are in groups: what the device reported at the time, and its current state: - Device details at time of observation lists the values that the observations captured, such as Hostname, Device ID, IP address, Device type, User, and Location. These values are fixed. Thus, you always see the device as it was when the activity occurred. The section tells you when the observations captured the values. If more than one observation recorded the device, the section tells you how many observations captured the values. The section also tells you that the values will not change.
- Real-time Universal Sensor data lists the current state of the device, as the SenseOn Universal Sensor reports it. This includes Isolation status, Last seen, OS type, Agent version, and Segment. These values refresh while the case is open. Thus, they stay current, also when you have an observation selected. The section shows the time of the last retrieval.
- If the integration of a configured third-party EDR covers the device, a Real-time section shows for that EDR. The section has the name of the vendor, and it lists the current details from that vendor for the device.
4. Telemetry Record Analysis
Advanced users can get access to the raw telemetry for each observation:
- Inspect low-level details, such as file paths, data transfers, registry changes, command lines, or parent-child process relationships.
- Pivot into Hunt Lab for comprehensive, granular reviews of observed activity
5. MITRE ATT&CK Mapping
SenseOn maps each observation to at least one applicable MITRE ATT&CK technique:
- Understand the probable objectives and tactics of the adversary.
- Use this to correlate detections with known attack chains or threat actor behaviour.
- To open the MITRE ATT&CK technique lookup, click a technique name. The lookup shows the full technique description, sub-techniques, and known threat actor associations directly in the platform.
5a. Evidence Management
The evidence panel in a case lets you attach and track the artefacts that you collect to support your investigation:
- Upload files: attach screenshots, memory dumps, log extracts, or any other artefact that is relevant to the case
- Link observations: manually link more observations from the Experience module to a case. Do this if they are related to the case but are not automatically part of it
- Add external references: record links to external threat intelligence sources, ticket numbers, or documentation
- Evidence notes: annotate each item of evidence with context, to help teammates or for a later review
The case keeps its evidence, and each case export includes the evidence.
6. Active Response Options
Where it is supported, and if you have Active Response access, you can respond directly to threats from the Investigate Pane:
-
Isolate Device
Immediately remove a compromised device from the network. -
Kill Process
Stop malicious or suspicious processes before they can escalate. -
Delete File
Remove known malicious files from affected endpoints. -
Remote Session
For advanced users, open a remote session to: - Pull forensic artefacts (for example, file contents and hashes)
- Run custom diagnostic commands
- Apply containment rules (for example, firewall changes, or the removal of persistence mechanisms)
Best Practices
- When you close a case, always update the case state and outcome. This makes sure that threat metrics and SOC reports are accurate.
- Use the SenseOn AI to start investigations quickly.
- Use the Observations Timeline to understand the sequence of events and the progression of the kill chain. This decreases the time to resolution.
- Use the Knowledge Graph to trace process trees and lateral movement, or to find hidden entity relationships.
- Add notes or comments to give visibility across teams and to make case handover clear.