Finance Operating SystemDocs
Security

Security

How we secure your books, the people who can access them, and the disclosure process for vulnerabilities.

Security

We treat security as table stakes, not a feature. This section is a frank summary of what we do and what the trade-offs are; if you need a SOC 2 report, contact security@financeoperatingsystem.com.

Tenant isolation

Every domain table has a tenantId column; every query goes through a Prisma extension that scopes the query to the active tenant; every API route guards on session + membership. We additionally run nightly cross-tenant sampling to detect drift. See Multi-tenancy for the architecture detail.

Authentication

Users sign in via magic link or passkey. There are no passwords. Sessions are JWT-free (server-side, opaque tokens) with a 7-day inactivity expiry and a 30-day absolute expiry. Session revocation is instant.

API keys are random 256-bit secrets, stored hashed with Argon2id. The plaintext is displayed once at creation and never again.

Authorisation

Three roles inside an organisation: owner, admin, accountant, employee. Owners can manage billing; admins can do everything except billing; accountants have full access to books and reports but cannot manage team or billing; employees can submit expenses and time, view their own data only.

API keys add a fine-grained scope layer on top of the role. The effective permission is key.scope ∩ actor.role.

Data at rest

  • Postgres encrypted at the storage layer (AES-256, AWS RDS managed keys).
  • Receipt and document blobs in object storage (S3 / R2) encrypted at rest with bucket-managed keys.
  • Backups encrypted with a separately-managed KMS key, retained 35 days, daily.

Data in transit

TLS 1.3 enforced on every public endpoint. HSTS with 1-year max-age and preload. Internal service-to-service uses mTLS in production.

Secrets

Application secrets in Doppler / AWS Secrets Manager, rotated quarterly for first-party secrets, on-incident for third-party vendor credentials.

Patching

Dependencies are scanned daily by Snyk. Critical CVEs are patched within 24 hours of disclosure; high within 7 days; medium within 30. The CI build fails if any critical-severity advisory is present.

Logging

We log every API request with method, path, status, latency, requestId, actor, tenant. We do not log request or response bodies — those may contain customer data. Logs are retained 90 days hot, then archived to cold storage with restricted access for the legal retention period.

Audit

Every state-changing action is recorded in the per-tenant audit log: who, what, when, before/after diff. Available to all users with the admin or owner role from Settings → Audit log. Audit log retention follows your subscription plan: Starter 6 months, Pro 24 months, Business unlimited.

Sub-pages