ISO policies
Your ISO 27001 policy set arrives drafted. A human approves it.
The platform reads the controls you have activated and drafts the missing policy for each one. An analyst reviews and signs before anything reaches the client. Nothing publishes itself.
Gap analysis
Know what exists, what is missing, and what you cannot prove.
Three states, not two. The difference between a policy that does not exist and one that exists but shows no sign of being practised is exactly what an auditor asks about.
Isolation
Tenant isolation is not a promise in code. It is a rule in the database.
Every row carries its client identifier and Postgres enforces Row Level Security in the engine. The application connects as an unprivileged role, so a wrong query returns nothing rather than another tenant's data.
Scanning
Scans scoped to the controls an auditor actually asks about.
HTTPS redirect, certificates, weak protocols, HSTS, CSP, SPF, DMARC, exposed paths. Every check maps to an ISO 27001, NIS2 or SOC 2 control, and each failure becomes a finding carrying that label.
Cases
From alert to audit evidence without leaving the app.
An alert becomes a case in one click, the case keeps the full investigation timeline, and a closed case attaches to the audit report as structured evidence.
NIS2
NIS2 gives you 24 hours, then 72. The clock runs in the platform.
The incident register holds the statutory notification deadlines, flags what has run past them, and keeps the state of every filing.
Post incident report
Every closed case leaves a report behind, not a memory.
Root cause, impact, affected systems, corrective actions, lessons learned. The draft fills itself from the case rather than from a blank form, and exports as a signable document.
White label
Your platform. Your name on it.
Each client gets their own name, colour and logo in the console and on the cover of exported documents. Your own team's console stays yours.