GDPR, ISO/IEC 27701:2019 and NIST Privacy Framework 1.0 crosswalk
Each row is one obligation from the GDPR, split by who carries it, controller or processor. Beside it stand the NIST Privacy Framework 1.0 subcategories that this site reads as addressing it, in full or in part, and the ISO/IEC 27701 clauses that a published mapping pairs with its provisions. Every ISO reference comes from that published mapping. Every NIST reference is this site's own reading of the article and of the subcategory, and is marked where a third-party crosswalk hosted by NIST agrees. Switch view to start from an ISO clause or a NIST subcategory instead, or to read the published mappings themselves.
The ISO column uses the numbering of the 2019 edition, because that is the numbering the public mappings use. That edition is withdrawn: ISO replaced it with ISO/IEC 27701:2025 in October 2025. The 2025 edition is restructured, with the management system in clauses 4 to 10 and the controls in Annex A, so a 2019 number cannot be assumed to carry over. The page keeps the published numbers and does not guess new ones; see Method and sources.
- 36 GDPR obligations
- 61 of 100 NIST subcategories linked
- 86 of the 188 ISO/IEC 27701:2019 clauses in the mapping project's list linked
This page was written without the text of ISO/IEC 27701. The ISO column repeats which clauses the Data Protection Mapping Project pairs with each GDPR provision: it shows that a clause is listed, by number and title, and says nothing about how far the clause goes. The NIST column is this site's selection from the Privacy Framework, whose text is public. Neither the standard nor the framework is binding, and the GDPR is: carrying out a clause or a subcategory does not discharge the obligation beside it, and a row without a gap mark means the Privacy Framework addresses the topic, not that it satisfies the article. Obligations are paraphrased; follow the article links to EUR-Lex for the text. Not legal advice.
How to read this
- Pick your role. Fewer rows apply to a processor (13) than to a controller (33). The role filter keeps the rows that apply to both.
- Read the obligation first, then the references. The obligation paraphrases the law, which is binding. The references are voluntary: they are where a framework gives you something to build or something to show.
- Weigh each NIST reference for what it is. Every NIST reference is this site's reading of the GDPR article and of the subcategory text, and is marked "site's reading". "Agrees with NIST-hosted crosswalk" is a cross-check: the GDPR crosswalk hosted by NIST, a third-party work, pairs the same subcategory with a provision of the row, or with the whole article or paragraph that contains it. A reference without that second mark rests on this site's reading alone.
- Treat a gap mark as work the Privacy Framework leaves to you. "NIST: partial match" and "No NIST equivalent" flag duties that the Privacy Framework does not contain or contains only in part, such as time limits, required contract terms or consulting the supervisory authority. The mark says nothing about ISO/IEC 27701.
The crosswalk stores nothing and sends nothing. It keeps its state in the address bar, so a link to a view, a filter or a single row can be copied and shared.
Method and sources
- GDPR. Regulation (EU) 2016/679, article titles from EUR-Lex; the paraphrases were checked against the text of the Regulation. It is in force and has not been amended: on 16 November 2026 EUR-Lex listed three corrigenda and no amending act. Two Commission proposals would amend it, COM(2025) 501 on the record-keeping exemption in Article 30(5) and COM(2025) 837, the Digital Omnibus; EUR-Lex showed both procedures as ongoing on that date, so the rows state the law in force. The page covers Articles 5 to 22, 24 to 39 and 44 to 49, except Article 28(5) to (8) and (10) and Article 32(3), which concern codes of conduct, certification, standard contractual clauses and a processor that acts as a controller. It leaves out scope and definitions (Articles 1 to 4), restrictions under Union or Member State law (Article 23), codes of conduct and certification (Articles 40 to 43), the supervisory authorities, remedies, penalties and specific processing situations among others (Articles 50 to 99), and Member State law. EUR-Lex.
- NIST Privacy Framework Version 1.0. Published 16 January 2020 (NIST CSWP 01162020). Subcategory text is quoted as published, in its American spelling, with the source named. Version 1.1 exists only as an initial public draft (NIST CSWP 40 ipd, 14 April 2025), and NIST had not published a final version on 16 November 2026. NIST describes the draft Core as realigned with Cybersecurity Framework 2.0, in particular in Govern-P and Protect-P, so the NIST column will be re-keyed once the final version is out, using NIST's mapping from 1.0 to 1.1 if it publishes one with it. NIST Privacy Framework.
- ISO/IEC 27701. Cited by clause number and title only, in the numbering of ISO/IEC 27701:2019 and as the Data Protection Mapping Project publishes them, with one typing error in a title corrected. The project shortens the titles of clauses 5 to 8; the views show its labels. The 2019 edition is withdrawn. ISO/IEC 27701:2025, the second edition, was published in October 2025 as a stand-alone management system standard. It is restructured: its table of contents shows the management system in clauses 4 to 10 and the controls in Annex A, so a 2019 number cannot be assumed to carry over. The same table of contents lists the standard's own mapping to the GDPR (Annex D) and a correspondence with the 2019 edition (Annex F); both are part of the paid standard and were not used here. The page will move to the 2025 numbering once a checked source for it is available. The text of the standard is copyright and is not reproduced, apart from clause titles, which come from the Data Protection Mapping Project; the standard is sold by ISO and by national standards bodies. ISO/IEC 27701:2025 on iso.org.
- Data Protection Mapping Project. An open project, hosted by Microsoft on GitHub, that maps ISO/IEC 27701 to data protection laws; its README says the initial data is based on the existing mapping between ISO/IEC 27701 and the GDPR. Copyright 2020 Data Protection Mapping Project, used under the MIT licence; last changed in July 2022. The ISO column of a row is the union of the clauses the project's GDPR sheet lists for the provisions of that row: it is computed, not chosen. The project's Privacy Framework sheet follows the preliminary draft of the framework, so its rows are matched to Version 1.0 where the subcategory text is identical, and by identifier where NIST reworded the text. Two rows of the sheet have no counterpart in Version 1.0, and three Version 1.0 subcategories (GV.PO-P1, CT.DM-P9, CT.DM-P10) have no row in the sheet. This sheet feeds the views by clause and by subcategory and the published mappings tab; it plays no part in choosing the NIST references of a row. Project on GitHub.
- The NIST-hosted GDPR crosswalk, used as a cross-check. "GDPR Crosswalk by Enterprivacy Consulting Group", contributed by Enterprivacy Consulting Group (R. Jason Cronk) to NIST's Privacy Framework Resource Repository and first posted on 2 July 2020. It is a third-party work hosted by NIST, not written by NIST; NIST hosts contributions without endorsing them, and warns that carrying out the Framework's activities does not mean a source's provisions are met. It maps Privacy Framework 1.0 subcategories to GDPR articles and paragraphs. This page did not take its references from it: once the site's own references were chosen, each was compared with the crosswalk, and the row says where the crosswalk pairs the same subcategory with an article or provision of the row. The file states no licence and is not reproduced. GDPR Crosswalk by Enterprivacy Consulting Group on nist.gov. A second third-party crosswalk in the same repository, "ISO/IEC 27701 Crosswalk by Microsoft", was used only to check the Data Protection Mapping Project's Privacy Framework sheet and is not shown. NIST Privacy Framework crosswalks.
- How the NIST references were chosen. For each row the provisions of the GDPR were read against the text of all 100 subcategories. A subcategory was kept only where achieving its outcome would implement or evidence part of the obligation. Outcomes that are only a precondition, or general governance, were left out unless the row is about them. Of the 114 references, 92 agree with the NIST-hosted GDPR crosswalk; for the other 22 the crosswalk does not pair the subcategory with any provision of the row. Agreement is a cross-check, not a test: a pairing in the crosswalk that did not pass this reading is not shown. The gap marks are this site's reading throughout.
The mapping was drafted and reviewed twice with an AI model on 16 November 2026, each review independent of the drafting and of the other, against the GDPR text, the Privacy Framework Core and the published mappings, and corrected after each. It is a working reference: check a row against the Regulation before relying on it. The text of ISO/IEC 27701 was not available for the drafting or for the reviews. Related tools: the GDPR Readiness Assessment for the activities that evidence each article, the Full DPIA, the Transfer Impact Assessment, the notice and policy generators, and the AI governance crosswalk for the AI Act.