25 controls
193 frameworks share controls with it
United Kingdom
verified against its source document
Every control below is one this framework asks for. The right hand column counts how
many other frameworks in our corpus carry the same control, which is the difference between
doing this work once and doing it again for the next standard.
There is no implementation kit for this framework yet. The control list and the overlap above are free and complete.
What you already have
Frameworks whose controls overlap this one, most first. If you run any of them, the
count is roughly what you have already evidenced.
Every control
| Code | Control | Also in |
OB-API.1 | Read/Write API Specification | 0 |
OB-API.2 | Open Data API Specification | 33 |
OB-API.3 | Dynamic Client Registration | 0 |
OB-API.4 | MI Reporting Specification | 37 |
OB-CX.1 | Explicit Customer Consent | 0 |
OB-CX.2 | Granular Consent Management | 63 |
OB-CX.3 | Strong Customer Authentication | 50 |
OB-CX.4 | Consent Dashboard | 0 |
OB-CX.5 | Consent Revocation | 0 |
OB-DIR.1 | Open Banking Directory | 50 |
OB-DIR.2 | Participant Onboarding | 0 |
OB-DIR.3 | Software Statement Assertions | 0 |
OB-DIR.4 | Dispute Management | 0 |
OB-OPS.1 | API Availability Requirements | 37 |
OB-OPS.2 | Performance Standards | 114 |
OB-OPS.3 | CMA9 Conformance Monitoring | 0 |
OB-OPS.4 | Incident Management | 77 |
OB-SEC.1 | FAPI Security Profile Compliance | 0 |
OB-SEC.2 | Transport Layer Security | 69 |
OB-SEC.3 | OAuth 2.0 and OpenID Connect | 0 |
OB-SEC.4 | Certificate Management | 85 |
UKOBS-1 | Open Banking Scope and Participant Status | 0 |
UKOBS-2 | FAPI 2.0 + SCA + API Specifications | 0 |
UKOBS-3 | Consent Management and Data Sharing | 0 |
UKOBS-4 | Variable Recurring Payments (VRPs) and Open Finance | 0 |
Tell me when UK Open Banking Standard files something new
One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.
What an auditor will ask you to produce
The artefacts named on the failure modes this framework speaks to.
- Evidence of executive or risk owner approval
- Operational records demonstrating execution
- Independent assurance or review report
- Documented procedure addressing uk-specific exemptions
- Documented procedure addressing lawful bases and conditions
- Documented procedure addressing content moderation information
- Consent capture mechanism design records
- Consent log with timestamp and purpose linkage
- Withdrawal workflow evidence
- Privacy notice version aligned to consent text
How programmes fail on this
Failure modes named by this framework and others. Each opens the full record.
What this page is
A control-level reference for UK Open Banking Standard, drawn from our framework corpus. Control codes and
titles are references to the standard, not reproductions of it. The overlap counts and the
auditor artefacts are our own work and are the part you will not find elsewhere.
Measure this against what you already run ·
All frameworks · Today's edition