✳ Misconception M2 / F4

Authentication did not prove which human was present

Authentication proves possession or control of an authenticator bound to a digital identity under NIST SP 800-63-4, not which physical human was sitting at the keyboard or whether the subsequent resource action was authorized.

Wrong claim

Why it feels true

An Identity Provider log showing a successful MFA challenge for dax.mercer@chronos.orbital feels like eyewitness proof that Dax personally initiated the session.

Precise correction

NIST SP 800-63-4 (final 31 July 2025) defines authentication as verifying control of an authenticator bound to a digital identity, which remains distinct from physical human attribution and from downstream authorization decisions.

A shared credential, an unattended unlocked workstation, or an MFA push prompt approved under fatigue can all produce a genuine authentication success log without the named person intending the action.

Principal Security Architect Vera Vance and Propulsion Lead Priya Nair can state as an observed fact that the account authenticated, while treating human presence and export authorization as separate questions requiring corroborating evidence.

NIST SP 800-63-4 Digital Identity Guidelines, final 2025-07-31 ↗

MINI-CHECK

Meridian Space & Robotics' (chronos.orbital) partner portal logs show contractor account ext.rowan passing a phishing-resistant security-key prompt at 03:40 UTC on Sunday and exporting the entire supplier ledger. The contractor is scoped only to the propulsion valve queue. What can Priya Nair and Vera Vance state from the log?

Go deeper

Find your next idea.

Tip: press / to open search. Escape closes this window.