Compete — Agentic Enterprise Operations
Cortex Console
Compete Playbook
Console competes in two places at once — against AI service management challengers coming for ServiceNow, and against agentic SOC platforms adding response execution. Know which fight you are in before you open your mouth.
New to portfolio · acquisition announced Sep 1, 2026
Read this before you compete on Console. There is no announced Cortex SKU, packaging, or GA date, and Palo Alto Networks has not explained how Console relates to Cortex AgentiX. A competitor will use both facts against you. The defensible position is that Cortex already ships agentic execution today in AgentiX, and Console deepens it into enterprise and IT operations. If the customer needs a committed capability this quarter, sell AgentiX and position Console as direction.
Seller brief
TL;DR
Console competes in two places at once — against AI service management challengers coming for ServiceNow, and against agentic SOC platforms adding response execution. Know which fight you are in before you open your mouth.
- Where we win and where they're strong
- Who to target: not a separate section on this page
- Discovery questions: not a separate section on this page
- Landmines and traps: not a separate section on this page
- Objection handling
- Proof points: not a separate section on this page
- Technical differentiators
- Details
Where we win and where they're strong
By Competitor
Competitor Deep Dives
ServiceNow (Now Assist, plus Moveworks)
Where Console Wins
- Do not fight for the system of record. The winning play is to sit beside it. Console can run as the execution layer over an existing ITSM platform, which lets the customer keep their ServiceNow investment and their multi-year contract intact.
- Security-originated work. ServiceNow SecOps is a separate product line with separate licensing and a separate implementation. Console’s security playbooks — JIT privileged access, access reviews, DLP and insider-risk triage with HR context — arrive as part of the same platform.
- Native OCSF audit output. Console’s activity lands in a SIEM without custom parsing. That is a direct XSIAM synergy ServiceNow has no equivalent for.
- Time to value. The most common complaint about ServiceNow is not capability, it is the length and cost of implementation. Console’s pitch is a Slack front door working in weeks, not a platform program.
- No platform toll. For an organization not already committed to ServiceNow, entry requires the platform itself. Console does not carry that precondition.
Watch For
- The Moveworks answer. ServiceNow spent $2.85B to own exactly this conversation, and it closed in December 2025. They will say the employee-facing agent is already bought and paid for.
- CMDB and asset gravity. If the customer’s configuration and asset records live in ServiceNow, that is genuine gravity. Concede it and position Console as execution, not as a records replacement.
- “You are a security company.” This is their strongest line and it is fair. Do not answer it by claiming ITSM credibility. Answer it by narrowing to the security-to-IT handoff, where you are the credible party.
- Enterprise agreement leverage. ServiceNow will discount aggressively to protect the platform. Compete on the seam, not on price.
Serval
Where Console Wins
- Security is a product line, not a use case. Serval is an IT automation company. Console arrives with a published security playbook library and, behind it, XSIAM, XDR, Xpanse, Cortex Cloud, and Unit 42. A CISO-led evaluation is not a fair fight for Serval.
- Detection plus execution in one vendor. Serval can execute an approved action but has no detection platform to originate it. Cortex supplies the signal, the case, and the decision.
- Enterprise assurance. Under 30 employees at the time of the Series B, scaling to a target of 100-plus. For a regulated buyer asking about support, roadmap durability, and vendor risk, Palo Alto Networks is the safer signature.
- OCSF and SIEM alignment. Auditable agent activity flowing natively into the security data platform is a story Serval does not have.
Watch For
- They ship today and you do not. Serval has a product, pricing, and references now. Console-in-Cortex has no announced GA. In an IT-led evaluation on a near-term timeline, Serval is likely to win, and pretending otherwise costs you credibility.
- The “AI layer” motion is well built. Serval deliberately accommodates customers locked into multi-year incumbent contracts — the same objection you would use against ServiceNow, they have already answered.
- Sequoia framing. A Sequoia partner publicly compared the customer feedback to ServiceNow’s own early days. Expect that quote in a competitive deck.
- Momentum narrative. Valuation from $232M to $1B in three months is a compelling story to an IT buyer who wants to back the winner. Counter with platform consolidation, not with momentum.
CrowdStrike — Charlotte AI and Agentic SOAR
Where Cortex Wins
- Execution beyond the security stack. Charlotte is excellent at investigating and responding within Falcon’s orbit. Console’s thesis is the work that happens after the security decision, in IT, HR, finance, and legal systems. Ask where Charlotte’s response ends and a ServiceNow ticket begins.
- The employee-facing surface. CrowdStrike has no service desk. The request that starts with an employee in Slack — “I need this access,” “I think this email is phishing” — has no Falcon equivalent.
- HR context in triage. Enriching an insider-risk or DLP alert with employment status, role, and recent manager change is not something an endpoint-rooted platform has.
- AgentiX is shipping. Do not let Console’s uncertainty obscure this. AgentiX has been GA-track since October 2025 with 1,100-plus integrations and native MCP support. Compete with AgentiX, and let Console extend the vision.
Watch For
- They announced the day after you did. The September 2, 2026 agentic SOC announcement will be positioned as shipping capability against your unshipped acquisition. Expect a side-by-side.
- “Seventh acquisition of 2026.” CrowdStrike will frame Palo Alto Networks as buying a story rather than building one. The counter is integration track record, not volume of deals.
- Shared context layer. Charlotte’s persistent cross-agent memory is a genuinely strong architectural claim. Do not dismiss it — differentiate on where the agents are allowed to act.
- Falcon Complete bundling. Expect agentic capability folded into managed service pricing so it appears to cost nothing.
Microsoft — Security Copilot and M365 Copilot
Where Console Wins
- Execution depth collapses outside Microsoft. Writing back to non-Microsoft systems needs Copilot Studio customization plus Power Automate flows. Okta, Jamf, GitHub, Salesforce, AWS, and CDW are all first-class in Console.
- Not purpose-built for IT execution. Copilot is a knowledge-worker assistant. Access provisioning, ticket resolution, and asset management require significant configuration before it behaves like a dedicated IT agent.
- Assistance versus completion. Copilot accelerates human work. Console’s design goal is to finish the request without a human in the loop where policy allows it.
- Heterogeneous identity reality. Most enterprises run Okta or Google alongside Entra. Console treats that as normal; Microsoft treats it as an edge case.
Watch For
- “It is in E5.” The perennial objection. Counter by asking which specific IT actions Copilot completes today without Power Automate work, and who is building and maintaining those flows.
- Genuine Entra strength. For an all-Microsoft shop, Security Copilot plus Entra is a real answer to identity remediation. Pick your accounts.
- Conflation of assistants and agents. Microsoft will present Copilot as equivalent. Hold the distinction between answering and doing.
Atlassian — Jira Service Management with Rovo
Where Console Wins
- Knowledge-grounded answers versus system actions. Rovo’s strength is resolving requests from documentation. Console’s is changing state in identity providers, MDM, and SaaS applications.
- Identity lifecycle. Onboarding across Okta, Google Workspace, and M365, time-bound access with automatic revocation, and FileVault or BitLocker recovery are not JSM territory.
- Security playbooks. JSM has no security operations story. Every Console security playbook is net-new capability in a JSM account.
- Licensing preconditions. Rovo agents in the JSM help center require AI and Rovo enabled, a Standard, Premium, or Enterprise plan, and a Service Collection subscription. Worth surfacing when a customer says they already have it.
Watch For
- Cost and incumbency. JSM is materially cheaper and already deployed. For routine ticket deflection alone, it is often good enough — so do not compete on deflection.
- Engineering affinity. In developer-led organizations the Atlassian estate has strong internal advocates. Route the conversation through security and compliance requirements instead.
Aisera, Glean, Leena AI, Salesforce Agentforce
Where Console Wins
- Aisera: breadth across departments is the strength, but it leans toward orchestration and deflection rather than deep autonomous end-to-end execution, and how much it resolves versus routes depends heavily on integration and tuning. Ask for measured resolution rates per request type.
- Glean: retrieval-first. Deep IT execution — provisioning, ticket resolution, workflow completion — is not its core. It remains a knowledge platform, and it is the wrong category for the execution problem.
- Leena AI: genuinely good at HR and IT self-service and policy answers, with IT request automation that varies by integration. No security operations story at all.
- Agentforce: excellent inside Salesforce and struggles outside it. Not built for employee help desks, infrastructure, or access provisioning.
- Common thread: all four answer and route well. None of them connect a security detection to an authorized change in an identity system with approvals, step-up MFA, and an OCSF audit trail.
Watch For
- Deflection metrics sound like resolution metrics. A high deflection rate can mean questions were answered, not that work was completed. Insist on the distinction in any bake-off scorecard.
- Glean’s knowledge-graph story is compelling to executives. Do not argue against it — it is a different job. Position Console downstream of the answer.
- Multi-department breadth resonates with HR and finance sponsors. If the sponsor is not security or IT, you are in the wrong lane for this account.
Torq and Tines
Where Cortex Wins
- No detection platform of their own. Both depend on someone else’s signal. Cortex owns detection, correlation, case management, and now execution in one place, which removes an integration seam and a vendor.
- Employee-facing intake. Neither has a service desk surface. Requests that originate with an employee rather than an alert are outside their model.
- Identity and IT lifecycle depth. They automate against IT systems through integrations; Console was built as an IT service platform first, including the asset, device, and entitlement records.
Watch For
- Vendor-neutrality as a selling point. Both position as the automation layer across a heterogeneous stack. A customer running CrowdStrike plus Splunk plus Okta hears that as freedom, not as a gap.
- Sunk automation content. A customer with hundreds of built workflows is not going to rebuild them. Position Cortex execution where their workflows stop, not as a replacement.
- Aggressive Tier-1 automation claims. Torq markets a very high share of Tier-1 handled autonomously. Ask how it is measured and over which ticket types.
The Question You Will Get Internally
The Internal Question — Console vs AgentiX
Cortex AgentiX was unveiled in October 2025 as the next generation of XSOAR. It ships with prebuilt agents that reason, plan, and execute, more than 1,300 automation playbooks, more than 1,100 prebuilt integrations, and native Model Context Protocol support. Console arrives with its own agent runtime, its own natural-language playbook model, and its own integration library of 600-plus connectors. Palo Alto Networks has not published how these differ, how they combine, or which Console capabilities integrate first.
The defensible way to talk about it, until there is official guidance:
- AgentiX is the security operations agent platform, and it is shipping. If the customer has a requirement this quarter, this is the answer. Nothing about the Console acquisition changes an AgentiX or XSOAR position.
- Console’s heritage is enterprise and IT operations — the systems outside the SOC where remediation actually has to land, plus the employee-facing intake surface that no security platform has.
- The strategic gap being closed is the handoff. Security understands the threat; IT holds the authority to change the affected system. Separate tools, separate queues, hours or days added to every response.
- Say “not yet announced” when that is the truth. It is a stronger position than a guess a customer later discovers was wrong, and this audience remembers.
Do not create an internal bake-off. If an account is mid-deployment on AgentiX, raising Console without official packaging guidance stalls the project and gives the competitor an opening. Clarify the overlap with the product team before you put Console on a slide in that account.
Objection handling
In The Room
Objection Handling
“When can I actually buy this, and what does it cost?”
The honest answer, and the only safe one: packaging, pricing, and GA have not been announced. What is available today is Cortex AgentiX, which ships agentic execution with 1,100-plus integrations and native MCP support. If the customer has a near-term requirement, scope it on AgentiX and treat Console as the direction of travel. Offer to bring the product team in rather than guessing.
“You are a security company. Why would I buy IT service management from you?”
Do not claim ITSM credibility you have not earned. Reframe: you are not selling them a help desk. You are selling the ability to finish security work in the systems where it has to land. Ask what happens after their SOC decides an entitlement must change — who makes the change, in which queue, and how long it takes. That gap is a security problem that happens to live in IT.
“We just signed a multi-year ServiceNow agreement.”
Good — do not touch it. Console can run as an execution and orchestration layer over an existing system of record, syncing and handing off work rather than replacing the platform. The customer keeps the records, the reporting, and the contract. Note that Serval sells the same accommodation, so the differentiator is the security half, not the layering.
“How is this different from Cortex AgentiX? Did you just buy a competitor to yourself?”
Acknowledge the overlap directly; evading it costs you the room. AgentiX is the security operations agent platform and it is shipping. Console’s heritage is enterprise and IT operations, plus an employee-facing intake surface AgentiX does not have. How they converge has not been published, and saying so is more credible than improvising.
“I am not letting an AI agent write to my identity provider.”
Agree with them. Console’s published default is no write access at all until an administrator explicitly configures an action, with deterministic approvals, least-privilege scoping, step-up MFA on high-risk actions, and full OCSF audit logs. Start read-only: alert triage, context enrichment, access review findings. Let them widen the boundary once they trust the audit trail.
“Serval is further along and we can deploy it next month.”
In an IT-led evaluation on a 30-day timeline, that may be true, and arguing it damages you. Change the question instead: ask whether the evaluation includes security-originated work — JIT privileged access, access review evidence, insider-risk triage with HR context, offboarding across non-SSO applications. If it does, the evaluation needs a security sponsor, and that is a different competitive field.
“We already have Copilot in E5.”
Ask for specifics: which IT actions does Copilot complete today without Copilot Studio customization and Power Automate flows, who built those flows, and who maintains them? Then ask about the non-Microsoft half of their estate — Okta, Jamf, GitHub, Salesforce, AWS. Copilot is a strong assistant; it is not purpose-built for IT execution outside Microsoft.
“Our automation platform already handles this.”
Probably part of it. Ask three questions: does it have its own detection signal, or does it depend on yours? Can an employee start a request in it? Does it hold the asset, device, and entitlement records, or does it call out to whoever does? Position Cortex execution where their workflows stop — nobody rebuilds hundreds of working automations.
“Did Palo Alto Networks really pay $500 million for a two-year-old company?”
The figure is press reporting, not disclosure. TechCrunch reported $500M in cash and stock citing two people familiar with the deal; Palo Alto Networks declined to comment and has not disclosed terms. Cite it as reporting or not at all. If pressed on the multiple, the strategic answer is that the acquisition buys an execution layer the platform did not have, not revenue.
Technical differentiators
Why Console Wins
Key Differentiators
Execution, not deflection
Most AI service tools classify, answer, and route. Console was designed to complete the work in the real system. In any bake-off, insist the scorecard separates questions answered from work completed — that single distinction is where most competitors lose.
The security-to-IT seam
No pure ITSM vendor owns detection and no pure SOC vendor owns the IT systems where remediation lands. Cortex plus Console is the only combination positioned on both sides of that handoff. This is the whole pitch — lead with it.
Governance built for write access
No write access by default, admin-configured actions only, deterministic approval routing, step-up MFA before high-risk actions, least-privilege scoping, and full audit logs. This is what makes an agent with identity-provider permissions survivable in a security review.
Native OCSF into the SIEM
Every agent and human action is logged in OCSF and ingests into a SIEM without custom parsing. No ITSM competitor offers this, and it turns agent activity into auditable security evidence rather than a blind spot.
HR context in security triage
Enriching DLP, CASB, and insider-risk alerts with employment status, role, and recent manager changes turns low-signal noise into a decision. A SIEM does not have this data. It is a narrow but genuinely defensible advantage.
Time-bound access that expires itself
JIT privileged access with approval flows, automatic expiry, and a compliance artifact on every grant. It attacks standing privilege, which is both an audit finding and a breach path — so it can be funded from GRC budget, not just the SOC.
The employee front door
A single intake point in Slack and Teams means requests arrive where people already are instead of in a portal nobody visits. No SOC-native competitor has this surface, and it is how security policy reaches employees without friction.
Both halves of agentic AI
Cortex AES (Koi) governs AI agents that arrive uninvited on the endpoint. Console is the agent you deliberately grant authority to. Very few vendors can hold both sides of that conversation, and together they make the AI story coherent.
Details
Orientation
Two Different Fights
The same product shows up in two competitive conversations with completely different buyers, budgets, and incumbents. Mixing them is the fastest way to lose both.
Lane 1
AI Service Management
The buyer is IT or IT Operations. The budget is the ITSM line item. The incumbent is a platform of record, and the challengers are well-funded AI-first startups. This is where Console’s own heritage sits — and where Palo Alto Networks has the least brand permission.
ServiceNow · Serval · Atlassian JSM · Aisera · Moveworks (ServiceNow) · Glean · Leena AI · Microsoft Copilot · Salesforce Agentforce
Lane 2
Agentic SOC Execution
The buyer is the CISO or SecOps leader. The budget is security operations. The competitors are all adding agents that investigate and respond. This is where Palo Alto Networks already competes and wins, and where Console strengthens an existing story rather than starting a new one.
CrowdStrike Charlotte Agentic SOAR · Microsoft Security Copilot · Torq · Tines · SentinelOne Purple AI · Google SecOps
Which lane should you pick? Default to Lane 2. Palo Alto Networks does not win a head-to-head ITSM platform evaluation against ServiceNow on ITSM terms, and it does not need to. The winning frame is the gap between the two lanes: security decides, IT executes, and nobody owns the handoff. That is a seam neither a pure ITSM vendor nor a pure SOC vendor is positioned to close.
Lane 1 · At a glance
AI Service Management
Console’s claim in this lane is execution depth rather than deflection. Its weakness is that it is a two-year-old product now owned by a security company.
| Dimension | Console (now Cortex) | ServiceNow + Now Assist | Serval | Atlassian JSM + Rovo | Aisera / Leena AI |
|---|---|---|---|---|---|
| Core design goal | Execute the request end to end | System of record and workflow | Execute, or act as AI layer over incumbent | Service desk inside the Atlassian estate | Deflect and orchestrate across departments |
| Can be system of record | Yes — native ITSM layer | Yes — the market default | Yes — or layer on top | Yes, within Atlassian | Generally no — sits on top |
| Runs on top of existing ITSM | Yes — syncs and hands off | n/a | Yes — explicit “AI layer” motion | Limited | Yes — the primary motion |
| Primary employee surface | Slack and Microsoft Teams | Portal, plus Teams/Slack integrations | Slack and Teams | Help center, portal, Slack | Slack, Teams, email, web |
| Natural-language automation authoring | Yes — Playbooks in plain language | Now Assist plus platform tooling | Yes — natural language generates code | Rovo agents, configurable | Varies by integration depth |
| Identity and access execution | Strong — Okta, Entra, Google, GitHub, AWS, Salesforce | Via integrations and IGA modules | Yes | Via integrations | Depends on configuration |
| Security playbook library | Yes — JIT access, reviews, IR, DLP triage, phishing | Separate SecOps product line | Not a security product | No | No |
| Native OCSF audit output to SIEM | Yes | Not native OCSF | Not published | No | No |
| Integration breadth | 600+ (vendor claim) | Very large ecosystem | Growing | Deep in Atlassian, broad via Rovo connectors | Broad, orchestration-oriented |
| Enterprise track record | Founded 2024 — cloud-native customer base | Two decades, largest estates on earth | Founded 2024, ~$1B valuation | Very large installed base | Established in large enterprise |
| Biggest weakness to expect | No announced Cortex packaging or GA date | Cost and implementation complexity | Young company, no security portfolio | Weak outside Atlassian estate | Deflection-leaning, not deep execution |
Lane 2 · At a glance
Agentic SOC Execution
Every serious SOC vendor now has agents that investigate. The differentiator is whether they can change something outside the security stack when the investigation concludes.
| Dimension | Cortex (AgentiX + Console) | CrowdStrike Charlotte Agentic SOAR | Microsoft Security Copilot | Torq | Tines |
|---|---|---|---|---|---|
| Agentic investigation | Yes — AgentiX agents reason, plan, execute | Yes — multi-agent with shared context layer | Yes — agents across Defender and Entra | Yes — AI SOC platform with agent analysts | Yes — workflow-first with AI |
| Prebuilt integrations | 1,100+ in AgentiX, plus Console’s 600+ | Falcon ecosystem plus marketplace | Strongest inside Microsoft estate | Broad, automation-oriented | Broad, automation-oriented |
| Native MCP support | Yes — in AgentiX | Expanding | Expanding | Yes | Yes |
| Execution outside the security stack | The Console thesis — IT, HR, finance, legal systems | Primarily security tooling and IT integrations | Strong in Microsoft IT estate, weaker outside it | Via integrations, security-led | Via integrations, security-led |
| Employee-facing service desk | Yes — Console’s origin | No | Partly, via M365 Copilot separately | No | No |
| HR context for alert triage | Yes — employment status, role, manager change | Not published | Via Entra and Graph | Via integrations | Via integrations |
| Identity remediation with approvals | Yes — JIT access, revocation, step-up MFA | Identity protection plus response actions | Strong for Entra | Via integrations | Via integrations |
| Shipping today | AgentiX yes; Console-in-Cortex not announced | Yes | Yes | Yes | Yes |
| Biggest weakness to expect | Console packaging and AgentiX overlap undefined | Execution mostly stays within Falcon’s orbit | Drops off sharply outside Microsoft | No detection platform of its own | No detection platform of its own |
Verification
Sources
Competitive claims here are traceable. Check before you quote a number in front of a customer.
Official — Palo Alto Networks
- Palo Alto Networks Acquires Console to Agentify Security, September 1, 2026 — paloaltonetworks.com/company/press/2026/palo-alto-networks-acquires-console-to-agentify-security
- Cortex AgentiX — 1,100+ prebuilt integrations and native MCP support — paloaltonetworks.com/cortex/agentix
- Palo Alto Networks Unveils Cortex AgentiX, October 28, 2025 — prnewswire.com
Competitor primary sources
- ServiceNow to acquire Moveworks for $2.85B, March 10, 2025 — newsroom.servicenow.com
- Serval — raising $75M Series B at a $1B valuation — serval.com
- Torq — $140M Series D at a $1.2B valuation, January 12, 2026 — torq.io/news/torq-seriesd
- CrowdStrike — Charlotte Agentic SOAR — crowdstrike.com/platform/charlotte-ai/agentic-soar
- CrowdStrike unveils next evolution of the agentic SOC, September 2, 2026 — crowdstrike.com/press-releases
- Atlassian — Rovo agents in Jira Service Management — support.atlassian.com
- Console — AI-Native ITSM, product and security pages — console.com/solutions/security
Press reporting — cite as reporting, not fact
- Palo Alto Networks paid $500M for Thrive-backed Console, sources say — TechCrunch, September 2, 2026 — techcrunch.com
- AI startup Serval valued at $1 billion after Sequoia-led round — Reuters, December 11, 2025 — reuters.com
- ServiceNow adds AI muscle with record $2.9 billion Moveworks deal — Reuters, March 10, 2025 — reuters.com
- Palo Alto Acquires Console to Expand Cortex Agentic Security — Security Boulevard, September 2026 — securityboulevard.com
- Torq raises $140M at $1.2B valuation — SiliconANGLE, January 11, 2026 — siliconangle.com
Note on competitor comparisons: the Aisera, Glean, Leena AI, and Salesforce Agentforce assessments draw on a Console-published comparison. Treat them as a starting hypothesis and verify against the vendor’s own materials before using them in a customer conversation.