Use case · Agentic SOC

A SOC that reasons.

Not a wall of dashboards waiting for a human to read them. You ask the Familiar, and three Watcher orders work the queue end to end, bringing a seal to your team only when the call is genuinely contested.

soc / live
handled autonomously0
escalated to a human16%
queue clear3 Watchers working2 awaiting a seal

Illustrative split, not a customer metric.

Why dashboards failed

Visibility was never the bottleneck. Action was.

A decade of tools gave the SOC more screens, more alerts, and more dashboards. None of them did the work. The analyst is still the engine, and the engine is overloaded.

Too much to watch

More telemetry than any team can read. Coverage on paper, blind spots in practice.

Humans as glue

People pivot between consoles to assemble context by hand, one alert at a time.

Automation that breaks

The playbooks meant to help crack on every tool change, so trust in automation erodes.

The shift

Watchers work the queue. Humans hold the seals.

In an agentic SOC, the default worker is a Watcher and the human is the supervisor. The orders detect, respond, and record within the bounds you set, surfacing the contested calls and high-blast-radius casts for a person to seal. Your team moves from doing every investigation to governing all of them.

  • Watchers run inquiries in parallel, around the clock.
  • Humans own the autonomy dial and the seals.
  • Every action attributable, to a Watcher or a person, on one Scroll.
Attack orderDETECT

Investigate and triage

Read the omens, correlate, score the spread, auto-close the clean.

Defend orderRESPOND

Contain and remediate

Cast reversible Spells within your thresholds, log everything.

Human + ScholarSEAL

Seal and govern

Decide the contested calls and high-blast-radius casts; the Scholar records it.

The three orders

Who does what on the floor.

Detect
Attack Watchers

Read the omens, correlate the signals, and name what is happening. They open and build the inquiry.

Owns
Omens
MITRE
ATT&CK
Respond
Defend Watchers

Cast response spells to contain, evict, and restore, under gated authority. Destructive casts pause at a seal.

Owns
Spells
MITRE
D3FEND
Record
Scholar Watchers

Document the inquiry, collect the seals, and keep your ticketing in sync: Jira, ServiceNow, Resilient.

Owns
Scrolls
Record
& sync
Attack detects Defend responds Scholar records every step
app.soarcery.ai
The Soarcery analyst console: a natural-language prompt with suggested investigations and recent conversations

Actual product. Demo data.

In the product

The Familiar: the console you ask

This is the working surface of the agentic SOC: ask the Familiar in plain English, pick up a suggested inquiry, or review what the Watchers already ran. Every thread above is an inquiry an order carried, with the evidence attached.

Build your agentic SOC

Start with one order. Grow the autonomy.

See the Watchers work your real queue in a 30-minute walkthrough.