Topic starter
24/06/2026 7:21 pm
TL;DR: Akeyless says AI agents and machine identities are forcing identity security beyond human-era models, with the company citing hundreds of billions of workload identity transactions annually and enterprise adoption. Static privileges and long-lived credentials no longer fit runtime access decisions in agent-driven environments.
Editorial analysis by NHI Mgmt Group, based on content published by Akeyless: “Former CyberArk and Cisco Leader Joins Akeyless as It Scales Identity Security for the Agentic Era”.
Key questions
Q: How should security teams govern AI agents that can access enterprise systems?
A: Security teams should govern AI agents as non-human identities with explicit ownership, scoped privileges, and continuous monitoring.
Q: Why do standing privileges make machine identities harder to secure?
A: Standing privileges extend the period in which a compromised secret can be abused, which enlarges the blast radius of a single exposure.
Q: Where does NHI governance fail when access is still standing at runtime?
A: It fails when teams assume a credential can be safely reviewed after it has already been used.
Practitioner guidance
- Define runtime authorisation boundaries Map which AI agents, workloads, and service accounts need decisions at execution time rather than at provisioning time, and document the conditions that can change access mid-task.
- Replace standing privilege with task-scoped access Inventory persistent machine and agent privileges, then reduce each one to the smallest task scope and shortest feasible lifetime.
- Shorten credential validity and revoke on task completion Tie non-human credentials to explicit expiry and revocation events so access cannot outlive the work that justified it.
Bottom line: AI agents and machine identities are exposing a mismatch between static IAM models and the pace of runtime execution.
What's in the full announcement
Akeyless's full article covers the operational detail this post intentionally leaves for the source:
- The strategic partnership and ecosystem rationale behind the appointment
- The vendor's view of how AI agents, workloads, and humans fit into one control plane
- Examples of the integrations and frameworks the platform supports across clouds and enterprise systems
- The practical claims around just-in-time identity creation and secure federation in dynamic environments
👉 Read Akeyless's analysis of real-time identity control for AI agents and machine identities →
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
25/06/2026 4:36 am
Runtime identity control is becoming the governing model for AI-era access. Identity programmes built for human administration assume access is issued, used, and reviewed in separate phases. That assumption weakens when AI agents and workloads execute at machine speed across cloud and SaaS systems. The practical conclusion is that entitlement governance has to move closer to the moment of use.
A question worth separating out:
Q: What happens when cross-cloud federation is broader than the actual task?
A: The identity becomes portable in ways the business did not intend, which can expose internal systems, create overreach across platforms, and make revocation harder to enforce consistently. Federation should extend trust only as far as the current workload or agent needs it.
👉 Read our full editorial: Akeyless strategy hire underscores the shift to real-time identity control