Join our Newsletter — 33% off our NHI Course

Can PKI-based identity keep agentic AI within its authority?

 

(@nhi-mgmt-group)
Member Moderator
Joined: 2 years ago
Posts: 20230
Topic starter  

TL;DR: Agentic AI can authenticate with PKI-based identity yet still exceed its intended authority, Keyfactor found. Runtime authorisation, ownership, and certificate lifecycle need to stay aligned so valid credentials do not outlast the task they support.

Editorial analysis by NHI Mgmt Group, based on content published by Keyfactor: “Keyfactor Validates PKI-Based Identity for Securing Agentic AI”.

Key questions

Q: Why is authentication alone not enough for agentic AI access control?

A: Authentication answers whether the agent can prove its identity, but agentic AI can still take actions that exceed the original intent of that identity.

Q: What fails when AI agents keep valid certificates after their task changes?

A: The failure is governance, not cryptography.

Q: How should security teams govern PKI-based identity for AI agents?

A: They should treat certificates as the start of governance, not the finish.

Practitioner guidance

  • Map agent identities to explicit owners Require every agent certificate or credential to have a named business owner, a technical custodian, and a revocation path tied to that ownership.
  • Bind privilege to task scope Issue access only for a defined task boundary and prohibit reusable standing permissions that remain valid after the task completes.
  • Review certificate lifecycle for agents Align issuance, rotation, expiry, and revocation for agent certificates with the agent lifecycle rather than with infrastructure deployment cycles.

Bottom line: Agentic AI makes authentication necessary but not sufficient, because a trusted identity can still exercise unsafe runtime authority.

Glossary terms: Agentic AI Identity, Runtime Authorisation, Certificate Lifecycle Management, Task-Scoped Access

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →


This topic was modified 1 week ago by NHI Mgmt Group

   
Quote
(@mr-nhi)
Member Moderator
Joined: 6 months ago
Posts: 20712
 

PKI-based identity for agentic AI is necessary but not sufficient: cryptographic proof of identity solves authentication, not governance. The article highlights a familiar failure mode in a new form: organisations can verify an agent without meaningfully constraining what it does after verification. The practitioner takeaway is that authentication for agents must be paired with runtime authorisation and lifecycle control, or trust becomes a thin wrapper over autonomy.

A few things that frame the scale:

  • 67% of organisations still rely heavily on static credentials despite the risks they pose to agentic AI deployments, according to the 2026 Infrastructure Identity Survey.
  • Only 13% of organisations feel extremely prepared for the reality of agentic AI despite the majority racing toward autonomous adoption, according to the 2026 Infrastructure Identity Survey.

A question worth separating out:

Q: What is the difference between PKI identity and agent authorisation?

A: PKI identity establishes cryptographic trust in the actor, while authorisation defines what that actor is allowed to do. For agentic AI, those are separate decisions because the agent may be trusted to authenticate but still need tight limits on tool use, data access, and delegated execution. Conflating the two leaves runtime behaviour under-governed.

👉 Read our full editorial: PKI identity for agentic AI highlights a trust gap in governance


This post was modified 1 week ago by NHI Mgmt Group

   
ReplyQuote
Share:

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.