# Agentic AI vs SOAR Playbooks: When a Playbook Is Enough

A SOAR playbook runs steps and branches a person wrote in advance; an agent chooses its next step. Worked through CVE-2026-0322, whose Palo Alto advisory lists 20 fixed PAN-OS builds, four of five steps stay fixed playbook logic. The fifth, turning advisory prose into a lookup table, suits an agent when the vendor ships no structured data.

## What a playbook fixes in advance

Palo Alto's [Cortex XSOAR playbook documentation](https://xsoar.pan.dev/docs/playbooks/playbooks-overview) says playbooks let you "structure and automate security responses that were previously handled manually". Its conditional tasks "are used as decision trees": were indicators found, if yes enrich them, if not conclude the incident is not malicious. Google's [Security Operations playbook overview](https://cloud.google.com/chronicle/docs/soar/respond/working-with-playbooks/whats-on-the-playbooks-screen) describes a trigger, actions "such as enriching data, notifying users, or isolating a compromised host", and a flow that decides, "typically using `if-then-else` conditions". In both products every branch was drawn by a person before the alert arrived.

Anthropic's [Building effective agents](https://www.anthropic.com/engineering/building-effective-agents) draws the line: workflows are systems where "LLMs and tools are orchestrated through predefined code paths"; in agents, LLMs "dynamically direct their own processes and tool usage". A playbook with a language-model step inside it, such as summarizing an alert, stays a workflow. OpenAI's [guide](https://cdn.openai.com/business-guides-and-resources/a-practical-guide-to-building-agents.pdf) gives three signs that fixed logic has run out: decisions needing "nuanced judgment, exceptions, or context-sensitive" calls, rule sets that have become "unwieldy due to extensive and intricate" rules, and heavy reliance on unstructured data.

## A real advisory, counted

Palo Alto published the advisory for CVE-2026-0322, a PAN-OS management interface code-execution flaw (CVSS 4.0 score 8.6), on 14 Oct 2026. CISA added it to its KEV catalog the same day with a due date of 17 Oct 2026. The advisory shows exploit maturity as attacked and says "very limited exploitation has been observed". It lists fixed builds for each sub-train: 1 for PAN-OS 12.2, 3 for 12.1, 5 for 11.2, 6 for 11.1 and 5 for 10.2. That is 20 builds to compare against, and a device on 11.2.7-h12 must reach 11.2.7-h21 or 11.2.16 or later, not merely 11.2.7-h13.

Written as playbook conditions, that is 20 branches, each a comparison on one field. Nothing in them needs judgment; they need a table. What a person or agent must supply is the table itself, once, from an advisory that arrives as prose and a web table. The branch count belongs to this advisory; the next one lists a different number, and a playbook cannot be redrawn each time on the day an exploited flaw is published.

## Five steps, split between playbook and agent

Step split is this site's reading of the Cortex XSOAR, Google SecOps, Anthropic and OpenAI pages above, applied to this site's CVE-2026-0322 record built from the Palo Alto advisory, read 19 Nov 2026.

| Step | Done by | Owner of the record | Record left | How it usually fails |
|---|---|---|---|---|
| 1. Trigger on the KEV entry or vendor feed | Playbook (a trigger, not a decision) | Detection engineer | Alert with CVE ID and feed timestamp | The KEV feed and the vendor feed each open a case for the same CVE, because the case is not keyed on the CVE ID |
| 2. Turn the advisory into a table of train, sub-train and first fixed build | Agent: unstructured data and a layout that changes | Vulnerability engineer reviews and signs the table | Proposed table, source URL, reviewer, diff against the advisory | The agent applies one sub-train's fixed build to the whole train, or drops a row (19 instead of 20). The reviewer signs after reading the table instead of diffing it against the advisory |
| 3. Match inventory against the table | Playbook: 20 comparisons on the sw-version field | Platform owner of the playbook | Matched devices with version and fixed build | Hotfix numbers compared as text, so h3 sorts above h21; or the sub-train is ignored, so 11.2.9 looks fixed by 11.2.7-h21 when it needs 11.2.10-h15 or 11.2.16 |
| 4. Check exposure: is the management interface reachable from untrusted networks | Playbook, reading permitted IP addresses and interface profiles | Network owner | Per-device exposure result | The permitted-address list is read from an old configuration export, so a device shows as restricted after the list changed |
| 5. Ticket, change window and approval | Playbook; an agent may draft the change note | Change approver, a named person | Approval, time, and the read-back of the version after the change | The approver signs the drafted note without opening the signed table, or the version is never read back after the change |

Steps 3 and 4 follow the first row of the decision table below: a branch that is a condition on a field belongs in a playbook, where it is cheap, repeatable and reviewed once. Step 2 is the open-ended one, and it can be undone, since a person signs the table before step 3 uses it. That is why the agent sits inside the playbook: the playbook owns the trigger, the ticket and the approval, and the agent's [run log](/guides/agent-run-logs-what-to-keep/) attaches to one step instead of the whole case. Keep the agent's tools to reading the advisory and writing a draft, as in the [guardrails guide](/guides/ai-agent-guardrails/).

## The same run, timed

Dates are from CISA's KEV catalog (added 14 Oct 2026, due date 17 Oct 2026) and Palo Alto's advisory, which lists the same 20 builds throughout. The clock times, the four firewalls and the review durations are constructed. Of the four, fw-a runs 11.2.7-h12 and needs 11.2.7-h21 or 11.2.16 or later; fw-b runs 10.2.13-h30, above its train's 10.2.13-h26; fw-c runs 12.1.7-h8, which is the fixed build; fw-d runs 11.1.6-h20 and needs 11.1.6-h39 or 11.1.16-h3 or later. Two of four are affected.

Times, devices and durations are constructed; the dates and the 20-build advisory are as read on 19 Nov 2026.

| Time | Event | Done by | Record |
|---|---|---|---|
| 14 Oct 2026, 09:00 | CISA adds CVE-2026-0322 to KEV; Palo Alto's initial publication is dated the same day | CISA, Palo Alto | KEV entry, due date 17 Oct 2026 |
| 09:02 | Playbook polls the feed and opens one case keyed on the CVE ID | Playbook | Case with CVE ID and feed timestamp |
| 09:03 to 09:08 | Agent reads the advisory and drafts the table: 5 trains, 20 rows | Agent | Draft table, source URL |
| 09:08 to 09:30 | Reviewer checks row counts per train (1, 3, 5, 6, 5) and compares every build string with the advisory, then signs | Vulnerability engineer | Signed table, diff, reviewer, 22 minutes |
| 09:31 | Playbook matches the four devices: fw-a and fw-d affected, fw-b and fw-c not | Playbook | Matched list with version and fixed build |
| 09:35 | Playbook reads the management interface settings for fw-a and fw-d | Playbook | Exposure result per device |
| 09:40 to 09:50 | Playbook opens the change ticket; the agent drafts the change note | Playbook, agent | Ticket and draft note |
| 09:50 to 10:05 | The approver compares the note with the signed table and approves | Change approver | Approval at 10:05, 65 minutes after the KEV entry |
| Change window, then next morning | Upgrade runs; playbook reads the version back from each device | Platform owner | Read-back: fw-a on 11.2.7-h21 or later, fw-d on 11.1.6-h39 or later |
| 15 Oct 2026 | The advisory's Updated field reads 15 Oct 2026. Whenever that field changes, the playbook re-runs step 2 and the reviewer signs the diff against the signed table; an empty diff is recorded too | Playbook, agent, vulnerability engineer | Second signed table or a signed empty diff |

The agent's part is 15 of the 65 minutes: 5 drafting the table and 10 drafting the change note. People spend 37 (22 reviewing the table, 15 approving) and the playbook 13. The longest step is the person's review of the table; skip the diff and the minutes saved buy an unchecked table.

## When the table-building step is not an agent step either

- The vendor ships the data in a structured form. Palo Alto's advisory page offers CVE JSON and CSAF downloads next to the table, and Cisco's offers CSAF. Where a file lists the fixed build for each sub-train, a playbook task parses it with no model. The agent step is for vendors whose structured file lacks that detail, or who publish none.
- The advisory arrives rarely. Checking 20 rows against the advisory is the same work as typing them, so for a vendor that publishes a few advisories a year a person builds the table and the playbook consumes it.
- Nobody can review the output before it takes effect. A table that feeds step 3 unsigned turns a draft into an unreviewed branch; keep the step a fixed, signed one.

## The decision table

Decision rules are this site's reading of the OpenAI, Anthropic, Cortex XSOAR and Google SecOps pages cited above, read 19 Nov 2026.

| Question about the job | If yes | If no |
|---|---|---|
| Can every branch be written as a condition on a field (severity, asset tag, build number)? | Playbook | Ask the next question |
| Does the next step depend on reading free text, code or an advisory whose layout varies? | Candidate for an agent step | Playbook |
| Is the rule set so large that analysts avoid editing it? | Candidate for an agent step (OpenAI's second sign) | Playbook |
| Can the step be undone and approved by a person before it takes effect? | An agent step is acceptable with that approval | Keep it a fixed, reviewed playbook step |

Anthropic adds the cost side: agents bring "higher costs, and the potential for compounding errors", and its advice is to find "the simplest solution possible". The checklist's [need-an-agent-at-all question](/evaluation-checklist/need-an-agent-at-all/) turns that into a written justification. LangChain lists "complex workflows that combine deterministic and agentic steps" among uses for its runtime, which is the shape above ([source](https://docs.langchain.com/oss/python/concepts/products)). For a job whose branches are known, such as phishing triage with indicator enrichment, a playbook is enough and the agent adds cost without reducing work.

## Sources

- [Palo Alto, Cortex XSOAR, Playbooks overview](https://xsoar.pan.dev/docs/playbooks/playbooks-overview), read 19 Nov 2026
- [Google Cloud, Security Operations, Playbook overview](https://cloud.google.com/chronicle/docs/soar/respond/working-with-playbooks/whats-on-the-playbooks-screen), read 19 Nov 2026
- [Anthropic, Building effective agents](https://www.anthropic.com/engineering/building-effective-agents), read 19 Nov 2026
- [OpenAI, A practical guide to building agents, When should you build an agent](https://cdn.openai.com/business-guides-and-resources/a-practical-guide-to-building-agents.pdf), read 19 Nov 2026
- [LangChain docs, Runtimes, frameworks, and harnesses](https://docs.langchain.com/oss/python/concepts/products), read 19 Nov 2026
- [Palo Alto Networks security advisory for CVE-2026-0322](https://security.paloaltonetworks.com/CVE-2026-0322), read 19 Nov 2026
- [CISA KEV catalog entry for CVE-2026-0322](https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-0322), read 19 Nov 2026
- [Cisco advisory cisco-sa-ISE-ABP-VNSW7Tn5 (CSAF download offered)](https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-ISE-ABP-VNSW7Tn5), read 19 Nov 2026

Last reviewed 19 Nov 2026

Canonical: https://agenticaiincybersecurity.com/guides/agentic-ai-vs-soar-playbooks/
