Skip to main content
azothos
← Back to home

Security

Security Policy

Last updated: 13 November 2026

Security posture

Azoth OS is built to OWASP ASVS Level 1 and Level 2 standards. Security is a first-class concern at every layer of the stack.

Infrastructure

  • Transport — HTTPS only on every connection (TLS 1.2 or 1.3, as negotiated with our hosting provider's edge). HSTS with a 2-year max-age, includeSubDomains and preload.
  • Data at rest — the database is encrypted at rest by Supabase (AES-256); provider keys and other secrets are also encrypted by the application (AES-256-GCM); backups are encrypted before they leave the backup job.
  • Database — Row Level Security enforced on every table. Service role used only for server-side writes; client role used for all user-facing queries.
  • Hosting — Deployed on Vercel Edge Network with automatic DDoS mitigation.

Authentication & access

  • Passwords — bcrypt-hashed by Supabase Auth. Minimum 8 characters enforced with strength indicator.
  • 2FA — TOTP (RFC 6238) available for all accounts via authenticator app.
  • API keys — stored as keyed hashes (HMAC-SHA256), never in plaintext; the key is shown once, on creation. Keys created before this scheme remain SHA-256 hashes until they are rotated.
  • Sessions — Supabase-issued JWT with hard expiry after a configurable inactivity window (default 8 hours; SESSION_MAX_AGE_HOURS env override). Refresh tokens rotate on each use.
  • OAuth — Google OAuth 2.0 via Supabase; no password stored for OAuth users.

Application security

  • Security headers — Content-Security-Policy, X-Frame-Options (DENY), X-Content-Type-Options (nosniff), Referrer-Policy, Permissions-Policy enforced via Next.js middleware.
  • CSRF — every state-changing request must come from Azoth's own origin (checked by the middleware); session cookies are SameSite=Lax.
  • Input validation — all user input validated at API boundaries. SQL injection not possible (parameterized queries via Supabase SDK).
  • Webhook signatures — HMAC-SHA256 with timing-safe comparison (Stripe-compatible format).
  • Audit logs — all significant actions (member invite, API key create/delete, settings change, billing event) written to an immutable `audit_logs` table via service role.

RBAC

Fine-grained role-based access control with four roles: Owner, Admin, Member, Analyst (read-only). Roles are enforced at both application and database (RLS) levels.

Vulnerability disclosure

We operate a responsible disclosure program. If you discover a security vulnerability, please email security@azothos.ai with:

  • A clear description of the vulnerability
  • Steps to reproduce
  • Potential impact

We will acknowledge your report within 48 hours and aim to resolve critical issues within 7 days. We do not pursue legal action against researchers who act in good faith.

Compliance

  • GDPR — Article 28 DPA available; data export from the account and through API v1 (Articles 15 and 20); account erasure from the account, at once (Article 17). Records of processing at /legal/ropa.
  • SOC 2 Type II — controls inventory and audit readiness assessment on the roadmap. We will publish an updated status here once a SOC 2 engagement is formally initiated; until then this section makes no claim of a current or in-progress audit.
  • HIPAA — Azoth OS has no HIPAA compliance programme and does not sign Business Associate Agreements: do not send it protected health information.

Contact

Security team: security@azothos.ai
PGP key available on request.

© 2026 Beweird SAS
Mentions légalesPrivacyCookiesTermsSecurityAccessibilityDPA