How we keep it secure.

A risk register is a list of your weaknesses. This is how we protect yours, written plainly so your security team can check it.

Signing in

Two-step sign-in for everyone
Every account needs an authenticator app, a passkey or a security key as well as its password, and it can't be switched off. Your admins can require passkeys or security keys only, or approved security key models.
Your own single sign-on
Sign in through Microsoft Entra ID, Google Workspace or Okta, with your own identity provider's rules.
Sessions that end
You're signed out after an hour without activity, after 12 hours whatever happens, and when you close the browser. Accepting a risk asks you to confirm it's you again.
Lockouts and limits
Repeated wrong passwords lock the account for a while, and a request limit slows down anyone trying their luck.

Your data

Hosted in the UK
On Microsoft Azure in the UK. Encrypted nightly copies are kept in a second UK region, where they can't be changed or deleted for 30 days.
Encrypted
In transit with TLS, always. Stored files and two-step secrets are encrypted with keys held apart from the database.
Each customer kept apart
Every page checks which organisation you belong to, and records are only ever looked up through it. Automated tests try to reach other customers' records on every change, and the build fails if one ever succeeds.
Files checked for malware
Every upload is scanned before it's kept. If the scanner can't be reached, uploads are refused rather than let through.
Your data, whenever you want it
Your admins can download everything your organisation holds, with its audit trail and files, in one go.

The record

An audit trail that can only grow
Every change is recorded with who made it, when, and the old and new values. The app can't edit or delete that history, and database rules refuse to as well.
Our access is yours to set
Your admins choose how much we can see in your register: nothing, read only, or enough to help manage risks. We never manage your people or settings unless you ask us to run the register for you. Everything we do there is in your audit log.

How we look after it

Tested on every change
Over 1,500 automated tests run before anything reaches the live service, and only code that has run on our test server is released.
Scanned for weaknesses
A security scan after every update, and an in-depth scan every quarter. What they find, and what we did about it, is written down.
Backups we restore
Nightly backups, checked every week by restoring one, and a recovery plan we rehearse every six months.

Found a weakness?

Tell us at security@riskwitness.io. Our policy for reporting it is at security.txt, and we won't take action against research done in good faith.

Security questionnaire to fill in? Send it to support@riskwitness.io and we'll answer it.