Framework overlap

Does Liechtenstein DPA cover NIST SP 800-171A?

You hold Liechtenstein DPA and have been told to do NIST SP 800-171A. Here is how much overlaps, control by control.

72% of NIST SP 800-171A you already have

Liechtenstein DPA already covers about 72% of NIST SP 800-171A, leaving 9 of 32 controls as genuinely new work.

Already covered 9 Likely covered 14 New work 9

What is genuinely new work

Nothing in Liechtenstein DPA reaches these. This is the list to scope.

171A-AC-01
Assess Account Management
171A-AC-03
Assess Information Flow Enforcement
171A-AU-01
Assess Audit Event Logging
171A-CM-03
Assess Least Functionality
171A-CM-04
Assess Software Restrictions
171A-IA-03
Assess Authenticator Management
171A-MA-01
Assess System Maintenance Controls
171A-MA-02
Assess Remote Maintenance
171A-MP-02
Assess Media Transport Protection
Show the 23 you already have
171A-AC-02
Assess Access Enforcement
171A-AC-04
Assess Separation of Duties
171A-AC-06
Assess Remote Access Controls
171A-AC-07
Assess Wireless Access Controls
171A-IR-01
Assess Incident Handling
171A-IR-02
Assess Incident Response Testing
171A-MP-01
Assess Media Protection
171A-SC-02
Assess Cryptographic Protection
171A-SC-03
Assess Communications Protection
171A-AC-05
Assess Least Privilege
171A-AT-01
Assess Security Awareness Training
171A-AT-02
Assess Role-Based Security Training
171A-AU-02
Assess Audit Record Review and Reporting
171A-AU-03
Assess Audit Record Protection
171A-AU-04
Assess Audit Record Retention
171A-CM-01
Assess Baseline Configuration
171A-CM-02
Assess Configuration Change Control
171A-IA-01
Assess Identification and Authentication
171A-IA-02
Assess Multi-Factor Authentication
171A-SC-01
Assess Boundary Protection
171A-SI-01
Assess Flaw Remediation
171A-SI-02
Assess Malicious Code Protection
171A-SI-03
Assess System Monitoring

How this is calculated

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