Does Cambodia Sub-Decree on Personal Data Protection (Sub-Decree No. 134) cover ENISA Data Protection Engineering?

57% of ENISA Data Protection Engineering you already have

Cambodia Sub-Decree on Personal Data Protection (Sub-Decree No. 134) already covers about 57% of ENISA Data Protection Engineering, leaving 12 of 28 controls as genuinely new work.

Already covered 0 Likely covered 16 New work 12

No control in Cambodia Sub-Decree on Personal Data Protection (Sub-Decree No. 134) maps directly to one in ENISA Data Protection Engineering. 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 Cambodia Sub-Decree on Personal Data Protection (Sub-Decree No. 134) reaches these. This is the list to scope.

ENISA-DPE-1.2

Scope of data protection engineering

ENISA-DPE-2.2

Connection with the Data Protection Impact Assessment

ENISA-DPE-2.3

Privacy-Enhancing Technologies (overview and taxonomy)

ENISA-DPE-3.4

Selecting an anonymisation scheme

ENISA-DPE-6.1

Privacy policies

ENISA-DPE-6.10

Exercising the rights to erasure and rectification

ENISA-DPE-6.2

Privacy icons

ENISA-DPE-6.3

Sticky policies

ENISA-DPE-6.4

Privacy preference signals

ENISA-DPE-6.5

Privacy dashboards

ENISA-DPE-6.9

Exercising the right of access

ENISA-DPE-7.1

Defining the most applicable technique

Show the 16 you already have

ENISA-DPE-1.1

Data Protection by Design

ENISA-DPE-2.1

From DPbD to data protection engineering

ENISA-DPE-3.1

Anonymisation

ENISA-DPE-3.2

Pseudonymisation

ENISA-DPE-3.3

Differential privacy

ENISA-DPE-4.1

Homomorphic encryption

ENISA-DPE-4.2

Secure multiparty computation (MPC)

ENISA-DPE-4.3

Trusted execution environments (TEEs)

ENISA-DPE-4.4

Private information retrieval (PIR)

ENISA-DPE-4.5

Synthetic data

ENISA-DPE-5.1

Communication channels (end-to-end encryption, proxy/onion routing)

ENISA-DPE-5.2

Privacy-preserving storage

ENISA-DPE-5.3

Privacy-enhancing access control and authorisation (ABC, ZKP)

ENISA-DPE-6.6

Consent management (gathering and systems)

ENISA-DPE-7.2

Establishing the state of the art

ENISA-DPE-7.3

Demonstrate compliance and provide assurance

How this is calculated

Already covered means a mapping runs from a control in Cambodia Sub-Decree on Personal Data Protection (Sub-Decree No. 134) 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