Security & trust
Nexus applies clear boundaries between the browser, application services and customer infrastructure.
Authenticator 2FA is recommended for every member and administrator. An unenrolled account may explicitly continue after the short pre-auth step; once 2FA is enabled, every later sign-in requires RFC 6238 TOTP verification or one single-use recovery code and cannot skip the factor.
Unique authenticator seeds use AES-256-GCM encryption with account-bound authenticated data. Accepted TOTP counters prevent replay, recovery codes are stored only as keyed hashes, and layered account plus IP limits bound online guessing.
There is no public registration or local password database. An administrator pre-provisions the exact business email, unknown Google identities fail closed, and the verified Google subject is bound on first approved sign-in.
System administration requires a current server-side session, database role and exact configured email allowlist match. Viewers and managers receive only explicitly assigned platforms; role, assignment and status changes revoke existing sessions. Administrators are strongly advised to activate 2FA.
Public, member and MCP clients never receive infrastructure credentials. Platform configuration stores explicit environment-secret references, and legacy raw values are masked for migration.
Domains, URLs, service endpoints, modules, databases and Redis records are normalized and bounded before persistence.
Only documented application hashes can be inspected or updated; unrelated and queue keys are outside the contract.
A restrictive Content Security Policy, trusted-origin checks, SameSite cookies, frame denial, no-store responses and bounded request bodies reduce browser-side attack paths.
Agent requests verify TLS, disable redirects and environment proxies, pin safe DNS resolution and reject private or reserved destinations unless explicitly approved for a deployment.
Account provisioning, role, platform access, account status, MCP registry and protected Redis changes create bounded server-side audit events without request secrets. Authentication audit and public contact records have datastore-enforced retention ceilings.
Trust through precision
This page describes controls present in the application architecture. Nexus does not claim certifications, audited uptime or customer outcome metrics that have not been independently established.