TL;DR: Palo Alto Networks’ planned $25B acquisition of CyberArk signals that identity security has moved from a set of point controls into a platform category, while AI, machine identities, and lateral movement keep widening the attack surface, according to Silverfort. The practical shift is that IAM, PAM, NHI, and AI governance can no longer be treated as separate programmes with separate risk models.
At a glance
What this is: Silverfort argues that Palo Alto Networks’ planned $25B acquisition of CyberArk signals a shift from fragmented identity controls toward identity security as a platform category, driven by AI growth and a larger machine identity attack surface.
Why it matters: IAM, PAM, NHI, and AI governance teams should read this as a sign that identity security is being treated less as infrastructure and more as a cross-cutting control plane for compromise prevention.
Context
Palo Alto Networks’ planned acquisition of CyberArk is being used here as a marker for a broader market shift, not just a transaction. The core issue is that identity has become the control plane for access, privilege, and lateral movement across both human and non-human actors.
Silverfort frames the problem as a mismatch between legacy silos and current attack reality. Human IAM, privileged access, non-human identity control, and AI governance are increasingly intersecting, which makes isolated tools harder to govern as a coherent security programme.
Key questions
Q: How should IAM teams respond when identity protection becomes a platform consolidation story?
A: They should re-check whether governance, lifecycle management, and enforcement are still split across different owners and tools. Consolidation changes the operating model, so the key question is not which vendor wins, but whether the programme can still prove coverage across human and non-human identities without duplicate control gaps.
Q: Why do machine identities complicate privileged access management?
A: Machine identities complicate PAM because they expand the number of non-human access paths and shorten the time between privilege assignment and use. Traditional vaulting and rotation help, but they do not by themselves solve over-provisioning, federated access chains, or the need for continuous review of how access is actually consumed.
Q: What breaks when AI agents are governed like ordinary service principals?
A: The main failure is that ordinary service-principal governance assumes a stable workload with predictable lifecycle and entitlement patterns. AI agents can inherit access from a blueprint, act through user-shaped interfaces, and change their operational state at runtime, so the control model no longer matches the behaviour. Teams need a separate governance view for the agent runtime, not just for the underlying credential object.
Q: What is the difference between IAM and identity security?
A: IAM governs authentication and authorization, while identity security evaluates whether access remains appropriate in context and over time. IAM can tell you who signed in and what policy allowed it. Identity security tells you whether the resulting access is still justified, over-permissioned, or risky for the current environment.
Technical breakdown
Identity security as a platform layer
Identity security is moving beyond a collection of adjacent controls and into a dedicated protection layer. The practical distinction is between identity infrastructure, which manages accounts and lifecycle, and identity security, which is meant to detect abuse, constrain privilege, and reduce compromise paths across that infrastructure. That matters because attackers rarely respect product boundaries. They move from authentication to privilege escalation to lateral movement across systems that were designed to be managed separately. A platform model tries to unify visibility and response across those paths rather than leaving each silo to defend itself in isolation.
Practical implication: Treat identity controls as one security domain with shared detection and enforcement requirements, not as disconnected admin functions.
Machine identities and the identity attack surface
The article points to the growth of non-human identities such as API keys, tokens, and service accounts as a major expansion of the attack surface. These identities are often numerous, poorly inventoried, and granted privileges that outlive the tasks they were meant to perform. That combination creates standing access that attackers can exploit once they obtain a credential or token. In identity terms, the problem is not just the existence of machine identities. It is the difficulty of proving ownership, scoping privilege, and maintaining control over their lifecycle at enterprise scale.
Practical implication: Build inventory, privilege scoping, and lifecycle governance for machine identities into the same operating model used for privileged human access.
AI agents and the new identity boundary
Silverfort’s framing draws a line between ordinary machine identities and AI agents, which may need their own protection model. The technical reason is that agentic systems can select actions dynamically, use tools, and interact with data in ways that do not fit older assumptions about static service accounts or user sessions. Once AI systems can initiate work, request access, and chain actions, identity controls have to account for runtime behavior as well as assigned privilege. That changes the governance problem from simply authenticating the entity to constraining what it can do in motion.
Practical implication: Separate AI agent governance from legacy workload identity controls and evaluate whether runtime privilege boundaries still hold.
Threat narrative
Attacker objective: The objective is to turn one compromised identity into wider enterprise reach by using trust relationships, standing privilege, and weak governance between identity silos.
- Entry occurs when attackers obtain an identity foothold through compromised credentials, tokens, or overused privileged access paths rather than through perimeter compromise.
- Escalation follows when that identity grants broader access than intended, allowing movement from initial access into privileged systems or adjacent services.
- Impact comes from lateral movement and privilege abuse across interconnected environments, turning identity compromise into broader operational compromise.
Breaches seen in the wild
- Sisense breach 2024: A credential in Sisense's GitLab reportedly opened S3 buckets of customer tokens, passwords and certificates; CISA urged a full reset.
- Palo Alto Networks Salesforce data theft 2025: Stolen Drift OAuth tokens exposed Palo Alto Networks CRM data, including support notes where some customers had shared credentials.
Read our 52 NHI Breaches Analysis report for a comprehensive view of breaches impacting Non-Human Identities including AI Agents.
NHI Mgmt Group analysis
Identity security has crossed the threshold from tooling category to control plane. The article reflects a market where compromise prevention is no longer credible if identity is treated as an admin layer beneath security. Identity now governs access, privilege, and movement across human, machine, and AI-driven workflows. Practitioners should read that as a signal to align governance around the control plane, not the product stack.
Machine identities expose a governance gap, not just an inventory problem. API keys, tokens, and service accounts outnumber humans in many enterprises, but volume alone is not the issue. The issue is that these identities often carry privileges that are hard to see, hard to certify, and easy to reuse. The implication is that lifecycle governance for NHIs is no longer a side programme; it is part of core identity risk management.
AI agents break the assumption that identity is a stable, reviewable subject. Access review processes were designed for identities whose privilege could be observed, certified, and revoked on a human governance cadence. That assumption fails when an agent can acquire, use, and discard access as part of runtime execution. The implication is not just more control, but a rethink of what is actually governable as an identity object.
The market is converging on unified identity governance because silos no longer match attack paths. The article’s critique of separate PAM, MFA, NHI, ITDR, and ISPM categories reflects a wider truth: attackers chain them together whether teams do or not. That creates a governance problem across ownership boundaries, not only across tools. Practitioners should expect identity programmes to be judged on how much of that chain they can see and interrupt.
Identity blast radius is becoming the more useful unit of risk than single-control maturity. The most relevant question is not whether one control exists, but how far a compromised identity can travel before detection or revocation. That applies across human users, non-human identities, and AI agents. Practitioners should prioritise reducing reachable privilege over preserving separate programme boundaries.
What this signals
Identity programmes now have to be judged by blast radius, not by the number of point controls deployed. When the same trust relationships connect PAM, MFA, NHI, and AI workflows, the question is how far one compromised identity can move before containment kicks in. That makes governance about reach, not just coverage.
Non-human identities should be managed as a lifecycle problem, not a tooling category. Inventory without offboarding, or privilege without ownership, leaves the organisation with credentials that persist beyond their business purpose. The programme issue is whether every non-human identity has a clear controller, scope, and retirement path.
AI governance and identity governance are converging operationally. The rise of agentic systems means identity teams will increasingly need to decide which identities can initiate actions, which can call tools, and which require separate runtime controls. That makes agent oversight part of core identity design rather than an adjacent AI policy exercise.
For practitioners
- Map identity security as a control plane Inventory where authentication, privilege enforcement, detection, and revocation are split across tools and owners, then identify which gaps let identity compromise travel between silos.
- Consolidate non-human identity governance Bring API keys, tokens, and service accounts under one lifecycle and privilege model so ownership, rotation, and offboarding are handled consistently.
- Separate AI agent access from workload identity assumptions Review whether agent workloads are still governed like static service accounts, especially where runtime actions, tool use, and delegated access can change during execution.
- Reduce identity blast radius Focus on shrinking the privilege reachable from any one identity, especially where lateral movement between systems is possible through shared trust relationships.
Key takeaways
- Identity security is being recast as a platform-layer control problem rather than a loose set of adjacent tools.
- Machine identities and AI agents expand the attack surface in ways that make siloed governance less effective.
- Practitioners should reduce identity blast radius by aligning lifecycle, privilege, and runtime control across human and non-human identities.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
OWASP Non-Human Identity Top 10, OWASP Agentic AI Top 10 and MITRE ATT&CK address the attack and risk surface, while NIST CSF 2.0 sets the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| OWASP Non-Human Identity Top 10 | NHI-05 — Overprivileged NHI | The article centers on machine identities and excessive privilege across identity silos. |
| NHI-07 — Long-Lived Secrets | API keys and tokens remain central to the article's machine identity risk discussion. | |
| Recommendation — Reduce overprivileged non-human identities by aligning access scope to task need and revoking standing excess. Shorten secret lifetimes and remove persistent credentials that extend identity blast radius. | ||
| OWASP Agentic AI Top 10 | ASI03 — Identity & Privilege Abuse | The article explicitly distinguishes AI agents as a separate identity governance challenge. |
| Recommendation — Apply agent identity controls that bound privilege and stop runtime abuse of delegated access. | ||
| NIST CSF 2.0 | PR.AA-05 — Access Permissions, Entitlements and Authorizations | The article is fundamentally about access, privilege, and authorisation across identity types. |
| Recommendation — Govern entitlements centrally so access permissions can be reviewed and constrained across the full identity estate. | ||
| MITRE ATT&CK | TA0006;TA0008 — Credential Access; Lateral Movement | The article uses identity compromise and lateral movement as the core threat pattern. |
| Recommendation — Map identity risks to credential access and lateral movement to prioritise the controls that block expansion after compromise. | ||
Key terms
- Identity Security: Identity security is the discipline of governing who and what can access systems, data, and tools, then proving those decisions are enforced. In practice it spans human users, service accounts, tokens, certificates, and AI agents across the full access lifecycle.
- Non-Human Identity (NHI): A digital identity assigned to a non-human entity such as a software application, service account, API key, bot, machine, or AI agent that enables it to authenticate and interact with systems without direct human involvement. NHIs now outnumber human identities in most enterprises by 25 to 50 times.
- Identity Blast Radius: The amount of damage a compromised identity can cause across systems, data, and infrastructure. In NHI environments, it is shaped by permissions, network reach, and administrative capability rather than by the credential alone. Reducing blast radius is a containment strategy that limits lateral movement and data exposure.
- Agentic Identity: An agentic identity is a non-human identity used by an autonomous system that can act, call tools, and access data with execution authority. It needs the same governance discipline as other privileged identities, plus runtime context, ownership mapping, and revocation paths.
Deepen your knowledge
NHI governance, agentic AI identity, and machine identity lifecycle are core topics in our NHI Foundation Level course, the industry's only accredited NHI security programme. If you are responsible for identity security strategy or NHI governance in your organisation, it is worth exploring.
Published by the NHIMG editorial team on June 24, 2026.
Updated on October 6, 2026.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org