Does Belgium Data Protection Act (Wet van 30 juli 2018, Loi du 30 juillet 2018) cover ISO/IEC 38500:2024?

32% of ISO/IEC 38500:2024 you already have

Belgium Data Protection Act (Wet van 30 juli 2018, Loi du 30 juillet 2018) already covers about 32% of ISO/IEC 38500:2024, leaving 41 of 60 controls as genuinely new work.

Already covered 0 Likely covered 19 New work 41

No control in Belgium Data Protection Act (Wet van 30 juli 2018, Loi du 30 juillet 2018) maps directly to one in ISO/IEC 38500:2024. 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 Belgium Data Protection Act (Wet van 30 juli 2018, Loi du 30 juillet 2018) reaches these. This is the list to scope.

5.10.1

Principle

5.10.2

Governance implications for use of IT

5.10.3

Outcomes

5.11.1

Principle

5.11.2

Governance implications for use of IT

5.11.3

Outcomes

5.12

Viability and performance over time

5.12.1

Principle

5.12.2

Governance implications for use of IT

5.12.3

Outcomes

5.2.1

Principle

5.2.2

Governance implications for use of IT

5.2.3

Outcomes

5.3.1

Principle

5.3.2

Governance implications for use of IT

5.3.3

Outcomes

5.4.1

Principle

5.4.2

Governance implications for use of IT

5.4.3

Outcomes

5.5.1

Principle

5.5.3

Outcomes

5.6.1

Principle

5.6.2

Governance implications for use of IT

5.6.3

Outcomes

5.7.1

Principle

5.7.2

Governance implications for use of IT

5.7.3

Outcomes

5.8

Leadership

5.8.1

Principle

5.8.2

Governance implications for use of IT

5.8.3

Outcomes

5.9.1

Principle

5.9.2

Governance implications for use of IT

5.9.3

Outcomes

6.2.2

Evaluate

6.2.3

Direct

6.2.4

Monitor

6.3

Management of IT practice

7.2.2

Direction

7.2.4

Policy

7.2.6

Performance

Show the 19 you already have

4.1

Outcomes of good governance of IT

4.1.2

Effective performance

4.1.3

Responsible stewardship

4.1.4

Ethical behaviour

4.2

Principles, model and framework

5.10

Risk governance

5.11

Social responsibility

5.3

Value generation

5.5

Oversight

5.6

Accountability

5.7

Stakeholder engagement

5.9

Data and decisions

6.2

Governance of IT practice

6.2.1

Engage stakeholders

6.4

Framework for the governance of IT

7.2

Elements of the framework

7.2.3

Capability

7.2.5

Delegation

7.2.7

Accountability

How this is calculated

Already covered means a mapping runs from a control in Belgium Data Protection Act (Wet van 30 juli 2018, Loi du 30 juillet 2018) 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