TL;DR: Akeyless's analysis of federal agencies finds machine identities and AI agents create access-scope risk that static credentials and broad entitlements do not close. Security teams need runtime policy, just-in-time issuance, and credential isolation to keep authenticated actors inside task scope.
Editorial analysis by NHI Mgmt Group, based on content published by Akeyless: “Akeyless Brings Modern Identity Security to Federal Agencies”.
Key questions
Q: Why do over-privileged AI connections create outsized risk in federal environments?
A: Because AI systems can turn ordinary access into broad reach very quickly.
Q: How can teams govern machine identities and AI agents in access reviews?
A: Teams should assign ownership, define review cadence, and include machine identities and AI agents in the same certification logic as human access, but with role-appropriate approvers.
Practitioner guidance
- Define task-scoped access for machine identities Map each machine identity and AI agent to a specific task scope, then remove any entitlement that is not required for that task.
- Move privileged access into just-in-time issuance Issue privileged credentials only at the moment of need and make them expire immediately after the action window closes.
- Prevent credential exposure inside AI agents Keep secrets, tokens, and reusable credentials outside the agent runtime so the agent can act without inheriting durable authentication material.
Bottom line: Machine identities and AI agents expose a governance gap that static credentials and broad entitlements do not close.
Glossary terms: Machine Identity, Just-in-Time Access Request, Runtime control, Task Scope Descriptor
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Task-scoped access, not durable credentials, is the governing unit for federal AI adoption: Once machine identities and AI agents enter operational workflows, the question is no longer whether an actor is authenticated. The question is whether its privileges are bounded tightly enough to the work it is supposed to perform. Federal programmes that keep treating authentication as the main control point will continue to over-grant access.
A few things that frame the scale:
- 70% of organisations grant AI systems more access than they would give a human employee performing the exact same job, according to the 2026 Infrastructure Identity Survey.
- 19% of organisations give AI systems dramatically more access than human employees, nearly one in five granting unrestricted privilege, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: Should organisations prioritize securing machine identities before expanding agentic AI use?
A: Yes. If agent identities, tokens, and service accounts are not tightly governed, expanding agentic AI increases the blast radius of every mistake or compromise. Security teams should establish inventory, least privilege, lifecycle control, and revocation paths before scaling deployment.
👉 Read our full editorial: Modern identity security for federal AI agents and machine identities