Reading an XSIAM services SOW: what's runbook, what's engineering, what's Premium Success.

A typical XSIAM deployment SOW combines documented runbook work, real engineering, and Palo Alto Networks Premium Success services. Knowing which is which lets you negotiate each line on its own merits.

5 min read·Cortex XSIAM

Cortex XSIAM ships hundreds of detection rules already mapped to MITRE ATT&CK and tuned by Palo Alto Networks against telemetry from across their customer base. The work in week one is enabling the right ones, not authoring from scratch.

When a deployment SOW prices six weeks of rule tuning, half of that scope is reading the OOTB ruleset, deciding which to enable, and toggling them on. That work is genuinely valuable, but it is hours, not weeks. The other half, customizing rules to your environment specific noise, is real engineering and worth your partner full rate.

The trap is letting both halves get billed at the same engineering rate. Your team sees a six-week scope, assumes it is all custom work, and pays accordingly.

Read the full lesson with Pro.

The takeaways below are public so you know what is in the lesson. The full body, the negotiation script, and every other lesson unlock with Pro. Free 30 days, no card.

Start free 30-day trial →Sign in

Takeaways

→XSIAM services have three distinct buckets: documented runbook, real engineering, and Palo Alto Premium Success. Negotiate each separately.
→Quote pattern that inflates the line: bundling all three into a single 'Deployment Services' line at engineering rates.
→Confirm with Palo Alto Networks what your Premium Success covers; do not pay your reseller for what Palo Alto is already delivering.
→Resource Units (RUs) need an indicative spend plan to prevent them from becoming a partner slush fund.
→Bring a partner in for custom parsers, multi-source correlation, internal-system integration, or compliance-driven content engineering.

Source: Cortex XSIAM Premium Success service description (Palo Alto Networks)Last verified Apr 26, 2026

Copy-ready script

Pro

“Can you split the rule scope into two phases? Phase one is enablement of the OOTB ruleset against my environment, ideally on a flat-rate or fixed-fee basis. Phase two is authoring custom rules where the OOTB set has gaps, billed hourly.”

Unlock with Pro →

See it in your own quote.

Paste a Palo Alto Networks quote. The engine will tell you, line by line, where the pattern in this lesson actually shows up.

Have Clarify read your SOW