| Version | Supported |
|---|---|
0.1.x (main) |
✅ Actively supported |
Please DO NOT open a public GitHub Issue for security vulnerabilities.
Report security issues via private email to:
Include in your report:
- A clear description of the vulnerability
- Steps to reproduce
- Affected versions
- Potential impact
| Step | Target |
|---|---|
| Initial acknowledgement | Within 48 hours |
| Severity assessment | Within 5 business days |
| Patch release (Critical/High) | Within 14 days |
| Public disclosure | After patch is released |
We follow Responsible Disclosure.
FaizDB implements the following security measures:
- Password Hashing: Argon2id with random salt (industry standard for 2026)
- JWT Authentication: EdDSA (Ed25519) — asymmetric, immune to timing attacks
- Encryption at Rest: AES-256-GCM via
ring(FIPS 140-2 compliant primitives) - Transport Security: TLS 1.3 via
rustls(no legacy TLS 1.0/1.1) - Memory Safety: Written in Safe Rust — no
unsafecode in core engine - Rate Limiting: Built-in brute-force protection with automatic IP banning
- RBAC: Three-tier role system (Admin, ReadWrite, ReadOnly)
- Audit Logging: JSON-Lines security event log for compliance