Notifications
Clear all
Topic starter
22/06/2026 1:43 pm
TL;DR: Palo Alto Networks’ planned acquisition of CyberArk, valued at about $25 billion, signals that identity security, privileged access, and lifecycle governance have become core enterprise controls, especially as AI and cloud access expand, according to SPHERE Technology Solutions. The deal makes identity hygiene and privileged access discipline board-level issues rather than back-office tasks.
NHIMG editorial — based on content published by SPHERE Technology Solutions: analysis of Palo Alto Networks’ planned acquisition of CyberArk and its implications for identity security
Questions worth separating out
Q: How should security teams handle shadow accounts in privileged access programmes?
A: Treat shadow accounts as a governance failure, not just a housekeeping issue.
Q: Why do stale identities weaken least privilege and just-in-time access?
A: Least privilege and just-in-time access depend on current identity state, current ownership, and accurate privilege scope.
Q: How can IAM teams bring machine identities into lifecycle governance?
A: Apply the same lifecycle discipline used for human access to service accounts, tokens, cloud services, and AI-connected identities.
Practitioner guidance
- Audit shadow accounts and orphaned privileges Create a recurring inventory process for abandoned identities, stale privileged roles, and ownership gaps, then route exceptions into remediation workflows before they can be reused.
- Validate identity hygiene before PAM enforcement Check whether your privileged access platform is consuming accurate identity data, current ownership, and up-to-date account status before you trust least-privilege decisions.
- Extend lifecycle governance to machine identities Apply joiner-mover-leaver discipline to service accounts, tokens, cloud services, and AI-connected identities so review and offboarding do not stop at human users.
What's in the full analysis
SPHERE Technology Solutions' full article covers the operational detail this post intentionally leaves for the source:
- How SPHEREboard for CyberArk PAM surfaces orphaned accounts, stale privileges, and misconfigurations in real time.
- How the vendor describes remediation workflows that feed cleaned identity data back into privileged access processes.
- How the article frames identity hygiene for AI agents, DevOps tokens, and ephemeral cloud services in practical terms.
- How SPHERE positions the relationship between visibility, dashboarding, and continuous privileged access remediation.
👉 Read SPHERE Technology Solutions’ analysis of the Palo Alto Networks and CyberArk deal →
Palo Alto acquiring CyberArk: what does it mean for IAM teams?
Explore further
This topic was modified 3 hours ago by Mr NHI
22/06/2026 1:48 pm
Identity security has become a control plane, not a supporting function. The article is right to frame the CyberArk acquisition as a sign that identity now sits alongside perimeter controls in enterprise defence. Once cloud, AI, and privileged access all depend on who or what can authenticate, identity governance becomes a foundational security layer. For practitioners, the implication is that IAM, PAM, and NHI controls can no longer be treated as back-office tooling.
A few things that frame the scale:
- Only 5.7% of organisations have full visibility into their service accounts, according to Ultimate Guide to NHIs.
- Another finding from our research shows that 97% of NHIs carry excessive privileges, which broadens attack surface and complicates lifecycle governance.
A question worth separating out:
Q: Who is accountable when unmanaged privileged identities remain in the environment?
A: Accountability should sit with the service owner, the identity governance function, and the platform team responsible for privileged access control. If no one owns the account, then no one can certify, remediate, or offboard it. The governance gap is as much organisational as technical.
👉 Read our full editorial: Palo Alto’s CyberArk deal shows identity security is now core
