Attacks · Credentials & humans
Every API key, bearer token, and service certificate is a secret that works from anywhere until you notice it is gone. One-shot, request-bound proofs replace that model.
~7 min readRelated: Vault breach
The ambient-credential attacker wants possession itself to be lasting authority: hold a key, cookie, or service account and call from any host, clone, or agent until rotation. The conversion is trivial — copy the secret, become the caller. Blast radius scales with every place the secret was pasted. If you only remember one Attacks framing, remember this: long-lived bearers are the root conversion object.
Ambient credentials are the default estate: keys in env vars, tokens in agents, certificates in meshes, cookies in browsers. Breach and blast radius follow possession. Security programs spend their lives rotating, scanning, and hoping nothing was cloned. The cost is not only theft — it is that the product model requires long-lived bearers to exist at all. Agent clones, CI variables, and mesh certificates are the modern vault — same possession model, wider blast radius.
ENI6MA replaces possession-as-authority with per-request envelopes. Authority expires when the request ends. There is no long-lived bearer that survives outside one authorized call — so vault dumps, clones, and keylogs lose the conversion path that makes ambient estates expensive. Family pages for vault, phish, and keylog are specializations of this same denial. Migration language for buyers is replace ambient keys with gated per-call proofs, then prove replay dies.
Read the dual plates as ambient success versus mechanism denial for ambient credentials: the surface plate shows why classical estates pay; the denial plate shows which ENI6MA check family stops the conversion without dumping an NDA attack-to-stage matrix. Claims below stay model-scoped.
Bearer lives outside the request
How to read: long-lived bearers left; possess-once call-many ambient win. Takeaway: authority survives the call.
Ambient success is possess-once, call-many — authority that outlives the request.
Authority dies with the request
How to read: ambient myths fail; per-request proof and burn succeed. Takeaway: no long-lived bearer on the channel.
Per-request proofs and burn leave nothing ambient to copy into the next call.
Every API key, bearer token, and service certificate is a secret that works from anywhere until you notice it is gone.ValidatedAmbient credentials authorize by possession alone; ENI6MA replaces that model with one-shot, request-bound proofs.
Authority expires at the end of each request.ShippingThe envelope binds method, endpoint_id, request hash, policy hash, tau, and nonce (one message, one use).Holds under the reference architecture
Replace ambient API keys with gated proofs.
No reusable tool secret to clone.
No transferable secret tray on the channel.
This essay critiques the systemic problems not addressed by contemporary passwordless trends (passkeys, FIDO tokens, and mobile MFA apps). While hardware-bound credentials reduce phishing and stuffing for interactive users, the author argues they bind users to specific devices and vendor escrow or sync services, ceding sovereignty over storage and recovery.
Written for challengers who worry that watching multiple successful logins reveals the password and private map, or that random guessing eventually hits both, this essay explains why those paths do not work for the ENI6MA rotating-ring method (not mathematically, statistically, computationally, or physically).
This accessible paper explains how the ENI6MA / Rosario–Wang Proof uses cognitive methods to protect the witness (the hidden information that proves identity or knowledge) without exposing it during authentication. Minds (human or artificial) perceive patterns, map symbols to private meanings, and make fast membership decisions; ENI6MA builds an interactive ceremony around those abilities.
Ambient-credentials problem statements contrast possession-as-authority with per-request, burned envelopes.