Topic starter
26/08/2026 11:51 am
TL;DR: At RSAC 2026, a hard governance problem framed agentic AI security: how businesses prove a specific human approved a high-consequence action, while also extending passwordless and enrollment workflows for human identities, according to Yubico. The real issue is that accountability for AI-driven actions breaks when approval is not cryptographically bound to the actor and event.
Editorial analysis by NHI Mgmt Group, based on content published by Yubico: “Yubico’s commitment to securing the future of digital identities: Reflecting on RSAC 2026”.
Key questions
Q: Who should approve high-risk actions taken by an AI agent?
A: A verified human should approve high-risk agent actions before execution, especially where money, sensitive data or privilege changes are involved.
Q: Why do passwordless systems still need identity governance?
A: Passwordless systems still need identity governance because authentication strength does not answer lifecycle questions.
Q: What breaks when AI actions are not bound to a human approver?
A: Without a verifiable human approval step, high-consequence AI actions become difficult to attribute, contest, or reconstruct after the fact.
Practitioner guidance
- Define a high-consequence approval policy for AI agents Identify which agent actions require a cryptographically verified human authorisation step, and distinguish those from low-risk automated actions.
- Bind approval evidence to the exact action Capture the actor, action payload, timestamp, and approver identity in one tamper-resistant record so approval cannot drift from execution.
- Review enrollment and recovery governance Treat hardware key enrolment, re-enrolment, and account recovery as controlled lifecycle events with explicit ownership and auditability.
Bottom line: The article frames agentic AI governance as an accountability problem, not just an authentication problem.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
26/08/2026 11:51 am
Approval without cryptographic binding is not accountability. The article exposes a familiar governance error: organisations often treat workflow approval as evidence of authorisation even when the approval is not bound to the exact AI-driven action. That assumption is brittle in agentic systems because the actor can separate request, approval, and execution across different moments and contexts. Practitioners need to stop treating generic sign-off as sufficient proof of authority.
A question worth separating out:
Q: What is the difference between authentication and authorisation in agentic AI governance?
A: Authentication proves who or what is present, while authorisation proves whether that identity is allowed to perform a specific action. In agentic AI, both matter, but authorisation becomes more important because the system can act at runtime. A secure login alone does not establish that the agent’s next action was approved.
👉 Read our full editorial: Hardware-backed approval for AI agents exposes the accountability gap