Security model
Security is the whole product, so the model is documented in the open. The app is one unminified HTML file — you can read every line yourself.
Audit status
NOT YET AUDITED
Offline Vault has not yet undergone an independent third-party security audit. The recovery-key envelope-encryption scheme in particular should be reviewed by a cryptographer before you rely on it for high-value secrets. Treat the current build as pre-audit. This page will be updated with the auditor, date, and report link once an audit is complete.
Cryptographic design
| Symmetric cipher | AES-GCM-256 |
| IV | 96-bit random, per encryption |
| Key derivation | PBKDF2-SHA-256 |
| Iterations | 250,000 (vault creation and backup export) |
| Salt | 128-bit random, per vault / per backup |
| Randomness | crypto.getRandomValues() |
| Key extractability | false (non-exportable CryptoKeys) |
| Recovery key | Envelope: a Master Vault Key wrapped by both the credential key and a one-time recovery-code key |
| Two-factor (TOTP) | RFC 6238, HMAC-SHA-1, computed locally |
| Transport | None — zero network requests after load |
Hardening
- Content-Security-Policy:
default-src 'none'; connect-src 'none'; frame-ancestors 'none'— no external scripts, no network egress, no framing. - Brute-force throttling on unlock: escalating lockout after repeated failures (5s → 30s → 120s → 600s).
- Auto-lock on inactivity and on tab/window hide.
- Clipboard auto-clear and per-field reveal with an auto-hide timer.
What it protects — and what it doesn't
Protects against: a remote breach (there is no server), network interception (nothing is transmitted), a stolen backup file (encrypted, useless without its password), and casual local inspection of storage (ciphertext at rest).
Does not protect against: losing both your master credential and your recovery code (unrecoverable — keep backups); malware or a keylogger on an unlocked device; clearing all browser site data (deletes the vault); or a weak master credential.
Reporting a vulnerability
Please email [SECURITY-EMAIL] with a description, reproduction steps, and impact. Do not open a public issue for a suspected vulnerability. We aim to acknowledge within 3 business days and provide a remediation timeline within 10. Coordinated disclosure is appreciated.