Cross-Framework Mapping

NIST Cybersecurity Framework 2.0vsGDPR

Name: NIST Cybersecurity Framework 2.0 to GDPR Control Mapping Dataset
Creator: TheArtOfService

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

Controls Mapped

Gaps Found

21%

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 GDPR with 21% coverage across 22 directly mapped controls. Analysis of 106 NIST Cybersecurity Framework 2.0 controls identifies 84 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 23 mapped controls across 5 domains. Sign up to explore all 310K+ mappings across 686 frameworks.

GV - Govern(6 mappings)

NIST-CSF-GV.OC-03Legal, regulatory, and contractual requirements regarding cybersecurity - including privacy and civil liberties obligations - are understood and managed2 targets

→GDPR-Art.24Responsibility of the controller

→GDPR-Art.5Principles relating to processing of personal data

NIST-CSF-GV.RM-07Strategic opportunities (i.e., positive risks) are characterized and are included in organizational cybersecurity risk discussions

→GDPR-Art.35Data protection impact assessment

NIST-CSF-GV.SC-05Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant third parties

→GDPR-Art.28Processor

NIST-CSF-GV.SC-06Planning and due diligence are performed to reduce risks before entering into formal supplier or other third-party relationships

→GDPR-Art.28Processor

NIST-CSF-GV.SC-07The risks posed by a supplier, their products and services, and other third parties are understood, recorded, prioritized, assessed, responded to, and monitored over the course of the relationship

→GDPR-Art.28Processor

Govern(1 mappings)

NIST-CSF-GV.OV-03Organizational cybersecurity risk management performance is evaluated and reviewed for adjustments needed

→GDPR-Art.24Responsibility of the controller

ID - Identify(6 mappings)

NIST-CSF-ID.AM-03Representations of the organization's authorized network communication and internal and external network data flows are maintained

→GDPR-Art.30Records of processing activities

NIST-CSF-ID.AM-07Inventories of data and corresponding metadata for designated data types are maintained

→GDPR-Art.30Records of processing activities

NIST-CSF-ID.RA-04Potential impacts and likelihoods of threats exploiting vulnerabilities are identified and recorded

→GDPR-Art.35Data protection impact assessment

NIST-CSF-ID.RA-08Processes for receiving, analyzing, and responding to vulnerability disclosures are established

→GDPR-Art.32Security of processing

NIST-CSF-ID.RA-09The authenticity and integrity of hardware and software are assessed prior to acquisition and use

→GDPR-Art.35Data protection impact assessment

NIST-CSF-ID.RA-10Critical suppliers are assessed prior to acquisition

→GDPR-Art.28Processor

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

→GDPR-Art.25Data protection by design and by default

NIST-CSF-PR.DS-01The confidentiality, integrity, and availability of data-at-rest are protected

→GDPR-Art.32Security of processing

NIST-CSF-PR.DS-02The confidentiality, integrity, and availability of data-in-transit are protected

→GDPR-Art.32Security of processing

NIST-CSF-PR.DS-11Backups of data are created, protected, maintained, and tested

→GDPR-Art.32Security of processing

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

→GDPR-Art.32Security of processing

NIST-CSF-PR.PS-06Secure software development practices are integrated, and their performance is monitored throughout the software development life cycle

→GDPR-Art.25Data protection by design and by default

RS - Respond(1 mappings)

NIST-CSF-RS.AN-03Analysis is performed to establish what has taken place during an incident and the root cause of the incident

→GDPR-Art.33Notification of a personal data breach to the supervisory authority

+3 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 GDPR crosswalk, built to order

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

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.

GDPR into NIST Cybersecurity Framework 2.0

Not published yet

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 GDPR (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 21% 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 GDPR 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.

Related Comparisons

Other NIST Cybersecurity Framework 2.0 comparisons

Other GDPR comparisons

ISO 27701:2019 vs GDPR36 mappings APPI vs GDPR30 mappings NIST SP 800-53 Rev 5 vs GDPR30 mappings Federal Decree-Law No. 45 of 2021 on the Protection of Personal Data (UAE PDPL) vs GDPR30 mappings AICPA Privacy Management Framework (PMF) vs GDPR30 mappings APEC Cross-Border Privacy Rules (CBPR) System vs GDPR28 mappings SOC 2 vs GDPR27 mappings Australia My Health Records Act 2012 vs GDPR26 mappings

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 →

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 GDPR?

NIST Cybersecurity Framework 2.0 has 106 controls across its framework, while GDPR covers 40 controls. Direct mapping analysis identifies 22 overlapping controls (21% coverage). The frameworks diverge most significantly in GV - Govern, where 23 NIST Cybersecurity Framework 2.0 controls have no direct GDPR equivalent.

How many controls map between NIST Cybersecurity Framework 2.0 and GDPR?

Of 106 total NIST Cybersecurity Framework 2.0 controls, 22 map directly to GDPR controls, representing 21% coverage. The remaining 84 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 GDPR?

84 NIST Cybersecurity Framework 2.0 controls have no direct equivalent in GDPR. The highest concentration of gaps is in GV - Govern with 23 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 GDPR?

The domain with the highest gap count is GV - Govern (23 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.