Hiyma is in beta. This page lists the controls that exist today, each with the source file a reviewer can read, and the gaps we have not closed yet. As of 2026-10-21.
In Place Today
HTTPS only
TLS certificates are issued and renewed automatically. HSTS is set for one year, so browsers refuse plain HTTP.
Encryption at rest
Disks and backup storage use Google Cloud default encryption with Google-managed keys. We do not hold our own keys yet.
Invite-only accounts
Every account is approved by hand. Each user gets a generated 160-bit access key, shown once and stored only as a SHA-256 hash. Five failed sign-ins lock the account, for up to an hour.
Signed sessions
Sessions are signed, HTTP-only, secure cookies that expire after 8 hours and can be revoked server-side.
Default deny
Every route outside the public pages requires a valid session. Roles are admin, analyst, viewer and agent.
Organisation scoping
Tenant records are filtered by organisation in application code. Coverage is still being extended across routes.
Append-only audit log
Audit rows are hash-chained. A database trigger refuses any edit, and refuses deletion of rows younger than 400 days.
Content Security Policy
Scripts run only from this origin with a per-request nonce.
Secrets handling
Secrets live in Google Secret Manager, never in the repository. Every pull request is scanned for leaked secrets.
Backups and restore drill
Continuous database archiving (at most 5 minutes of data at risk), weekly full and nightly differential backups, two full backups kept (14–21 days), and an automated restore drill every week.
Labelled data
Every data response says whether it is live, cached, stale or missing. The build fails if code fabricates values.
Publicly checkable records
Sealed records roll up into daily hash-chained roots that anyone can re-derive at /verify.
Not Yet in Place
No SOC 2, ISO 27001 or third-party penetration test yet.
Sign-in is username plus access key. SAML/OIDC single sign-on and multi-factor authentication are not built.
Production runs on one server in one Google Cloud zone (us-central1). Backups are stored in the same region.
Encryption at rest uses Google-managed keys; backups are not encrypted with our own keys.
Customers cannot yet pull their own audit trail or stream it to a SIEM.
Accounts are reviewed by hand. Users are not automatically screened against sanctions lists.
FLOOR messages are not end-to-end encrypted; the platform can read them.
Uptime is monitored, but there is no published uptime history or service level.
Audits and Certifications
SOC 2 Type II
No auditor engaged yet. This row changes when one is.
ISO 27001
Not planned before SOC 2.
Third-party penetration test
None commissioned yet.
See Compliance for privacy requests, the audit trail and incident handling.
Report a Vulnerability
Email [email protected] with steps to reproduce. Please give us a reasonable time to fix the issue before disclosing it.