Does ENISA Data Protection Engineering cover EDM Council CDMC?

14% of EDM Council CDMC you already have

ENISA Data Protection Engineering already covers about 14% of EDM Council CDMC, leaving 12 of 14 controls as genuinely new work.

Already covered 0 Likely covered 2 New work 12

No control in ENISA Data Protection Engineering maps directly to one in EDM Council CDMC. Everything counted as covered is covered because both map to the same third standard, which is what a crosswalk is, but it is an inference rather than a lookup.

What is genuinely new work

Nothing in ENISA Data Protection Engineering reaches these. This is the list to scope.

CDMC-KC1

Data Control Compliance

CDMC-KC11

Data Retention, Archiving and Purging

CDMC-KC12

Data Quality Measurement

CDMC-KC13

Cost Metrics

CDMC-KC14

Data Lineage

CDMC-KC2

Ownership Field

CDMC-KC3

Authoritative Data Sources and Provisioning Points

CDMC-KC4

Data Sovereignty and Cross-Border Movement

CDMC-KC5

Cataloguing

CDMC-KC6

Classification

CDMC-KC7

Entitlements and Access for Sensitive Data

CDMC-KC8

Data Consumption Purpose

Show the 2 you already have

CDMC-KC10

Data Protection Impact Assessments

CDMC-KC9

Security Controls

How this is calculated

Already covered means a mapping runs from a control in ENISA Data Protection Engineering to that control. Likely covered means no direct mapping exists but both frameworks map to the same control in a third standard. New work means neither. We keep those separate rather than adding them into one friendlier number, because blending them would present a two-hop inference as a verified fact.

Coverage is not symmetric. Run it the other way and you will get a different number; both are correct.

From 332,959 cross-framework control mappings across 723 frameworks, 531 of them verified against their source documents. It does not tell you that you are compliant: a mapped control means the two standards ask for the same thing, not that you have done it.

Try another pair · Today's edition