Skip to content
GarnetOS

Security

Built for data you are legally required to look after.

GarnetOS holds employee records, passports and right-to-work evidence. That is not ordinary application data, and the architecture reflects it from the database upwards.

What we have not got

No certifications, because we do not have any yet.

GarnetOS is early. Listing a badge we have not earned would be the easiest thing on this page to write and the first thing a serious buyer would check.

What follows is a description of how the system is actually built, written from the code and the infrastructure definitions rather than from an aspiration. If you need to assess it properly, ask us — we would rather walk a technical reviewer through the real thing than send a filled-in questionnaire.

If your procurement requires a formal certification today, we are not yet the right supplier for you, and we would rather say so now.

Separation

Enforced by the database, not the application
Every table holding company data has PostgreSQL row-level security switched on and forced — including for the table owner. A query that forgot its filter returns nothing rather than somebody else’s employees. Seventy-two tables are covered, and a build fails if a new one is added without a policy.
Three separate database roles
The credential the application uses on a request cannot bypass those policies. A separate owner role runs migrations, and a third is used only for platform administration.
Isolation is tested, not assumed
Tenant isolation tests run on every build: a second company is created and asked for the first company’s records by id, and has to be refused.

Documents

Never publicly addressable
Files live in private storage with all public access blocked at the bucket. There is no URL that serves a document without authorisation, including one somebody guesses.
Access by short-lived signed link
A download is a signed URL issued for that request, to that person, expiring shortly after. Nothing is served from a permanent address.
Scanned before they can be read
Uploads land in a quarantine bucket and are scanned for malware. A file is only moved where people can reach it once it comes back clean, and anything left unscanned expires within a week.
Encrypted with a key we control
At rest under a customer-managed KMS key rather than the provider default, and TLS is required for every request to the bucket.

Accounts

Two-factor sign-in
Time-based codes from any authenticator app, with single-use recovery codes issued once at enrolment. A company can require it of everybody.
Passwords hashed with Argon2
The current recommended algorithm for password storage. Nobody is ever emailed a password — an invited person sets their own.
Permissions enforced server-side
Every endpoint checks the caller’s permissions for itself. Hiding a button in the interface is a courtesy to the reader, never the control.
Separated sign-in tiers
Customer sessions and platform-administration sessions are different audiences on different tokens; one cannot be used in place of the other.

Records

An audit trail that cannot be edited
Audit events are append-only at the database grant level: the application credential holds permission to read and insert, and nothing else. There is no code path that can alter or delete one, because the permission to do so was never granted.
Who, what, when and why
Consequential changes record the person, the previous and new values, the time it was recorded, the date it takes effect, and the reason given.

Infrastructure

Hosted in London
AWS eu-west-2. Employee records and documents stay in the UK; only the certificate for the content delivery edge lives elsewhere, as that service requires.
Managed database with automated backups
Point-in-time recovery over a retention window, with storage encrypted under the same customer-managed key.
Private networking
The database sits in an isolated subnet with no route to the internet in either direction — not even outbound. The application containers run in a private subnet with no public address. Nothing holding customer data is directly reachable.

Reporting something

If you believe you have found a vulnerability, email security@garnetos.com. Tell us what you found and how to reproduce it, and please give us a reasonable period to fix it before publishing. We will acknowledge you unless you would rather we did not.

Bring your technical reviewer.

We would rather answer hard questions about the architecture than send you a questionnaire.

Request a demo