Cortex — Agentic Enterprise Operations
Cortex Console
The Execution Layer
Palo Alto Networks acquired Console on September 1, 2026 to give Cortex the ability to do the work, not just find it. Console is an AI-native service management platform that takes a plain-language request, gathers context, and completes the task across identity, devices, and apps — with approvals and an audit trail. Financial terms were not disclosed.
Product brief
One-line value
Palo Alto Networks acquired Console on September 1, 2026 to give Cortex the ability to do the work, not just find it. Console is an AI-native service management platform that takes a plain-language request, gathers context, and completes the task across identity, devices, and apps — with approvals and an audit trail. Financial terms were not disclosed.
- Who buys
- Pains solved: not a separate section on this page
- Discovery questions
- Key capabilities
- Competitors: not a separate section on this page
- Related plays: not a separate section on this page
- Details
Who buys
Qualification
Who Needs This
Console’s pre-acquisition customer list is a strong signal: cloud-native, identity-heavy, fast-growing companies with small IT teams. The Cortex opportunity is broader, but the pattern still holds.
Small IT team, high request volume
An IT or IT Ops team of 4 to 40 supporting hundreds or thousands of employees, drowning in access requests, password and MFA resets, onboarding, and hardware. They cannot hire their way out and they know it.
Opening line: what share of your ticket volume is work nobody would miss if it happened automatically?
Identity-heavy SaaS estate
Okta or Entra plus dozens or hundreds of SaaS applications, with standing privilege accumulating and access reviews done in spreadsheets. Often has a SOC 2 or ISO obligation forcing periodic review.
Opening line: how do you prove today that access granted eight months ago is still needed?
Existing Cortex customer with a remediation gap
Already running XSIAM or XDR. The SOC detects and decides well, then the fix stalls in an IT queue because the analyst cannot change an entitlement or reset a credential themselves.
Opening line: after your SOC decides what to do, how long until the change is actually made?
ITSM contract coming up for air
Paying heavily for a legacy ITSM platform of record, seeing limited automation for the money, and either approaching renewal or already piloting an AI layer on top of it.
Opening line: is the platform you are renewing resolving requests, or just tracking them?
Compliance-driven access governance
Audit findings on access reviews, offboarding completeness, or privileged access. The budget sits in GRC or internal audit, not the SOC — a different buying center with its own money.
Opening line: which audit finding did you close with a manual process you will have to repeat next quarter?
Security and IT run on separate queues
Security understands the threat; IT holds the authorization to change the affected system. Separate tools and separate queues create a handoff that adds hours or days to every response.
Opening line: who is authorized to make the change, and are they in the same ticket as the person who found the problem?
Qualify in when you hear
- “We can’t hire fast enough on the service desk.” Capacity pain with no headroom is the cleanest trigger.
- “Access reviews are a spreadsheet exercise.” Standing privilege plus an audit clock.
- “Offboarding takes a week and we still miss apps.” Especially the non-SSO long tail.
- “Our SOC finds it, then waits on IT.” The handoff gap this deal exists to close.
- “We already automate with scripts nobody maintains.” Brittle automation with a single owner who has left.
- “Everything happens in Slack anyway.” The surface Console is built for.
Qualify out or slow down when
- They want a committed Cortex SKU and GA date. Neither exists yet. Do not invent one.
- Air-gapped or heavily on-premises IT. Console’s integration model assumes cloud identity and SaaS.
- No cloud identity provider. Without Okta, Entra, or Google as an anchor, most playbooks have nothing to act on.
- Policy forbids any automated write to identity systems. You can still sell read-only triage and enrichment, but scope it honestly.
- They are mid-deployment on Cortex AgentiX. Clarify the overlap first or you will create internal confusion.
- Sub-100 employees. Real pain, but rarely enough volume to fund the platform.
Discovery questions
In The Meeting
Discovery Questions
Twelve questions that surface whether the execution gap is real in this account.
Key capabilities
The Deal
The Acquisition — What Is Confirmed
Separate the official record from the press reporting. Customers and competitors will quote both back at you.
| Detail | What is confirmed | Confidence |
|---|---|---|
| Announcement date | September 1, 2026, Santa Clara — announced alongside Palo Alto Networks’ fiscal Q4 and full-year FY26 results | Official (PANW press release) |
| Status | “Has acquired” — stated as completed, not pending | Official |
| Purchase price | Not disclosed by Palo Alto Networks. TechCrunch reported $500M in cash and stock citing two people familiar with the deal; PANW declined to comment | Press-reported — do not state as fact |
| Destination | Cortex. Console “will help advance this vision by deepening our agentic capabilities in Cortex” | Official |
| SKU / packaging | Not announced. No Cortex offering has been named as the delivery vehicle | Unknown — say so |
| GA timing | Not announced. No integration timetable published | Unknown — say so |
| Relationship to AgentiX | Not explained. PANW has not detailed how Console differs from, or combines with, existing Cortex AgentiX capability, nor which Console capabilities land first | Unknown — say so |
| Console standalone future | Not announced. Whether Console continues to be sold as an IT service management product in its own right has not been stated | Unknown — say so |
| Founder | Andrei Serban, Co-Founder and CEO; founded 2024; previously founded Fuzzbuzz (acquired by Rippling) | Confirmed (PANW + TechCrunch) |
| Funding history | ~$29M total: $6.2M seed led by Thrive Capital, $23M Series A led by DST Global with Thrive. Other investors include SV Angel and Abstract Ventures. Nikesh Arora participated personally as an angel investor | Press-reported (TechCrunch/PitchBook) |
| Prior valuation | ~$157M pre-acquisition, per PitchBook | Press-reported |
| Deal sequence | Seventh Palo Alto Networks acquisition of 2026, per PitchBook | Press-reported |
Architecture
How It Works
Console describes itself as a modular platform in three layers built over a Context Graph.
Surface Modules
Where people meet it. A single front door in Slack and Microsoft Teams, plus a native ITSM layer for requests, approvals, actions, and outcomes. Console can be the system of record, or it can sync and hand off to an existing one while remaining the execution layer.
AI Layer
The Assistant and the agents. Interprets plain-language requests, consults the knowledge base and access policies, runs Playbooks, decides when to act and when to escalate. The Assistant will also build an integration on request by reading the target API’s documentation, without engineering work.
Foundation
The Context Graph plus connectivity — 600+ integrations per Console’s own materials — spanning identity providers, HRIS, devices, SaaS, finance, legal, and knowledge sources. This is the layer that knows the customer’s environment well enough for an agent to act on it.
Representative Workflows
What It Automates Today
Details
Overview
What Console Actually Is
Console is an AI-native service management platform. An employee asks for something in plain language inside Slack or Microsoft Teams — “I’m locked out of my laptop,” “I need access to the production Salesforce org,” “reset my MFA.” Console reads the request, pulls the context that matters (who this person is, their manager, their role, their device, their location), checks it against company policy, and then completes the work in the real systems — Okta, Entra, Google Workspace, Microsoft 365, GitHub, AWS, Jamf, Intune. When a human is needed, it opens a properly structured ticket with the full context already attached.
The distinction that matters for a Cortex conversation: most AI service desk tools classify, answer, and route. Console was built to execute. It has its own native ticketing layer if a customer wants to run everything on it, and it can equally sit as an orchestration and execution layer on top of an existing ITSM system of record. Console markets itself on a claim that it automates the majority of inbound service requests — the company’s own site cites 75%+ of service requests in one place and 50%+ of internal support requests in another, which tells you it varies heavily by scope and tuning. Treat both as vendor marketing, not a commitment.
Console was founded in 2024 by Andrei Serban, whose previous company, Fuzzbuzz, was a code security platform acquired by Rippling. It raised roughly $29M across two rounds — a $6.2M seed led by Thrive Capital and a $23M Series A led by DST Global with Thrive — and was valued around $157M before the acquisition, per PitchBook. Named customers reported across public sources include Databricks, Ramp, Scale AI, Webflow, Flock Safety, Cursor, and Bloomerang — a profile worth noting: high-growth, cloud-native, identity-heavy companies with small IT teams, not traditional ServiceNow estates.
Plain Language
Jargon, In Plain Language
Use these definitions in front of a business buyer. Every one of these terms will come up and most of them get used loosely.
The Cortex-Relevant Half
Security Playbooks
Console started in IT and extended into security workflows before the acquisition. These are the published playbooks — and they are the reason this deal makes sense next to XSIAM.
| Playbook | What it does | Why it matters in a Cortex deal |
|---|---|---|
| User access reviews & revocation | Scheduled playbooks identify stale or unused access and either revoke it automatically or route it for review. | Reduces standing privilege and produces audit evidence — a compliance-funded entry point that does not depend on a SOC budget. |
| Just-in-time privileged access | Time-bound access policies with approval flows for business-critical apps. Access expires on its own and is documented in a ticket or artifact. | The strongest single story. Directly adjacent to the Idira / CyberArk identity conversation and easy for a CISO to justify. |
| Security alert triage & context | Enriches incoming alerts with identity, user, device, and application context before an analyst reads them. | Overlaps conceptually with XSIAM enrichment. Ask which side of the line the customer wants it on rather than selling both. |
| Incident response | Triggers playbooks from EDR or other security events, with a human in the loop for triage and response. | This is the handoff Cortex has always had to hand off. Console can carry the remediation into IT-owned systems. |
| Incident management | Automates coordination — creates the Slack channel, adds the right stakeholders, opens the incident ticket with context attached. | Unglamorous and universally painful. Good demo material because every customer recognizes it instantly. |
| Phishing & suspicious email triage | Self-serve submission for employees, streamlined initial assessment, and only credible threats routed onward. | Pairs with Cortex Advanced Email Security. Note the overlap and scope one owner. |
| Insider risk & DLP alert triage | Enriches DLP, CASB, and insider-risk alerts with HR context — employment status, role, recent manager change — routes high-signal events and auto-closes low-risk noise. | HR context is the piece a SIEM genuinely does not have. This is a real differentiator, not a repackaged feature. |
| Vulnerability assessment | Determines exposure to a specific vulnerability across employee devices and cloud infrastructure so impact can be scoped quickly. | “Are we affected by this CVE” is the question that consumes a week. Complements, not replaces, Cortex Cloud and Xpanse. |
| Employee offboarding (security lens) | Removes access across systems including non-SSO applications through app-owner coordination. | The non-SSO long tail is where offboarding actually fails. Worth asking about explicitly in discovery. |
| Compliance tracking | Integrates with compliance systems to track issues and deadlines, notifies employees with remediation steps, keeps owners informed. | Opens a GRC-budget conversation that sits outside the usual Cortex buying center. |
| Tool migration & secure deployment | Supports projects such as identity provider migrations and EDR rollouts with controls built into the rollout to catch configuration gaps early. | Notably relevant to Optiv delivery work — this is deployment assurance, and it is a services conversation as much as a product one. |
| Device compliance & remediation | Identifies non-compliant devices and drives the remediation steps. | Closes the loop between what XDR observes on the endpoint and what IT has to change to fix it. |
The Objection You Will Get First
Governance and Guardrails
“You want an AI agent with write access to my identity provider?” Have this answer ready before the question lands.
Console’s published position is that agents do not receive write access to connected systems by default. An administrator has to explicitly configure an action before an agent can change anything. Everything else layers on top of that starting point.
Portfolio
Where Console Fits In Cortex
The strategic logic is a straight line: Cortex got very good at knowing what happened and what should be done. Console is about the doing.
A security incident usually starts in an identity system, an endpoint, or an application. Remediating it usually requires changing a permission, resetting a credential, or reconfiguring something — and that authority sits with IT, in a different tool and a different queue. The team that understands the threat is not the team authorized to change the affected system. That handoff is where response time actually goes.
The intended progression is: Cortex interprets the signal, decides what deserves attention, assembles context, and prepares the change; an approver authorizes it; a Console-derived agent executes it in the affected system and records the outcome. If that lands, Cortex becomes the place investigation, prioritization, and response all happen — rather than a place where analysts examine information and then file a request somewhere else.
| Adjacent product | Relationship | How to talk about it |
|---|---|---|
| Cortex AgentiX | Overlapping, and unresolved. AgentiX launched in October 2025 as the next generation of XSOAR, with prebuilt agents that reason, plan, and execute, over 1,100 prebuilt integrations, and native MCP support. Console arrives with its own agent runtime, its own playbook model, and its own integration library. | Say the overlap out loud. AgentiX is the security-operations agent platform and is shipping today. Console’s heritage is enterprise and IT operations — the systems outside the SOC where remediation has to land. Palo Alto Networks has not published how they converge. If the customer needs certainty now, sell AgentiX. |
| Cortex XSOAR | The original orchestration and automation engine, with the large playbook library. AgentiX is its stated evolution. | Customers deep in XSOAR content should hear a continuity story, not a replacement story. Nothing announced changes their XSOAR position. |
| Cortex XSIAM | Detection, correlation, and case management — the decision layer. Console is a candidate execution layer beyond the security stack, and it already writes OCSF audit logs. | The cleanest joint story: XSIAM decides, Console executes, and Console’s own activity flows back into XSIAM as auditable evidence. |
| Identity (Idira / CyberArk) | Highly complementary. Console’s strongest playbooks — JIT privileged access, access reviews, revocation, offboarding — are identity workflows. | Use Console to make an identity conversation operational. A privileged access platform defines the policy; an agent that enforces and expires it converts policy into practice. |
| Cortex Advanced Email Security | Partial overlap on phishing triage. | Email security handles detection and mail-flow enforcement. Console’s phishing playbook is employee self-service intake and initial assessment. Scope one owner per account. |
| Cortex Cloud / Xpanse | Complementary on exposure. Console’s vulnerability assessment playbook answers “are we affected” across devices and cloud infrastructure. | Cloud and Xpanse find and prioritize exposure. Console helps scope organizational impact and drive the remediation work through the people who own it. |
| Cortex AES (Koi) | No functional overlap, but a matched pair in the pitch. | AES governs AI agents that arrive uninvited on the endpoint. Console is the AI agent you deliberately give authority to. Together they make the agentic AI conversation coherent in both directions. |
Accuracy
Boundaries — State These Before A Customer Finds Them
- No Cortex SKU, packaging, or price. Nothing has been announced. If a customer needs to budget for this in the current fiscal year, that is a conversation with the product team, not a commitment you make.
- No GA date or integration timetable. Console-derived capability inside Cortex is not stated to be generally available today.
- The AgentiX relationship is genuinely undefined. Palo Alto Networks has not said how Console differs from AgentiX, how the two combine, or which Console capabilities integrate first.
- The $500M figure is press-reported, not disclosed. TechCrunch, two sources, cash and stock; PANW declined to comment. Cite it as reporting or not at all.
- Automation rates are vendor claims. Console’s own site cites both 75%+ of service requests and 50%+ of internal support requests. The real number depends entirely on scope, integration depth, and tuning. Do not put either in a business case as a commitment.
- Autonomy is not the same as capability. Console can execute; whether a given customer lets it execute unattended is a governance decision they make, and most will start with approvals on everything.
- Console’s pre-acquisition base skews cloud-native. Databricks, Ramp, Scale AI, Webflow, Cursor. There is no published evidence yet of the same results in a large, heavily regulated, on-premises estate.
- Console’s standalone future is unstated. Whether it continues to be sold as an independent IT service management product has not been announced. Do not promise a customer they can buy it that way.
Verification
Sources
Official Palo Alto Networks properties first. Press reporting is labeled as such.
Official — Palo Alto Networks
- Palo Alto Networks Acquires Console to Agentify Security, press release, September 1, 2026 — paloaltonetworks.com/company/press/2026/palo-alto-networks-acquires-console-to-agentify-security
- Cortex AgentiX product page — paloaltonetworks.com/cortex/agentix
- Cortex AgentiX documentation, MCP integrations — docs-cortex.paloaltonetworks.com
- Palo Alto Networks fiscal Q4 and FY26 results — investors.paloaltonetworks.com
Console product materials (vendor claims)
- Console — AI-Native ITSM — console.com
- What Is Console? AI Agents for Automating IT Tasks — console.com/faq/what-is-console-ai-it-agent
- AI Agents for Security — 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
- Palo Alto Acquires Console to Expand Cortex Agentic Security — Security Boulevard, September 2026 — securityboulevard.com
- Palo Alto Networks beats quarterly earnings estimates, acquires AI platform — Reuters, September 1, 2026 — reuters.com
- Palo Alto Buys Console — Cortex into IT workflows — quasa.io