Topic starter
25/06/2026 12:58 am
TL;DR: Forcing AI to use MFA creates borrowed-credential risk, operational friction, and weak identity boundaries, according to Defakto Security. Instead, the vendor proposes delegation with multi-attestation based on code integrity and runtime context. The identity model matters because human authentication assumptions break when non-human actors need their own access path.
Editorial analysis by NHI Mgmt Group, based on content published by Defakto Security: “MFA vs Multi-Attestation: Why AI Needs a New Identity Model”.
Key questions
Q: How should security teams govern AI access without forcing MFA on machines?
A: Treat AI as a separate identity class.
Q: Why do human authentication controls create risk when applied to AI systems?
A: They create risk because they assume a person is present to complete login, own the credential lifecycle, and remain accountable for the session.
Q: What breaks when an AI system uses borrowed user credentials for CMMC-scoped work?
A: Borrowed credentials break attribution, least-privilege review, and identity-bound audit evidence.
Practitioner guidance
- Separate human and AI authentication paths Stop routing AI access through human MFA flows.
- Require runtime attestation before access is issued Use code integrity, origin, and orchestration context as gating evidence for AI access.
- Replace long-lived human tokens with short-lived delegated credentials Issue credentials only after fresh proof and keep their lifetime tied to the task.
Bottom line: For AI systems, forcing human MFA onto the access path creates borrowed-credential exposure and weakens identity boundaries.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
25/06/2026 10:06 am
Human MFA is a borrowed control when the actor is an AI system. MFA was designed around human interaction, stable users, and credential lifecycles that assume a person can complete the login ceremony. When applied to AI, it often forces borrowed human credentials into non-human workflows, which blurs ownership and widens the access boundary. The implication is that identity governance must stop treating AI access as a human authentication variant and start treating it as a distinct identity class.
A few things that frame the scale:
- 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.
- Systems with least-privileged AI access had a 17% incident rate vs 76% for over-privileged systems. Organisations failing to scope AI access properly are 4.5x more likely to experience a security incident, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: What is the difference between delegated agent access and impersonation in AI systems?
A: Delegated access keeps both the user and the acting agent visible in the token chain, while impersonation makes the agent indistinguishable from the user. Delegation is usually the safer pattern because it preserves attribution, supports per-hop authorization, and keeps an audit trail intact. Impersonation can hide the actor, which weakens forensics and accountability after an incident.
👉 Read our full editorial: AI identity models need attestation, not human MFA rituals