Security pack

Application security

Version 1.0, November 2026 · The whole pack · PDF

How it is built

  • A small, known stack: Python (FastAPI) on the server, PostgreSQL, an S3-compatible store, and a React front end. Standard, well-reviewed libraries for everything security-sensitive: Argon2id for passwords, AES (Fernet) for secrets, HMAC-SHA256 for signatures. No cryptography of our own.
  • Security in the design. The architecture and its threat model are written down, and the application is assessed against the OWASP Application Security Verification Standard (ASVS) 4.0.3, level 2: see the self-assessment, requirement by requirement, with what is met, what is partial and what is planned.
  • Company isolation in one place. The check of session, company, site and role happens in one layer for the whole application, not route by route, so a new page cannot forget it.

How each release is tested

Every change goes through the same pipeline before it can reach the server:

  1. The whole test suite (several hundred tests, many repeated for every page and role), including the isolation tests: signed in as one company, every page and API call is asked for with another company's names and ids, and must return nothing.
  2. Dependency scanning: Python packages against known vulnerabilities (pip-audit); the container image against known vulnerabilities (Trivy).
  3. The image is built, tested again, scanned, and published, pinned by its commit.

The server updates itself only to images its own pipeline built, tested and scanned, and can roll back to the one before.

In the browser

  • Content Security Policy: scripts, styles, images and connections from the app itself only; no inline scripts.
  • Frames refused (frame-ancestors 'none'), no content-type sniffing, a strict referrer policy, a restrictive permissions policy, cross-origin opener isolation, and HSTS.
  • Every request that changes something must carry a header only the app sends, on top of SameSite=Strict cookies, so another site cannot make one for you (cross-site request forgery).
  • Everything shown is escaped by React; there is no HTML from users.

Input, files and the API

  • Every request body is validated against a typed schema; database queries are parameterised (SQLAlchemy); there is no deserialisation of untrusted objects.
  • Uploads are checked by content type, size and (for archives) contents; kept outside the web root; drawings deleted within 2 hours. Downloads are by id, never by a path from the request. Requests above 110 MB are refused.
  • No server-side fetching of addresses users give, other than by the research tools Claude runs at your provider.
  • The API's own documentation pages are not published on the hosted service.

Plugins

Plugins add registers and tools to a site, from a reviewed marketplace.

  • A plugin's functions run as WebAssembly in a sandbox: no files, no network, and limits on memory, processing and time.
  • Each runs inside one site, with only the permissions your admin consented to when installing it, and only if signed with the platform's key after review.
  • Installs, updates and removals are in your audit log, and we can suspend a plugin everywhere at once.

Secrets and keys

  • No secrets in the code (the repository is scanned). Platform secrets are held on the server in files readable only by the service (mode 600), on the encrypted disk.
  • Your company's key, and each site's, seal your secrets; they can be rotated, and old secrets are re-sealed.
  • Planned: keys held in a cloud key vault, with the move to the cloud configuration.

Known limits

From the ASVS self-assessment, stated plainly:

  • Containers still run as root inside the virtual machine (they drop capabilities and are not privileged).
  • Logs are kept on the server rather than shipped to a central, separate log store.
  • Container images are not yet signed; production is protected by deploying only its own pipeline's images.
  • No independent penetration test yet: one is planned before the service grows beyond its first customers, then yearly.