Framework overlap

Does API 1164 cover ASEAN Data Management Framework?

You hold API 1164 and have been told to do ASEAN Data Management Framework. Here is how much overlaps, control by control.

56% of ASEAN Data Management Framework you already have

API 1164 already covers about 56% of ASEAN Data Management Framework, leaving 12 of 27 controls as genuinely new work.

Already covered 0 Likely covered 15 New work 12

No control in API 1164 maps directly to one in ASEAN Data Management Framework. 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 API 1164 reaches these. This is the list to scope.

ADMF-1.1
Establish data management governance functions
ADMF-1.2
Data management function responsibilities
ADMF-1.3
Business process function responsibilities
ADMF-2.1
Leadership commitment in policy (who)
ADMF-2.2
Define objectives, scope and considerations (what and why)
ADMF-2.3
Establish the data management approach (how)
ADMF-2.4
Embed data management in corporate governance and policy
ADMF-5.2
Apply technical, procedural and physical safeguards
ADMF-5.3
Protect data across the data lifecycle
ADMF-5.6
Reference recognised security and privacy standards
ADMF-6.4
Test data protection control effectiveness
ADMF-6.5
Update policies, procedures and processes
Show the 15 you already have
ADMF-1.4
Risk management function responsibilities
ADMF-1.5
Executive direction and risk appetite
ADMF-3.1
Identify and understand organisational data
ADMF-3.2
Maintain a data inventory
ADMF-3.3
Apply overarching categorisation considerations
ADMF-4.1
Establish a data categorisation matrix
ADMF-4.2
Assess confidentiality, integrity and availability impact
ADMF-4.3
Assess business impact categories
ADMF-4.4
Assign datasets to risk tiers
ADMF-5.1
Implement risk-based protection controls
ADMF-5.4
Build a data protection control matrix
ADMF-5.5
Manage and accept residual risk
ADMF-6.1
Define monitoring and measurement scope
ADMF-6.2
Review controls associated with each category
ADMF-6.3
Review categories assigned to datasets

How this is calculated

Already covered means a mapping runs from a control in API 1164 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