25% of NATO STANAG 4774 (Confidentiality Metadata Labels) and STANAG 4778 (Metadata Binding) you already have
GDPR already covers about 25% of NATO STANAG 4774 (Confidentiality Metadata Labels) and STANAG 4778 (Metadata Binding), leaving
6 of 8 controls as genuinely new work.
Already covered 0
Likely covered 2
New work 6
No control in GDPR
maps directly to one in NATO STANAG 4774 (Confidentiality Metadata Labels) and STANAG 4778 (Metadata Binding). 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 GDPR reaches these. This is the list to scope.
STANAG-3Label Authoring, Originator Identification, and Policy Identifier
STANAG-4Cross-Domain Label Translation and Interoperability Testing
STANAG-5Label Verification on Ingress and Label Preservation Through Processing
STANAG-6Label Handling in Email, Documents, and Storage
STANAG-7Incident Response, User Training, and Label Audit
STANAG-8Label Caveats, Releasability, and Conditions
Show the 2 you already have
STANAG-1STANAG 4774 Confidentiality Label Schema and XML Structure
STANAG-2STANAG 4778 Metadata Binding Mechanism and Cryptographic Binding
How this is calculated
Already covered means a mapping runs from a control in GDPR 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