Supervise every bank's cyber controls as they change, not once a year.
Probity gives a regulator one current view of how each institution it oversees meets its cyber security controls. It is built for cyber supervision and works alongside the system you already use to collect regulatory returns.
- Your servers, your network. Probity runs on infrastructure you control and installs without an internet connection. Evidence stays with you unless you choose an outside AI provider.
- A person decides. AI review only advises. A named auditor makes every decision, and the record shows who decided and why.
| Control \ Bank | A | B | C | D | E | F |
|---|---|---|---|---|---|---|
| 1.1AInternet access | ||||||
| 2.2Security updates | ||||||
| 4.2Multi-factor auth | ||||||
| 5.1Access control | ||||||
| 6.4Logging | ||||||
| 7.1Incident response |
Most supervisors see a bank's controls months after the fact.
Assessed once a year
A control that fails in March can go unnoticed until the next assessment cycle.
Evidence by email attachment
Screenshots and reports pass between bank, auditor and regulator with no shared record of what was submitted, or when.
No view across the sector
Each assessment arrives on its own, so the same weakness at several banks looks like several separate problems.
One workflow from the bank's evidence to your decision.
Banks, appointed auditors and the regulator work in the same system. Each sees only what their role allows.
- Bank
Submits evidence against a named control
Policies, configuration exports, scan reports, screenshots. Each upload is kept with its history.
- Optional AI review
Gets an early reading
An AI review reads each upload against the control's requirement and drafts a verdict with reasons. It advises. It never records a finding.
- Auditor
Approves or rejects, by name
A named auditor reviews the evidence and decides, giving reasons. Findings carry a severity and an owner.
- Regulator
Sees the sector as it stands
Your view updates when the auditor decides: every institution, every control, with overdue items brought forward.
A record that holds up when a finding is challenged.
Tamper-evident by design
Every submission, decision and account change is written to a record in which each entry is linked to the one before it by a cryptographic hash. A verification run shows whether anything was altered or removed.
A named person behind every finding
Findings come from auditors, not from software. The record shows who decided, when, and why.
Runs on your servers
Probity installs from a single package on a Linux server you control, with no internet connection needed. Evidence stays inside your network unless you turn on AI review with an outside provider.
AI on your terms
AI review is off until you turn it on and choose the provider. It never switches to another provider on its own.
You control access
Your officials approve accounts for banks and auditors, and can disable any account immediately. Changes to operator accounts can require a second approver.
Built to be run by your team
Encrypted daily backups, a health check, restore onto a new server, and upgrades with a rollback step, each with a written guide for your engineers.
- #2041evidence submitted · 6.4 Logging and Monitoringhash 7c1e…a904 · prev 41d2…0b7e
- #2042AI review drafted · needs more evidencehash b83f…12c6 · prev 7c1e…a904
- #2043auditor rejected · finding raised, highhash e09a…5d31 · prev b83f…12c6
- #2044evidence resubmitted · 6.4hash 2f6d…c8e0 · prev e09a…5d31
The standards your banks already report against.
Controls are stored as data, each with its requirement and the evidence it expects. Your own national standard can be added alongside these.
SWIFT CSP
The full Customer Security Controls Framework, mandatory and advisory controls, for banks on the SWIFT network.
OWASP ASVS 5.0
Application security requirements for the systems banks expose to customers and partners.
PCI DSS v4.0
Card-data security requirements, being loaded for institutions that process payments.
In national deployment in East Africa.
A national regulator, its appointed auditors and the banks it supervises work in Probity, installed on servers the regulator controls.
Request a briefing
A working session with the Q3 team, for your supervision and technology leads. We cover:
- the regulator's view and an auditor's workflow, with sample data;
- how Probity installs and runs on your own infrastructure;
- what a pilot with a few of your institutions would involve.
Tell us your organisation, the sector you supervise, and roughly how many institutions.