Writing incident response SOPs that analysts and AI agents can both follow

Reviewed by ContraForce

Security Delivery · Best practice · Intermediate · 5 min read

A structure for incident response SOPs that analysts and AI agents can follow the same way: decisions as explicit conditions, per-customer exceptions, versioning and a suspicious sign-in example.

It's 02:10, and a sign-in alert fires for a finance user at one of your customers. The sign-in came from a country that user has never signed in from. Your night analyst opens the SOP, which says: investigate, and escalate if suspicious.

What counts as suspicious? Escalate to whom? A senior analyst fills those gaps from experience. A new analyst guesses, and an AI agent reading the same document can't stop to ask.

An SOP that both can follow names the evidence to collect, states each decision as a condition and marks where a human signs off.

Why should analysts and agents share one SOP?

If agents and analysts follow different documents, the customer gets two standards depending on who picked up the incident. Write one procedure, precise enough that a new analyst and an agent reach the same classification from the same evidence.

What sections does every incident response SOP need?

How do you turn a judgement call into an explicit condition?

Swap adjectives for tests. "If the sign-in is suspicious" becomes "If the sign-in country isn't in the user's sign-in history for the previous 30 days, and the customer's travel register has no entry for it." Anyone can check that against the evidence.

Give every condition an else branch, and a branch for missing evidence. Number the steps and use clear headings: ContraForce's SOP guidance notes that structured headings and step-by-step procedures help an agent find the relevant section.

How should an SOP handle classification?

Keep status and classification apart: status is where the work is, and classification is what you found. Map your SOP's outcomes exactly to the values your platform records.

Microsoft Sentinel requires a classification when you close an incident. The options are True Positive (suspicious activity), Benign Positive (suspicious but expected), False Positive (incorrect alert logic), False Positive (incorrect data) and Undetermined. The legacy incident experience in the Microsoft Defender portal uses a different set: True positive; Informational, expected activity; and False positive, with Not set as the default.

For each incident type, say what each value means in practice. Make Undetermined a deliberate outcome, with a comment listing the missing evidence. ContraForce's classification guide warns that overusing Undetermined makes your classification data less useful.

Worked example: a suspicious sign-in SOP excerpt

SOP-ID-004, Suspicious sign-in. Version 2.3. Owner: SOC lead. Last reviewed 2026-11-01.

Where do per-customer exceptions belong?

Don't fork the SOP for every customer. Keep the procedure general and point it at a customer profile: travel register, egress IPs, VIP list, approvers, contacts and any actions the customer has ruled out. The SOP above never names a customer: steps that depend on one read from E3 or the profile.

Write exceptions as conditions too, and check them before the general rule: "For this customer, don't isolate plant-floor devices without a phone call to the plant manager." Where a platform can enforce an exception, enforce it there as well, because a sentence in a document depends on the reader following it.

How should you version and review SOPs?

An agent reads the version it has

When an approver changes, update the customer profile and every SOP that names them. An agent works from the text it's given.

How does ContraForce use SOPs?

In ContraForce, you upload SOPs as Markdown or plain-text files, typed as Classification or Response, and link them to Security Delivery Agents. An agent can have several Classification SOPs, but only one is activated per investigation. To change an SOP you upload a new version: agent links are kept, and the version field records the change. SOPs are scoped to a workspace, so a customer-specific procedure lives in that customer's workspace.

Approval points don't have to rely on the text. Response actions run as Gamebooks, and Workspace Policies are ordered allow, block or ask-an-approver rules per workspace: checked top to bottom, the first match decides, and anything unmatched is allowed. A policy can apply only to Security Delivery Agents and match on the action, its target, the people or devices involved, severity or source. Agent Gamebooks also wait for approval while the workspace's Allow service providers to run gamebooks setting is off, which is the default.

Approval enforced, not just described

R2 says Reset MFA and password resets need approval. A Workspace Policy that sends those actions to an approver for Security Delivery Agents enforces that at run time, whatever the agent concluded from the text.

Uploading and linking SOPs is covered in SOPs for Security Delivery Agents.

Building and ordering run policies is covered in Workspace Policies for Gamebooks and Agents.

Keep learning

All of ContraU

Sources

  1. Microsoft Learn, Basic incident tasks for Microsoft Sentinel incidents (Close an incident), verified 2026-11-20
  2. Microsoft Learn, Manage incidents in the Microsoft Defender portal, verified 2026-11-20
  3. ContraForce Docs, How to Classify Incidents, verified 2026-11-20
  4. ContraForce Docs, SOPs for Security Delivery Agents, verified 2026-11-20
  5. ContraForce Docs, What Are Gamebooks?, verified 2026-11-20
  6. ContraForce Docs, Workspace Policies for Gamebooks and Agents, verified 2026-11-20