63% of NIST Special Publication 800-34 Revision 1, Contingency Planning Guide for Federal Information Systems you already have
Azure Security Benchmark already covers about 63% of NIST Special Publication 800-34 Revision 1, Contingency Planning Guide for Federal Information Systems, leaving
3 of 8 controls as genuinely new work.
Already covered 4
Likely covered 1
New work 3
What is genuinely new work
Nothing in Azure Security Benchmark reaches these. This is the list to scope.
NISTSP34-6Plan Maintenance: Updates, Approval, Distribution, Configuration Control
NISTSP34-7Telecommunications and External Service Resilience, Cloud and Third-Party Contingency
NISTSP34-8Recovery Capability by Impact Level, RTO/RPO, and Integration with NIST RMF
Show the 5 you already have
NISTSP34-1Contingency Planning Policy, Programme, and Plan Coordination
NISTSP34-2Business Impact Analysis (BIA): Critical Resources, Recovery Priorities
NISTSP34-3Preventive Controls and Recovery Strategies: Backup, Alternate Sites, Equipment
NISTSP34-4Information System Contingency Plan (ISCP) Development
NISTSP34-5Plan Testing, Training, and Exercises (TTE)
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