Cross-Framework Mapping

NIST Cybersecurity Framework 2.0vsOpen Banking Security

Name: NIST Cybersecurity Framework 2.0 to Open Banking Security Control Mapping Dataset
Creator: TheArtOfService

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

Controls Mapped

Gaps Found

14%

Coverage

According to the TheArtOfService Compliance Knowledge Graph:

NIST Cybersecurity Framework 2.0 maps to Open Banking Security with 14% coverage across 15 directly mapped controls. Analysis of 106 NIST Cybersecurity Framework 2.0 controls identifies 91 compliance gaps — primarily concentrated in GV - Govern.

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

Control Mappings

Showing 20 of 21 mapped controls across 6 domains. Sign up to explore all 323K+ mappings across 700 frameworks.

DE - Detect(1 mappings)

NIST-CSF-DE.AE-08Incidents are declared when adverse events meet defined criteria

→OPENBANK-2Strong Customer Authentication (SCA), Consent Lifecycle, and Customer UX

GV - Govern(3 mappings)

NIST-CSF-GV.RM-03Cybersecurity risk management activities and outcomes are included in enterprise risk

→OPENBANK-4Third Party Provider (TPP) Onboarding, Directory Integration, Due Diligence

NIST-CSF-GV.RM-04Strategic direction for cybersecurity risk management is established

→OPENBANK-4Third Party Provider (TPP) Onboarding, Directory Integration, Due Diligence

NIST-CSF-GV.SC-01Cybersecurity supply chain risk management program is established

→OPENBANK-4Third Party Provider (TPP) Onboarding, Directory Integration, Due Diligence

ID - Identify(2 mappings)

NIST-CSF-ID.IM-04Incident response plans and other cybersecurity plans are established and maintained2 targets

→OPENBANK-7Logging, Monitoring, Regulatory Reporting, SLA, Availability

→OPENBANK-8Incident Detection, Response, Customer Notification, Post-Incident Review, BCM

PR - Protect(9 mappings)

NIST-CSF-PR.AA-05Access permissions, entitlements, and authorizations are defined and managed

→OPENBANK-2Strong Customer Authentication (SCA), Consent Lifecycle, and Customer UX

NIST-CSF-PR.DS-10The confidentiality, integrity, and availability of data-in-use are protected2 targets

→OPENBANK-4Third Party Provider (TPP) Onboarding, Directory Integration, Due Diligence

→OPENBANK-8Incident Detection, Response, Customer Notification, Post-Incident Review, BCM

NIST-CSF-PR.IR-03Mechanisms are implemented to achieve resilience requirements in normal and adverse situations2 targets

→OPENBANK-4Third Party Provider (TPP) Onboarding, Directory Integration, Due Diligence

→OPENBANK-8Incident Detection, Response, Customer Notification, Post-Incident Review, BCM

NIST-CSF-PR.IR-04Adequate resource capacity to ensure availability is maintained2 targets

→OPENBANK-4Third Party Provider (TPP) Onboarding, Directory Integration, Due Diligence

→OPENBANK-8Incident Detection, Response, Customer Notification, Post-Incident Review, BCM

NIST-CSF-PR.PS-01Configuration management practices are established and applied

→OPENBANK-3Mutual TLS, Token Binding, Request Signing (JWS), Key Management

NIST-CSF-PR.PS-06Secure software development practices are integrated throughout the SDLC

→OPENBANK-3Mutual TLS, Token Binding, Request Signing (JWS), Key Management

RC - Recover(3 mappings)

NIST-CSF-RC.RP-01The recovery portion of the incident response plan is executed2 targets

→OPENBANK-7Logging, Monitoring, Regulatory Reporting, SLA, Availability

→OPENBANK-8Incident Detection, Response, Customer Notification, Post-Incident Review, BCM

NIST-CSF-RC.RP-06End-of-recovery is declared based on criteria and documentation

→OPENBANK-8Incident Detection, Response, Customer Notification, Post-Incident Review, BCM

RS - Respond(2 mappings)

NIST-CSF-RS.MA-01The incident response plan is executed in coordination with relevant third parties2 targets

→OPENBANK-7Logging, Monitoring, Regulatory Reporting, SLA, Availability

→OPENBANK-8Incident Detection, Response, Customer Notification, Post-Incident Review, BCM

+1 more mappings

Plus AI-powered gap analysis, compliance advisory, PDF exports, and cross-mapping for all 700 frameworks.

Create Free Account →

Free forever — no credit card required

Related Comparisons

Other NIST Cybersecurity Framework 2.0 comparisons

Other Open Banking Security comparisons

APRA CPS 234 vs Open Banking Security5 mappings Protective Security Policy Framework (PSPF) Release 2024 vs Open Banking Security5 mappings FFIEC IT Examination Handbook vs Open Banking Security5 mappings Singapore Government Instruction Manual on ICT&SS Management (IM8) vs Open Banking Security5 mappings UK Open Banking Standard vs Open Banking Security5 mappings NIST SP 800-171A Rev 3 - Assessing CUI Security Requirements vs Open Banking Security5 mappings Annex 11 to EU GMP - Computerised Systems vs Open Banking Security5 mappings South Korea ISMS-P vs Open Banking Security5 mappings

Stop Paying Consultants to Read Spreadsheets

AI-powered compliance intelligence across 700 frameworks — at a fraction of consulting costs.

$0/forever

Free

✓ 700 framework browser
✓ Cross-framework mappings (323K+)
✓ 824 compliance assessments
✓ 3 AI queries & searches per day

Get Started Free

Recommended

$49/month

Professional

✓ Unlimited AI Compliance Advisory
✓ Unlimited full-text search
✓ Framework self-assessment
✓ PDF, Excel & CSV exports

Start 7-Day Free Trial →

Popular framework comparisons

NIST CSF vs NIST 800-53 ISO 27001 vs NIST CSF CMMC vs NIST 800-53 FedRAMP vs NIST 800-53 NIST CSF vs SOC 2 HIPAA vs NIST 800-53 ISO 27001 vs SOC 2 ISO 27001 vs ISO 27701

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

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

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

Of 106 total NIST Cybersecurity Framework 2.0 controls, 15 map directly to Open Banking Security controls — representing 14% coverage. The remaining 91 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 Open Banking Security?

91 NIST Cybersecurity Framework 2.0 controls have no direct equivalent in Open Banking Security. The highest concentration of gaps is in GV - Govern with 25 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 Open Banking Security?

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

Related Resources

How to Map Controls Across Frameworks|Multi-Framework Compliance Guide|Compliance Glossary

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.