Morpheus AI

Incident Response Automation with a Human Approval Step

Incident response automation collects the evidence, proposes containment and produces the report. Morpheus starts in assist mode, and the analyst approves every state-changing action until your SOC moves the autonomy mode. Every approval is recorded with who approved it and when, in the same record that answers a NIS2, DORA or GDPR review.

24h / 72h

NIS2 early-warning and incident-notification windows your evidence has to fit

72 hours

GDPR Article 33 breach-notification window for supervisory authorities

800+

bidirectional integrations to detect, contain, and remediate across your stack

What does security incident response automation do in a SOC?

Security incident response automation runs the steps of handling a security incident: it gathers the evidence, works out what happened, proposes the response and, once approved, carries it out and records it. In Morpheus, the investigation comes before the action. Attack Path Discovery traces the incident across the tools you connect, and every finding cites the searches behind it. When Morpheus is uncertain, it defers to a human.

From First Alert to Filed Report

Detect
alerts from 800+ tools
→
Triage
verdict with evidence
→
Investigate
attack path reconstruction
→
Contain
approval-gated actions
→
Report
evidence on regulator clocks

Where is the human approval step?

It sits between the decision and the action. When Morpheus wants to run a command during an incident, what happens depends on what the command does and on your action-permission policy:

  • Read-only commands, such as searches, lookups and reputation checks, run without asking.
  • Commands that change something, such as adding a tag, blocking, quarantining or closing, stop at an approval card. The card names the command and lists its parameters. The analyst approves it or rejects it.
  • A command your policy blocks is removed from what Morpheus can choose, and does not run.

Administrators set the policy for each risk class, read and write: Blocked, Requires approval or Always allow. The organization default can be overridden per site. Rules add hard constraints in plain language, for example “Ask the analyst for approval before isolating a host.” The four autonomy modes, Deterministic, AI-Assisted, AI-Led and Autonomous, are configuration your SOC owns, with approval gates by command-risk tier.

What evidence does the approver see?

The approval card shows the exact command and parameters. Beside it, the investigation report shows what Morpheus concluded and why: each key finding cites the searches that support it, every search is listed with what it found, and a Data Caveats section names what the investigation could not see.

Every finding is graded Confirmed, Inferred or Gap. Where Morpheus looked and found nothing, it reports the gap instead of filling it. The full investigation downloads as a file for the case record.

What happens after approval?

The command runs, and a result card shows its status and what it did, with its details and evidence. Each session’s action log lists every command Morpheus ran, its integration and class, and, for each approved action, who approved it and when. The log also totals approvals and blocked attempts.

Per incident, the record holds the triage verdict and its reasoning, every query the platform ran, every action with its command-risk tier, who approved what, and the timeline from first alert to closure.

How is security incident response automation different from IT incident management?

IT incident management restores a service: a ticket, an owner, a fix and a closed ticket. Security incident response deals with an adversary: it investigates what was accessed, contains it, keeps the evidence and, in regulated sectors, reports to an authority on a fixed clock.

The tools overlap, but the record a security incident needs is the evidence and the approvals, not the ticket history.

Evidence on the Regulator’s Clock

Three frameworks, three clocks. The same automated incident run produces evidence for each.

NIS2

Article 21 asks for incident-handling measures. Article 23 sets a 24-hour early warning and a 72-hour notification. Morpheus produces evidence for both articles from the incident record itself.

DORA

Financial entities classify and report ICT incidents on fixed timelines. The Morpheus audit trail maps to DORA Articles 5, 6, and 19, so classification starts from evidence, not memory.

GDPR

Article 33 gives you 72 hours to notify a supervisory authority of a personal-data breach, and Article 34 covers affected individuals. Timeline reconstruction and scope evidence come out of the same investigation Morpheus already ran.

Related

Running incident response on a legacy SOAR today? See how teams are migrating off legacy SOAR without losing the playbooks that still earn their keep.

faqs

Frequently Asked Questions

What security and compliance teams ask about incident response automation.