Ulas
1146588212
- SECURITY.md: add bcrypt v6 reference and mandatory SESSION_SECRET note - CODE_OF_CONDUCT.md: add enforcement contact (GitHub Private Reporting) - BACKLOG.md: add completed features table entries for v0.5.0 through v0.7.0 - docs/SPEC.md: add supported languages table with Italian (v0.5.8) - Remove CLAUDE.md.proposed (tracked, deleted from disk)
52 lines
2.2 KiB
Markdown
52 lines
2.2 KiB
Markdown
# Security Policy
|
|
|
|
## Reporting a Vulnerability
|
|
|
|
If you discover a security vulnerability in Oikos, please report it responsibly. **Do not open a public issue.**
|
|
|
|
Instead, use [GitHub Private Vulnerability Reporting](https://github.com/ulsklyc/oikos/security/advisories/new) to submit your report. This creates a private advisory visible only to you and the maintainers.
|
|
|
|
Include:
|
|
|
|
- Description of the vulnerability
|
|
- Steps to reproduce
|
|
- Potential impact
|
|
- Suggested fix (if you have one)
|
|
|
|
You should receive an acknowledgment within 48 hours. Fixes for confirmed vulnerabilities will be released as soon as possible.
|
|
|
|
## Scope
|
|
|
|
Oikos is designed for self-hosted deployment on a private network behind a reverse proxy with SSL. The security model assumes:
|
|
|
|
- The server is not directly exposed to the public internet without Nginx + TLS
|
|
- The admin controls all user accounts (no public registration)
|
|
- The host machine itself is reasonably secured
|
|
|
|
Vulnerabilities that require physical access to the host or root on the server are generally out of scope.
|
|
|
|
## Security Features
|
|
|
|
- Session-based auth with `httpOnly`, `SameSite=Strict`, `Secure` cookies
|
|
- CSRF protection via Double Submit Cookie on all state-changing requests
|
|
- Passwords hashed with bcrypt v6 (cost factor 12)
|
|
- Login rate limiting (5 attempts/min per IP)
|
|
- API rate limiting (300 requests/min per IP)
|
|
- Content Security Policy via Helmet (`self`-only)
|
|
- Optional SQLCipher AES-256 database encryption
|
|
- No API endpoint accessible without session auth (except login)
|
|
- `SESSION_SECRET` is mandatory - server refuses to start if unset
|
|
|
|
## Authorization Model
|
|
|
|
Oikos uses a flat family authorization model:
|
|
|
|
- **Admin** can create, edit, and delete all user accounts and all shared data.
|
|
- **Member** can read and write all shared data (tasks, shopping lists, meals, calendar events, notes, contacts, budget entries) but cannot manage user accounts.
|
|
|
|
There is no per-user data isolation - all family members see and can edit all data. This is intentional: Oikos is a shared family planner, not a multi-tenant application.
|
|
|
|
## Supported Versions
|
|
|
|
Only the latest version on `main` receives security updates. There are no LTS branches.
|