SOCPilots
Entity relationships / synthetic illustration

One workspace. The whole investigation.

SOCPilots Platform

From alert
to understanding.

Alerts, entities, cases and response. Bring the investigation together without leaving your existing SIEM behind.

Built around your SIEMWazuhElasticSplunkQRadarCapabilities vary

The console

Real application views with synthetic demonstration data. No customer alerts, cases or accounts.

The SOCPilots case grid: identifier, severity, name, source, type, phase, status, verdict, incident lead, creation time, acknowledgement and response SLA, and tenant.
A case holds the alerts, the evidence, the timeline and the verdict in one record. Closing one requires a disposition and a closure note.

Open the full-resolution image to read the detail — 5400 × 1708 pixels.

The SOCPilots alert queue with a detail pane showing the selected alert's agent, ATT&CK technique, source address, rule level and log source, alongside actions to create a case or suppress.
Triage from one queue. The detail pane carries the agent, technique, source and rule level, and the actions that open a case or suppress the alert.

Open the full-resolution image to read the detail — 4200 × 5528 pixels.

Automation run history. Two runs are marked PAUSED with the reason shown: an approval is required before the containment step runs.
Response runs are recorded with their outcome. A paused run is held awaiting a human approver — containment has not been carried out.

Open the full-resolution image to read the detail — 4200 × 1928 pixels.

An ATT&CK matrix of fourteen tactic columns, with techniques shaded by how much alert activity was observed against each in the selected timeframe.
ATT&CK coverage: a heatmap of techniques observed in the selected timeframe. Observed activity is not validated detection coverage, and the percentage is of the application’s own technique list.

Open the full-resolution image to read the detail — 4000 × 2488 pixels.

SOCPilots is a desktop console. These are wide screenshots: on a narrow screen open the full-resolution image to read them.

From signal to judgement

From incoming signal to a recorded outcome, with evidence and review along the way.

01Ingest

Connect your SIEM and normalize incoming alerts while retaining their source context.

Result: searchable, comparable events.

02Correlate

Identify repeated and related signals using configured grouping rules. Correlation links evidence; it is not the same as creating or closing a case.

Result: related alerts grouped for investigation.

03Investigate

Bring available asset context, threat intelligence and entity relationships into the investigation.

Result: evidence an analyst can inspect.

04Decide

Review evidence and risk, record a verdict, and route actions through configured policy and approval requirements.

Result: a documented decision.

05Respond

Run supported connector actions and review execution results. Availability depends on the connected environment.

Result: recorded action outcomes.

SOCPilots in action

Watch an investigation
take shape.

From a suspicious alert to reputation checks, account context and an evidence-backed finding for your team.

Simulated example with synthetic data. No live systems are accessed and no response is executed.

Cases that hold the whole story

Investigation is a record, not a chat log. Everything that happened to a case stays attached to it.

Case management, ownership, evidence and service levels

Cases

cases

Alerts, evidence, tasks and a timeline in one record. Closure requires a disposition and a closure note.

verdict picklistclosure noteaudit trail

Tasks and ownership

tasks

Assign and track case work. With workforce management enabled, route new cases by shift and available capacity.

shift awarecapacity limitsassignment log

Evidence

evidence

Keep documents, exports and screenshots with the investigation. Extract and index text for later searches.

OCR extractionsemantic searchper-case scope

Collaboration

comments

Notify colleagues with account-linked mentions in cases, tasks and war rooms.

@mentionswar roomsnotifications

Service levels

sla

Track response and resolution against your policy, including configured business hours and breach warnings.

business hoursbreach predictionper-tenant policy

Entity intelligence

A relationship changes
the investigation.

Follow the identity, host, process and destination behind an alert. Inspect the connections before drawing a conclusion.

Entity relationships / synthetic illustration
Identity

svc_backup

A service account links the activity across hosts. An unusual relationship is evidence to investigate, not a verdict.

Illustration, not live telemetry

The rest of the console

Coverage, intelligence, assets, vulnerabilities and reporting
coverage

ATT&CK coverage

Explore techniques observed in alerts and their associated rules, agents and activity. Export to MITRE Navigator to support detection planning. Observed activity is not validated detection coverage.

intelligence

Threat intelligence

Indicators are enriched against reputation and pulse feeds, cached so the same address is not looked up forty times an hour, and cross-referenced against a stored indicator feed that raises the score on anything already known bad.

assets

Assets and exposure

Discover what is on the network, track criticality and ownership, and find the hosts your SIEM has no agent on — the blind spots that make coverage numbers look better than they are.

vulnerabilities

Vulnerabilities

Exposure per asset, tied back to the same inventory the cases use, so a vulnerability on a tier-0 host reads differently from the same vulnerability on a lab machine.

reporting

Reporting

Operational reporting for the people running the shift, and executive reporting for the people funding it. Volumes, response times, coverage, and what changed since last month.

risk

Digital risk

Monitoring beyond the perimeter — credential leaks, brand abuse and dark-web mentions — brought into the same case system as everything else.

One console, five points of view

Role decides what a person sees and what they are allowed to do. It is a permission model, not five different products.

Roles and responsibilities

Analyst

l1 · l2

Works the queue: triage, enrich, document, respond. Sees their own tenant and their own assignments first.

queuecases

Senior analyst

l3

Owns escalations, approves containment requested by others, and authors detection content.

approvalsrules

SOC manager

reporting

Watches queue health, response times, shift coverage and service levels, and reassigns work when a queue tips over.

SLAshifts

Administrator

admin

Configures connections, users, policies, automation and workspaces, with administrative changes recorded in the audit trail.

settingsaudit

Executive and client

read only

Posture, risk and outcomes without the operational detail — and, for a managed customer, a view shaped by the role-based permissions you grant them.

scopedreports

See it against your own backend

A demo on your SIEM tells you more than a demo on ours.