Continuous presence
Authentication is based on continuously proven authorised presence at the protected request boundary.
HCAC / Authentication
Prove presence.
Continuously.
Hardware-Bound Continuous Authentication
An authentication architecture centred on continuously proven authorised presence at the protected request boundary.
Public boundary view · conceptual illustration
Explore the boundary
Architecture status
Complete, structurally closed architecture
01 / Governing boundaryHCAC / Public description
The protected request
is the boundary.
HCAC shifts authentication from user-held secrets and replayable sessions to continuously proven authorised presence at the protected request boundary.
Identity is no longer treated as a login event or transferable artefact.
Passwords, passcodes, OTP-based MFA, cookies, and bearer tokens no longer function as authenticators for protected operations.
Protected operations
User-held passwords, passcodes, and OTP-based MFA no longer function as authenticators for protected operations.
Beyond bearer sessions
Cookies and bearer tokens no longer serve as authenticators in the protected authentication path.
02 / Architectural contextDistinct domains. Defined boundaries.
Related architecture / DCIP
A different boundary: integrity before state change.
HCAC addresses authorised presence at the protected request boundary. DCIP addresses structural admissibility of incoming input before receiver-side state change.
03 / Status & disclosureComplete privately. Disclose selectively.
A public outline.
A controlled discussion.
- Status
- Complete, structurally closed architecture
- Availability
- Controlled acquisition discussion only
Public descriptions establish the domain, governing boundary, and significance. Enabling technical structure remains under controlled disclosure.
Implementation, deployment, adaptation, and post-transfer development belong to the acquiring party.
HCAC / Controlled discussionBegin at
Begin at
the protected request.
For a relevant acquisition discussion, identify the authentication domain, why HCAC may matter, and the authority to consider acquisition.
Discuss HCAC