Framework overlap

Does NIST SP 800-172 cover ANSSI Cybersecurity Framework?

You hold NIST SP 800-172 and have been told to do ANSSI Cybersecurity Framework. Here is how much overlaps, control by control.

22% of ANSSI Cybersecurity Framework you already have

NIST SP 800-172 already covers about 22% of ANSSI Cybersecurity Framework, leaving 18 of 23 controls as genuinely new work.

Already covered 0 Likely covered 5 New work 18

No control in NIST SP 800-172 maps directly to one in ANSSI Cybersecurity 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 NIST SP 800-172 reaches these. This is the list to scope.

ANSSI-CRYPTO
Cryptography Recommendations
ANSSI-EIDAS-QTS
eIDAS Qualified Trust Services
ANSSI-HOMOLOG
Security Homologation Decision
ANSSI-HYGIENE-02
User Authentication
ANSSI-HYGIENE-03
Workstation Security
ANSSI-HYGIENE-05
Remote Access Security
ANSSI-HYGIENE-06
Administration Workstations
ANSSI-HYGIENE-07
Logging and Monitoring
ANSSI-HYGIENE-08
Backup and Recovery
ANSSI-LPM-OIV
LPM OIV Obligations
ANSSI-NIS2-OSE
NIS2 OSE Obligations (France Transposition)
ANSSI-PASSI
PASSI Qualified Audit Providers
ANSSI-PDIS
PDIS Security Incident Detection Providers
ANSSI-PRIS
PRIS Incident Response Providers
ANSSI-PVID
PVID Identity Verification Providers
ANSSI-RGS
RGS Security General Reference
ANSSI-SECNUMCLOUD
SecNumCloud Qualification
ANSSI-SUPPLY-CHAIN
Supply Chain Security
Show the 5 you already have
ANSSI-EBIOS-RM
EBIOS Risk Manager Method
ANSSI-HYGIENE-01
Information Systems Inventory
ANSSI-HYGIENE-04
Network Segmentation
ANSSI-HYGIENE-09
Incident Response Capability
ANSSI-HYGIENE-10
Awareness and Training

How this is calculated

Already covered means a mapping runs from a control in NIST SP 800-172 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