Framework overlap

Does Azure Security Benchmark cover NIST SP 800-66?

You hold Azure Security Benchmark and have been told to do NIST SP 800-66. Here is how much overlaps, control by control.

50% of NIST SP 800-66 you already have

Azure Security Benchmark already covers about 50% of NIST SP 800-66, leaving 4 of 8 controls as genuinely new work.

Already covered 2 Likely covered 2 New work 4

What is genuinely new work

Nothing in Azure Security Benchmark reaches these. This is the list to scope.

NISTSP66-3
Security Incident Procedures, Contingency Plan, and Evaluation
NISTSP66-4
Business Associate Agreements (BAAs) and Third-Party ePHI Governance
NISTSP66-7
Policies, Procedures, Documentation, and Organisational Requirements
NISTSP66-8
Integration with NIST RMF, Cybersecurity Framework, and OCR Enforcement Posture
Show the 4 you already have
NISTSP66-1
Security Management Process: Risk Analysis and Risk Management for ePHI
NISTSP66-6
Technical Safeguards: Access Control, Audit Controls, Integrity, Person Authentication
NISTSP66-2
Workforce Security, Information Access Management, and Awareness Training
NISTSP66-5
Physical Safeguards: Facility Access, Workstation Use and Security, Device and Media Controls

How this is calculated

Already covered means a mapping runs from a control in Azure Security Benchmark 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