Learn
What you're actually paying for, in plain English.
Short explainers for Cortex XSIAM, written from your side of the table and grounded in the current Palo Alto Networks public docs and the Cortex marketplace. The vocabulary your partner assumes you know, the patterns the engine flags, and the negotiation language that fits each one. Each lesson cites its source and is dated.
What you can learn about
Every line of your Cortex XSIAM quote, in plain English.
Detection content
3 lessonsOut-of-the-box rules, correlation logic, and what's a deploy versus a project.
Data sources
3 lessonsMarketplace integrations, broker VM, parsers, and which work counts as engineering.
Playbooks
2 lessonsXSOAR templates, automation work, and where bespoke authoring is real value.
Platform configuration
1 lessonTenant setup, RBAC, alert routing. The day-one work that has docs and a checklist.
Analytics versus rules
1 lessonWhy correlation rules and ML analytics are different products, and how reps blur them.
Dashboards and widgets
1 lessonSearches, widgets, and dashboards. Almost always DIY-with-patience.
Services scoping
2 lessonsHow to read a deployment SOW: what's bundled, what's DIY, and what's worth full rate.
Licensing and SKUs
2 lessonsTier mapping, credit-based ingestion, retention, and the math behind the line items.
Playbooks. XSOAR templates, automation work, and where bespoke authoring is real value.
View all topics →Cortex AgentiX ships 1,300+ playbooks. You're paying to author the gaps, not the catalog.
Cortex AgentiX (the next generation of XSOAR, embedded in XSIAM) ships more than 1,300 playbooks and 1,000+ integrations. Most incident response workflows already have a working template. The work is tailoring the gaps, not authoring from scratch.
How AgentiX playbooks are actually triggered: automation rules, jobs, and the WHEN/IF/THEN model.
In Cortex XSIAM, a playbook does not run by itself. Three things trigger it: automation rules (issue-driven), jobs (time or feed-driven), or a manual run. Understanding the trigger layer is the difference between automation that ships and automation that sits in a folder.
See it in your own quote.
Run a check and the engine will cite the lessons relevant to every line it flags. The pattern, the dollar consequence, and the script.
Have Clarify read your SOW