Cross-Framework Mapping

GDPRvsISO/IEC 23894:2023

See exactly how GDPR controls map to ISO/IEC 23894:2023. Pre-computed mappings, identified gaps, and coverage analysis.

11
Controls Mapped
29
Gaps Found
20%
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:

GDPR maps to ISO/IEC 23894:2023 with 20% coverage across 8 directly mapped controls. Analysis of 40 GDPR controls identifies 32 compliance gaps, primarily concentrated in Chapter IV - Controller and Processor.

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

Control Mappings

Showing 11 of 11 mapped controls across 3 domains. Sign up to explore all 309K+ mappings across 686 frameworks.

Chapter II - Principles(3 mappings)

GDPR-Art.10Processing of personal data relating to criminal convictions
ISO23894-A.5Privacy and Data Protection in AI
GDPR-Art.11Processing which does not require identification
ISO23894-A.5Privacy and Data Protection in AI
GDPR-Art.9Processing of special categories of personal data
ISO23894-A.5Privacy and Data Protection in AI

Chapter III - Rights of the Data Subject(2 mappings)

GDPR-Art.15Right of access by the data subject
ISO23894-A.5Privacy and Data Protection in AI
GDPR-Art.19Notification obligation regarding rectification, erasure or restriction
ISO23894-A.5Privacy and Data Protection in AI

Chapter IV - Controller and Processor(6 mappings)

GDPR-Art.25Data protection by design and by default
ISO23894-A.5Privacy and Data Protection in AI
GDPR-Art.35Data protection impact assessment4 targets
ISO23894-6.3AI Risk Assessment
ISO23894-6.3.1AI Risk Identification
ISO23894-6.3.3AI Risk Evaluation
ISO23894-A.5Privacy and Data Protection in AI
GDPR-Art.38Position of the data protection officer
ISO23894-A.5Privacy and Data Protection in AI
Coverage crosswalk

A GDPR to ISO/IEC 23894:2023 crosswalk, built to order

The table above lists candidate mappings. A crosswalk answers the narrower question you are probably here for: which ISO/IEC 23894:2023 controls your existing GDPR work already satisfies, which are real gaps, and the reasoning behind every claim so you can check it. One pair, $299, one time.

GDPR into ISO/IEC 23894:2023
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.

ISO/IEC 23894:2023 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 to ISO/IEC 23894:2023 (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 20% in the header counts how many GDPR controls carry at least one candidate mapping in the graph, before any review. The crosswalk percentage counts something stricter: how many ISO/IEC 23894:2023 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 (309K+)
  • 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 GDPR and ISO/IEC 23894:2023?

GDPR has 40 controls across its framework, while ISO/IEC 23894:2023 covers 85 controls. Direct mapping analysis identifies 8 overlapping controls (20% coverage). The frameworks diverge most significantly in Chapter IV - Controller and Processor, where 13 GDPR controls have no direct ISO/IEC 23894:2023 equivalent.

How many controls map between GDPR and ISO/IEC 23894:2023?

Of 40 total GDPR controls, 8 map directly to ISO/IEC 23894:2023 controls, representing 20% coverage. The remaining 32 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping GDPR to ISO/IEC 23894:2023?

32 GDPR controls have no direct equivalent in ISO/IEC 23894:2023. The highest concentration of gaps is in Chapter IV - Controller and Processor with 13 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 GDPR and ISO/IEC 23894:2023?

The domain with the highest gap count is Chapter IV - Controller and Processor (13 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.