SECURITY
Controls designed around explicit trust boundaries.
These statements describe controls implemented in the current HallVPN architecture—not roadmap claims or compliance badges.
01Identity and SaaS access
Passwords use Argon2id. Browser sessions are opaque, server-revocable, and protected by exact-origin and session-bound CSRF validation.
- TOTP MFA with replay-safe counters
- Single-use recovery codes
- Backend RBAC and scoped API keys
- Rate limits fail closed
02Certificates and secrets
An isolated PKI signer owns the EC P-384 certificate authority and issues P-256 device keys. Profile bundles use context-bound AES-256-GCM envelope encryption.
- Per-device certificate identity
- Atomic certificate revocation list publication
- Private keys are never logged and leave the signer only inside a single-use encrypted profile workflow
- Secrets supplied outside source control
03Node trust
Each VPN node has an Ed25519 identity and connects over mutual TLS. Control commands are signed, expire quickly, and carry replay-protected nonces.
- Short-lived one-use enrollment
- One active gateway lease per node
- Least-privilege operational helper
- Fixed executable allowlists
04Data isolation and recovery
Organization scope is enforced in service transactions and forced PostgreSQL row-level security.
- Composite tenant foreign keys
- Tenant-visible audit history with controlled retention
- Encrypted backups with verified restore procedures
- Restore and tenant-isolation smoke tests
HallVPN