English
Français
Deutsch
Italiano
РусскийZero-knowledge authentication
- The password never reaches the server.
- A database leak cannot be used for offline brute-force.
Keep your data safe
The host never reads the findings
The password never reaches the server. Data is encrypted in the browser. Confidentiality and integrity hold. Availability is the residual risk — immutable backups close it.
Cryptography
Password never hits the server. Host never reads the data.
Zero-knowledge authentication and zero-access encryption. Access starts as key possession, not a row in a table.
Zero-access encryption
- Encrypted in the browser.
- The server is assumed breached.
- Confidentiality and integrity still hold.
- Availability is the only residual risk for the data.
- Immutable backups of the servers close that gap.
ACLs by cryptography
- By default, ACLs are key possession, not a flag in the app.
- Without the wrapped project key, a leaked record is noise.
Access
Roles, devices, and 2FA on top of the crypto.
Cryptography is the floor. The app still lets you manage roles, score devices, and lock the perimeter.
App ACLs and roles
- You can manage roles and change permissions in the app.
- Crypto remains the default.
- The interface is how you operate it.
Device trust score
- A device-based score from last login, country, IP, known device, and a few other metrics.
- When the score is low, the manager gets a notification.
Global ACLs
- Per-role allow lists: countries, IPs, and time windows.
- Tighten the global app ACL when the engagement needs a smaller box.
Enforce 2FA
- Turn on 2FA and require it.
- TOTP or a hardware key as the second factor.
Hosting
Hardened Alpine by default. Self-host or air-gap if you need to.
Minimal images, low privilege, optional machine segregation. A monitoring container watches the stack.
Hardened Alpine
- Default images are hardened, minimalist, low-privilege Alpine.
- Segregate them on different machines — possible, and advised.
Self-host or air-gap
- Run HoneyDoc on your infrastructure, a private cloud, or air-gapped.
- The security model does not depend on where the ciphertext sits.
Monitoring container
- A monitoring Docker checks for any admin key change, a tampered signed frontend, or a compromised-backend signal.
Hardening
Obfuscated by default. Reviewed like we review a target.
Frontend jail, aggressive CSP, and an offensive boutique that tests its own product.
Obfuscated code
- The frontend is obfuscated by default.
- Source is not sitting in the clear for a casual dump.
Frontend security
- Aggressive CSP.
- A jailed subdomain for report generation.
- A maintained JS framework with no insecure code calls.
Written by an offensive boutique
- We are an offensive security boutique.
- Automated security checks on the codebase, plus manual reviews.