Cross-Framework Mapping

NIST Cybersecurity Framework 2.0vsPSD2 SCA

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

22
Controls Mapped
84
Gaps Found
14%
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 PSD2 SCA 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 | 686 frameworks | 310K+ cross-framework mappings

Control Mappings

Showing 20 of 22 mapped controls across 6 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
PSDTWO-1Strong Customer Authentication (SCA) Core Requirements

GV - Govern(6 mappings)

NIST-CSF-GV.RM-03Cybersecurity risk management activities and outcomes are included in enterprise risk management processes2 targets
PSDTWO-1Strong Customer Authentication (SCA) Core Requirements
PSDTWO-3Common and Secure Communication, API Access for AISPs and PISPs
NIST-CSF-GV.RM-04Strategic direction that describes appropriate risk response options is established and communicated2 targets
PSDTWO-1Strong Customer Authentication (SCA) Core Requirements
PSDTWO-3Common and Secure Communication, API Access for AISPs and PISPs
NIST-CSF-GV.SC-01A cybersecurity supply chain risk management program, strategy, objectives, policies, and processes are established and agreed to by organizational stakeholders2 targets
PSDTWO-1Strong Customer Authentication (SCA) Core Requirements
PSDTWO-3Common and Secure Communication, API Access for AISPs and PISPs

ID - Identify(2 mappings)

NIST-CSF-ID.IM-04Incident response plans and other cybersecurity plans that affect operations are established, communicated, maintained, and improved2 targets
PSDTWO-3Common and Secure Communication, API Access for AISPs and PISPs
PSDTWO-4Fraud Reporting and Incident Management

PR - Protect(6 mappings)

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
PSDTWO-1Strong Customer Authentication (SCA) Core Requirements
NIST-CSF-PR.DS-10The confidentiality, integrity, and availability of data-in-use are protected
PSDTWO-2SCA Exemptions and Risk-Based Authentication
NIST-CSF-PR.IR-03Mechanisms are implemented to achieve resilience requirements in normal and adverse situations
PSDTWO-2SCA Exemptions and Risk-Based Authentication
NIST-CSF-PR.IR-04Adequate resource capacity to ensure availability is maintained
PSDTWO-2SCA Exemptions and Risk-Based Authentication
NIST-CSF-PR.PS-01Configuration management practices are established and applied
PSDTWO-2SCA Exemptions and Risk-Based Authentication
NIST-CSF-PR.PS-06Secure software development practices are integrated, and their performance is monitored throughout the software development life cycle
PSDTWO-1Strong Customer Authentication (SCA) Core Requirements

RC - Recover(4 mappings)

NIST-CSF-RC.RP-01The recovery portion of the incident response plan is executed once initiated from the incident response process3 targets
PSDTWO-2SCA Exemptions and Risk-Based Authentication
PSDTWO-3Common and Secure Communication, API Access for AISPs and PISPs
PSDTWO-4Fraud Reporting and Incident Management
NIST-CSF-RC.RP-06The end of incident recovery is declared based on criteria, and incident-related documentation is completed
PSDTWO-2SCA Exemptions and Risk-Based Authentication

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
PSDTWO-3Common and Secure Communication, API Access for AISPs and PISPs

+2 more mappings

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

Create Free Account →

Free forever, no credit card required

Coverage crosswalk

A NIST Cybersecurity Framework 2.0 to PSD2 SCA crosswalk, built to order

The table above lists candidate mappings. A crosswalk answers the narrower question you are probably here for: which PSD2 SCA 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 PSD2 SCA
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.

PSD2 SCA 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 PSD2 SCA (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 14% 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 PSD2 SCA 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 PSD2 SCA?

NIST Cybersecurity Framework 2.0 has 106 controls across its framework, while PSD2 SCA covers 28 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 PSD2 SCA equivalent.

How many controls map between NIST Cybersecurity Framework 2.0 and PSD2 SCA?

Of 106 total NIST Cybersecurity Framework 2.0 controls, 15 map directly to PSD2 SCA 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 PSD2 SCA?

91 NIST Cybersecurity Framework 2.0 controls have no direct equivalent in PSD2 SCA. 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 PSD2 SCA?

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.

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.