When to bring a partner in: a decision matrix for Cortex XSIAM work.

Most XSIAM work splits cleanly into three buckets: do it yourself with the runbook, workshop with a partner and run it yourself, or pay a partner for full delivery. Here is the decision matrix.

6 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

→Mode 1 (DIY): documented runbook work. Broker VM, tenant config, marketplace integrations, OOTB rule enablement, OOTB playbook adoption.
→Mode 2 (workshop): pattern-plus-judgment work. Rule tuning, playbook customization, dashboard design, correlation rule type decisions.
→Mode 3 (full delivery): real engineering. Custom parsers, multi-source correlation, custom playbooks, custom AI agents, compliance content.
→A good partner welcomes Mode 1 and 2 conversations; a bad partner pushes everything to Mode 3.
→Look for Cortex-specific references, published methodology, and willingness to scope down.
→Day-to-day operations after rollout is Mode 1 (your team) unless you are explicitly buying an MSSP service, which is a different conversation.

Source: Cortex XSIAM product page (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 →

Or go deeper on Services scoping

5 min read

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

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