Skip to main content

Alerts Management

The Alerts page is the primary workspace for security analysts, providing real-time visibility into all security events detected by AuroraSOC's multi-source ingestion pipeline.

Alert Lifecycle

Status Definitions

StatusDescriptionWho Sets It
NEWJust ingested, not yet triagedSystem (Rust normalizer)
TRIAGEDAI agent has assessed severity and categorySecurity Analyst agent
INVESTIGATINGHuman or AI actively investigatingAnalyst / Orchestrator
ESCALATEDRequires senior analyst or incident responseAnalyst / Threshold rule
RESOLVEDRoot cause identified, remediated or false positiveAnalyst / Playbook

Alert Table

The main alert table displays:

ColumnDescription
SeverityColor-coded badge (Critical/High/Medium/Low)
TitleDescriptive alert title
SourceOrigin system (Suricata, Wazuh, Velociraptor, etc.)
MITRE ATT&CKMapped technique ID(s)
StatusCurrent lifecycle state
CreatedTimestamp of first detection
ActionsView, Investigate, Dismiss

Use the filter bar to narrow alerts:

  • Severity filter — Click severity badges to toggle
  • Status filter — Show only specific states
  • Date range — Custom time window
  • Search — Free-text search across title and description

Bulk Operations

Select multiple alerts using checkboxes for bulk actions:

  • Bulk Resolve — Mark selected as resolved
  • Bulk Escalate — Escalate selected to incident response
  • Create Case — Group related alerts into a single case

Alert Detail View

Clicking an alert opens its detail pane:

Overview Tab

  • Full alert description with raw event data
  • Extracted IOCs (IP addresses, domains, hashes, emails)
  • MITRE ATT&CK technique mapping with kill chain phases

Investigation Tab

When an AI investigation has been run:

  • Agent Reasoning — Step-by-step AI analysis
  • Correlated Events — Related alerts found by correlation
  • Recommended Actions — AI-suggested response steps

Timeline Tab

Chronological history of all actions taken:

  • Alert created
  • Agent triage performed
  • Status changes
  • Analyst comments
  • Playbook executions

Deduplication

AuroraSOC automatically deduplicates alerts using SHA-256 hashes:

dedup_hash = SHA256(source + title + mitre_techniques)

When a duplicate arrives within the dedup window (configurable, default 15 minutes), the existing alert's count increments rather than creating a new entry. This is why you may see a Count column showing values greater than 1.

Investigation Workflow

The fastest workflow: Filter by Critical + NEW → Review top alerts → Click Investigate to trigger AI agent analysis → Review agent findings → Resolve or Create Case.

Triggering AI Investigation

From any alert, click the Investigate button to:

  1. Alert is sent to the Orchestrator agent
  2. Orchestrator dispatches to Security Analyst for initial assessment
  3. If IOCs found → Threat Intel agent enriches them
  4. If network indicators → Network Security agent analyzes flows
  5. If endpoint indicators → EDR / Endpoint Security agent scans
  6. Results compiled into structured investigation report
  7. Alert status updated to INVESTIGATING

The investigation runs asynchronously—you'll see real-time progress via the WebSocket agent-thoughts stream.