Platform access · app-based MFA required
One platform.
Three journeys.
Each space is protected by app-based multi-factor authentication (RFC 6238), cryptographically signed sessions, and a complete audit trail — without unnecessary friction, with high trust by default.
0
framework subcategories
NIST CSF 2.0 · csrc.nist.gov
≥0
Monte Carlo simulations
per risk · public methodology
0s
TOTP window
rotating code · RFC 6238
0h
session
MFA re-challenge · RFC 6238
Access spaces
Choose the space that matches your role. Each journey is protected by app-based MFA.
Security posture
Security by design.
No compromise on usability.
Platform access rests on three implemented primitives — app-based TOTP, HMAC-signed sessions, audit logging — verifiable in source code and continuously logged.
Trust level · HIGH · enforced
01
App-based TOTP
Google Authenticator · 1Password · Authy · Microsoft Authenticator. RFC 6238, ±30 s window.
NIST SP 800-53 r5
IA-2IA-2(1)IA-2(2)IA-2(8)IA-5AC-7
02
Signed sessions
HMAC-SHA256, HttpOnly, SameSite=Strict, 8 h lifetime with MFA freshness enforced.
NIST SP 800-53 r5
AC-12SC-23AU-10SC-12
03
Anti-enumeration
Constant-time responses. No leak of account existence, even under dictionary attack.
NIST SP 800-53 r5
AC-7SI-4AU-2
04
Audit log
Every attempt timestamped. Audit log held in process memory today, export endpoint scheduled.
NIST SP 800-53 r5
AU-2AU-3AU-9AU-12AU-10
RFC 6238 · HMAC-SHA256 · PBKDF2 210,000 · TLS 1.3CyQuant · Sovereign access