-
Notifications
You must be signed in to change notification settings - Fork 0
oauth agent identity presence gap
Nicolas Cravino edited this page Jul 29, 2026
·
1 revision
id: oauth-agent-identity-presence-gap title: OAuth Can Prove Who Your Agent Works For. It Cannot Prove Where That Person Is Standing. tags: [security, compliance, zero-trust] category: oscal-compliance published: 2026-07-29 created: 2026-07-29 updated: 2026-07-29 freshness: fresh date_source: git-commit source_file: OAuth-Can-Prove-Who-Your-Agent-Works-For-It-Cannot-Prove-Where-That-Person-Is-Standing.md
AI agents inherit our identities but not our geography. A delegated token minted in New York lets an agent in a Virginia datacenter render covered US payment data to a hotel Wi-Fi session in Shanghai while every control passes — the structural gap the DOJ Data Security Program and CISA requirements now make a compliance problem. Companion article to the oscal-presence-gate repo.
- Identity propagates through delegation; presence does not — location controls end up evaluating the wrong party (the agent's datacenter, not the human behind the request). [^src:articles-published §oauth-agent-identity-presence-gap]
- Three stacked failures: tokens outlive geography (time), controls geolocate infrastructure rather than the human (place), and regulated data becomes visible at the rendering surface, not only the API call (delivery). [^src:articles-published §oauth-agent-identity-presence-gap]
- Five fixes: make presence a claim rather than an assumption, gate the human touchpoints, shorten delegation for covered scopes, reclassify traffic by human impact of the data, and log the full delegation chain. [^src:articles-published §oauth-agent-identity-presence-gap]
- The compliance question is whether organizations can prove where the human behind a delegation was when the data was accessed and rendered — in banking, healthcare, and enterprise agent deployments alike. [^src:articles-published §oauth-agent-identity-presence-gap]