Cross-Framework Mapping

NIST Cybersecurity Framework 2.0vsUK Open Banking Standard

See exactly how NIST Cybersecurity Framework 2.0 controls map to UK Open Banking Standard. Pre-computed mappings, identified gaps, and coverage analysis.

17
Controls Mapped
89
Gaps Found
9%
Coverage

Need this as a report you can hand to an assessor? A coverage crosswalk for this pair can be built to order.

According to the TheArtOfService Compliance Knowledge Graph:

NIST Cybersecurity Framework 2.0 maps to UK Open Banking Standard with 9% coverage across 10 directly mapped controls. Analysis of 106 NIST Cybersecurity Framework 2.0 controls identifies 96 compliance gaps, primarily concentrated in GV - Govern.

Source: TheArtOfService Knowledge Graph | 106 controls analysed | 686 frameworks | 310K+ cross-framework mappings

Control Mappings

Showing 17 of 17 mapped controls across 5 domains. Sign up to explore all 310K+ mappings across 686 frameworks.

DE - Detect(1 mappings)

NIST-CSF-DE.AE-08Incidents are declared when adverse events meet the defined incident criteria
OB-OPS.2Performance Standards

ID - Identify(1 mappings)

NIST-CSF-ID.IM-04Incident response plans and other cybersecurity plans that affect operations are established, communicated, maintained, and improved
OB-OPS.4Incident Management

PR - Protect(13 mappings)

NIST-CSF-PR.AA-01Identities and credentials for authorized users, services, and hardware are managed by the organization3 targets
OB-CX.3Strong Customer Authentication
OB-DIR.1Open Banking Directory
OB-SEC.4Certificate Management
NIST-CSF-PR.AA-02Identities are proofed and bound to credentials based on the context of interactions3 targets
OB-CX.3Strong Customer Authentication
OB-DIR.1Open Banking Directory
OB-SEC.4Certificate Management
NIST-CSF-PR.AA-05Access permissions, entitlements, and authorizations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties
OB-OPS.2Performance Standards
NIST-CSF-PR.DS-10The confidentiality, integrity, and availability of data-in-use are protected2 targets
OB-API.4MI Reporting Specification
OB-OPS.1API Availability Requirements
NIST-CSF-PR.IR-03Mechanisms are implemented to achieve resilience requirements in normal and adverse situations2 targets
OB-API.4MI Reporting Specification
OB-OPS.1API Availability Requirements
NIST-CSF-PR.IR-04Adequate resource capacity to ensure availability is maintained2 targets
OB-API.4MI Reporting Specification
OB-OPS.1API Availability Requirements

RC - Recover(1 mappings)

NIST-CSF-RC.RP-01The recovery portion of the incident response plan is executed once initiated from the incident response process
OB-OPS.4Incident Management

RS - Respond(1 mappings)

NIST-CSF-RS.MA-01The incident response plan is executed in coordination with relevant third parties once an incident is declared
OB-OPS.4Incident Management
Coverage crosswalk

A NIST Cybersecurity Framework 2.0 to UK Open Banking Standard crosswalk, built to order

The table above lists candidate mappings. A crosswalk answers the narrower question you are probably here for: which UK Open Banking Standard controls your existing NIST Cybersecurity Framework 2.0 work already satisfies, which are real gaps, and the reasoning behind every claim so you can check it. One pair, $299, one time.

NIST Cybersecurity Framework 2.0 into UK Open Banking Standard
Not published yet

This direction has not been through crosswalk review and sign off, so no coverage figure is published for it. Reporting an unreviewed number would be worse than reporting none. It can be built to order at the same price as a pair that is already on the shelf.

If the two frameworks turn out to have too little in common for a crosswalk to help you, we say so and refund it rather than send a number worth nothing.

UK Open Banking Standard into NIST Cybersecurity Framework 2.0
Not published yet

This direction has not been through crosswalk review and sign off, so no coverage figure is published for it. Reporting an unreviewed number would be worse than reporting none. It can be built to order at the same price as a pair that is already on the shelf.

If the two frameworks turn out to have too little in common for a crosswalk to help you, we say so and refund it rather than send a number worth nothing.

NIST Cybersecurity Framework 2.0 to UK Open Banking Standard (built to order)
$299
per framework pair, one time
  • Every evidenced control, with the reasoning behind it
  • Every gap, with what it requires
  • Its level of review stated plainly, not a bare number

Why this page shows two different percentages. The 9% in the header counts how many NIST Cybersecurity Framework 2.0 controls carry at least one candidate mapping in the graph, before any review. The crosswalk percentage counts something stricter: how many UK Open Banking Standard controls are actually evidenced, after a pass that argued against each mapping and kept only what survived. They answer different questions and they are not meant to agree.

A crosswalk narrows the work. It does not replace an audit, and your assessor may take a different view on individual controls. Mappings between frameworks are judgements, not text printed in either standard, which is why every claim in the report shows its reasoning. Questions go to support@theartofservice.com.

Stop Paying Consultants to Read Spreadsheets

AI-powered compliance intelligence across 686 frameworks, at a fraction of consulting costs.

$0/forever

Free

  • 686 framework browser
  • Cross-framework mappings (310K+)
  • 824 compliance assessments
  • 3 AI queries & searches per day
Get Started Free
Recommended
$149/month

Professional

  • Unlimited AI Compliance Advisory
  • Unlimited full-text search
  • Framework self-assessment
  • PDF, Excel & CSV exports
Start 7-Day Free Trial →

What are the key differences between NIST Cybersecurity Framework 2.0 and UK Open Banking Standard?

NIST Cybersecurity Framework 2.0 has 106 controls across its framework, while UK Open Banking Standard covers 25 controls. Direct mapping analysis identifies 10 overlapping controls (9% coverage). The frameworks diverge most significantly in GV - Govern, where 28 NIST Cybersecurity Framework 2.0 controls have no direct UK Open Banking Standard equivalent.

How many controls map between NIST Cybersecurity Framework 2.0 and UK Open Banking Standard?

Of 106 total NIST Cybersecurity Framework 2.0 controls, 10 map directly to UK Open Banking Standard controls, representing 9% coverage. The remaining 96 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping NIST Cybersecurity Framework 2.0 to UK Open Banking Standard?

96 NIST Cybersecurity Framework 2.0 controls have no direct equivalent in UK Open Banking Standard. The highest concentration of gaps is in GV - Govern with 28 unmapped controls. These gaps represent areas where additional controls, policies, or documentation must be created to achieve compliance with both frameworks.

Which control domains have the most gaps between NIST Cybersecurity Framework 2.0 and UK Open Banking Standard?

The domain with the highest gap count is GV - Govern (28 gaps). Export the full domain-by-domain gap breakdown via the Professional tier to generate a prioritised remediation roadmap.

This platform provides educational compliance tools, not legal, regulatory, or professional compliance advice. Cross-framework mappings are AI-assisted interpretations and do not reproduce or replace official standards. Framework names and trademarks belong to their respective owners. Consult qualified professionals for your specific compliance requirements. See our Terms of Service.