Search
Ctrl+K
Usability
5
Automation
3
Security
4
Infrastructure
4
On this page
Documentation for triaging alerts, investigating incidents, collaborating with AI agents, and automating response workflows in Shuffle Security.
Shuffle Security (shuffle.security/incidents) is an incident response and alert triage workspace built to keep investigations, observables, tasks, AI agents, and automated playbooks in one place.
Instead of jumping between a separate ticketing queue, threat intelligence tabs, and your automation engine, you can review incoming alerts, inspect enriched indicators, assign tasks to teammates or AI agents, and trigger containment workflows directly from the incident view.
@AIAgent in comments, assign checklist tasks to the agent, and approve or reject high-impact containment actions with human-in-the-loop controls.NoteZero License Paywalls
Incident and case management is included in both Shuffle Cloud and self-hosted open-source instances. There are no per-seat licenses, analyst fees, or ticket caps. Standard app runs execute only when automation workflows run. Manual incident handling, triage, and queue management consume zero app runs.
Navigate to /incidents in Shuffle Security to view and manage your active queue:
Incidents progress through standardized lifecycle states as your team works them:
| Status Stage | Meaning | Typical Handling |
|---|---|---|
| New / Open | Ingested alert awaiting triage | Evaluate observables, review automated enrichment, escalate or close. |
| In Progress | Active investigation | Inspect the investigation workspace, work tasks, execute response playbooks. |
| Under Review | Containment executed | Verify remediation and complete post-incident documentation. |
| Resolved / Closed | Threat neutralized or confirmed false positive | Archive the case and tune detection rules if necessary. |
All, Open, In Progress, Under Review, Closed), severity (Critical, High, Medium, Low, Info), or search by keyword, ticket ID, and observable value.When you click on an incident from the queue, you land on the investigation workspace at /incidents/:id. This view gives you everything you need during an active investigation—whether you prefer a fast, conversational triage feed or need to inspect raw telemetry.
The workspace tabs are organized into Operational Tabs on the left for day-to-day triage, and Data Translation Tabs on the right for inspecting the underlying payload.
@AIAgent. The feed reads bottom-to-top like a standard chat window.To Do, In Progress, Done). When an incident requires multiple response steps—such as isolating a machine, resetting credentials, and notifying a user—break them down into tasks here. Assign tasks to teammates, or assign them to AI Agent to let Shuffle execute them automatically.Along the right side (or inline in Detailed view) is the incident activity timeline. Because investigations can generate a high volume of updates, you can toggle filters to focus on specific activity:
Beyond an individual incident, you can manage indicators and feeds across your entire tenant:
/incidents/observables, or configure custom regex extraction patterns./incidents/threat-feeds (including Feodo Tracker, MalwareBazaar, AlienVault IP reputation, Blocklist.de, Emerging Threats, and OpenPhish).On the right side of the incident tab bar, you can inspect how the raw alert was normalized:
AI in Shuffle Security works directly inside your incidents as an operational teammate rather than a separate chatbot. Shuffle AI agents read the incident context, analyze observables, suggest containment steps, and execute actions through your authenticated integrations.
@AIAgentChat with an agent directly inside incident comments or the Simple triage view by mentioning @AIAgent (or @agent):
Code
Editable
Response
The agent reads the incident finding, observables, tasks, threat feed matches, and comment history, then posts its findings and tool outputs directly into the timeline.
In the Tasks tab, set any task's assignee to AI Agent. The agent reads the task objective, selects the appropriate tools from your connected apps (such as querying Active Directory, pulling endpoint logs from CrowdStrike, checking an Okta user, or posting to Slack), updates the checklist steps, and marks the task Done when complete.
To prevent unintended disruption, high-impact or destructive actions (such as blocking an IP on a firewall, revoking user sessions, or isolating a host) require human approval:
WAITING state.If an agent encounters a tool failure or error, an Agent Failed — Manual Action Needed banner alerts you immediately so you can step in.
To have agents triage alerts before an analyst opens them, configure routing rules under Admin -> Preferences (or via category automations on /incidents). For example, you can automatically run an agent on incoming Critical alerts to check running processes, enrich indicators, and post an initial triage summary.
Click the Ask AI button in the top navigation bar to open the AI side drawer scoped to the active incident. Use it to generate Post-Incident Reviews (PIR), draft shift handoff summaries, or build containment commands on the fly.
Use the interactive ingestion panel above, or navigate to /incidents and use the ingestion controls in the top header bar to connect alert sources.
Every tenant has a dedicated inbound webhook to receive alerts from SIEMs, EDRs, email security gateways, and custom scripts (Splunk, Wazuh, Elastic, CrowdStrike, AWS GuardDuty):
/incidents in Shuffle Security.Code
Editable
Response
For alert sources that do not push webhooks or sit behind firewalls, connect your app credentials in the header bar or use scheduled workflows (such as Ingest Tickets). These workflows poll external APIs on a schedule and create incidents automatically. Click Sync Now in the header bar to trigger an immediate pull.
Different security tools output very different JSON structures. Shuffle is schemaless at ingest:
TLP:RED, TLP:AMBER, TLP:GREEN, TLP:CLEAR).When an alert lands in Shuffle, observables are enriched automatically so analysts have reputation context as soon as they open the incident:
On ingest (via webhook or polling workflow), Shuffle parses raw logs, email headers, and descriptions using regex and heuristic extractors (configurable at /incidents/observables) and attaches discovered indicators to the incident.
Background workflows (Enable Threat feeds and Realtime IOC extraction) pull intelligence from active feeds configured at /incidents/threat-feeds. Whenever observables are added to an incident, Shuffle checks them against these feeds in real time and tags matching indicators with reputation, confidence, and threat category metadata.
When you connect external threat intelligence apps (such as VirusTotal, Shodan, AbuseIPDB, or URLScan) and enable the Enrich automation on /incidents, Shuffle queries those services for new incidents and records the results in the incident's enrichments list:
JSON
Response
Inside the incident's Observables tab, click any indicator row to view its sighting history across other incidents or trigger an immediate lookup against your connected threat intelligence tools.
Use the interactive control above, or navigate to /incidents and click the Automation for Incidents (rocket) button in the header bar to configure automatic AI triage, enrichment, and response workflows.
Code
Editable
Response
When an incident triggers a workflow, Shuffle passes the full incident object as $incident:
$incident.title — Alert title$incident.severity — Severity level (Critical, High, Medium, Low, Info)$incident.observables — Array of extracted IOCs$incident.description — Incident description or summary$incident.id — Unique incident identifierShuffle Security checks whether your core incident response automations are active:
| Readiness Pillar | Verification Check | Target Flow / Key | Purpose & Configuration |
|---|---|---|---|
| Ingestion | Inbound webhook trigger running | Ingestion Webhook (webhook_<trigger_id>) | Pushes alerts directly into incidents via webhook. Configure at /incidents -> Webhook. |
| Enrichment | Threat feeds, IOC extraction, and enrich automation active | Enable Threat feeds, Realtime IOC extraction, threat_intel_case_management_1 | Matches extracted observables against threat intelligence feeds. Activate in /usecases. |
| Assign & Escalate | Active workflow with background processing | case_management_assign_escalate_1 | Routes new incidents to on-call analysts and handles SLA escalations. Activate in /usecases. |
| Default config | Datastore cache present | shuffle-security_ioc_types, shuffle-security_threat_feeds, security rules | Seeds default IOC types, community threat feeds, and security routing rules. Seeded via /preferences -> Incidents. |
Code
Editable
Response
Shuffle Security includes pre-built templates for common SOC workflows in /usecases:
.eml attachments, evaluate header authentication (SPF/DKIM/DMARC), check URLs, and purge malicious emails across the tenant.You can customize the terminology used across the web application to match your team's workflow:
Navigate to /preferences -> Terminology (or /admin/preferences):
| Option | Singular | Plural | Route | Description |
|---|---|---|---|---|
| Incidents (default) | Incident | Incidents | /incidents | Standard SOC incident triage and response. |
| Alerts | Alert | Alerts | /alerts | High-volume detection pipelines and triage. |
| Cases | Case | Cases | /cases | Formal investigations and digital forensics. |
| Tickets | Ticket | Tickets | /tickets | Helpdesk or IT-oriented workflows. |
| Jobs | Job | Jobs | /jobs | Operations and scheduled tasks. |
Changing terminology updates navigation menus, page titles, and UI labels across the application. From /admin/preferences, you can also configure SLA response/resolution targets, custom lifecycle statuses and severities, task statuses, and incident routing rules.
Under the hood, all incidents, alerts, and cases are stored directly in Shuffle's Datastore under the shuffle-security_incidents category formatted according to the OCSF 2005 (Incident Finding) specification.
Inspect and query raw incident records directly:
/admin/datastore?category=shuffle-security_incidents in Shuffle Security. If local datastore exists, it loads locally; otherwise, it automatically redirects to Shuffle Core.https://shuffler.io/admin?tab=datastore&category=shuffle-security_incidents or /admin?tab=datastore&category=shuffle-security_incidents on self-hosted instances).shuffle-security_incidents.To prevent analysts from accidentally deleting active investigations or destroying audit history, /incidents does not expose a hard-delete button in the main operational views (normal triage marks cases as Resolved or False Positive).
If a test webhook or noisy rule ingested bogus records that need to be permanently purged, an admin (isAdmin) can delete them from the Datastore:
/admin/datastore?category=shuffle-security_incidents.incident_2026_0942).When a detection workflow, ingestion webhook, or custom script writes an incident to shuffle-security_incidents, it stores an OCSF 2005 JSON payload:
| Field | Type | Description | Sample Value |
|---|---|---|---|
class_uid | Integer | OCSF Class Identifier | 2005 (Incident Finding) |
category_uid | Integer | OCSF Category Identifier | 2 (Findings) |
activity_id | Integer | Action Identifier | 1 (Create) |
severity_id | Integer | Severity Scale (1 to 5) | 4 (High) |
finding_info | Object | Finding Title, Description, and Timestamps | {"title": "Phishing detection with credential harvester URL"} |
observables | Array | Indicators (IP, hash, process, domain, user) | [{"name": "process.name", "value": "mimikatz.exe"}] |
Python
Editable
Response
Because incidents live in the native datastore:
Every key in shuffle-security_incidents is stored with an immutable revision history. Whenever an analyst edits a case in the UI, an AI Agent enriches observables, an ingestion webhook posts updates, or a workflow runs self.set_cache(...), Shuffle creates a new revision instead of overwriting the previous record destructively.
revision_id, Unix timestamp (edited / created), actor provenance (user_id or workflow_id / execution_id), and field diffs.API Call
Response
No response received.
Python
Editable
Response
GET /api/v1/incidentsAPI Call
Response
No response received.
API Call
Response
No response received.
API Call
Response
No response received.
API Call
Response
No response received.
Python
Editable
Response
For more details on backend API endpoints and datastore caching rules, see the API documentation.