Framework overlap

Does NIST SP 800-53 Rev 5 cover ASD Strategies to Mitigate Cyber Security Incidents?

You hold NIST SP 800-53 Rev 5 and have been told to do ASD Strategies to Mitigate Cyber Security Incidents. Here is how much overlaps, control by control.

73% of ASD Strategies to Mitigate Cyber Security Incidents you already have

NIST SP 800-53 Rev 5 already covers about 73% of ASD Strategies to Mitigate Cyber Security Incidents, leaving 10 of 37 controls as genuinely new work.

Already covered 14 Likely covered 13 New work 10

What is genuinely new work

Nothing in NIST SP 800-53 Rev 5 reaches these. This is the list to scope.

ASD37-05
Automated dynamic analysis of email and web content (Excellent)
ASD37-07
Web content filtering (Excellent)
ASD37-08
Deny direct internet connectivity (Excellent)
ASD37-09
OS generic exploit mitigation (Excellent)
ASD37-13
Control removable storage media (Very Good)
ASD37-14
Block spoofed emails (Very Good)
ASD37-21
Disable local administrator accounts (Excellent)
ASD37-24
Non-persistent virtualised sandboxed environment (Very Good)
ASD37-26
Software firewall - outbound (Very Good)
ASD37-30
Endpoint detection and response (Very Good)
Show the 27 you already have
ASD37-04
User application hardening (Essential)
ASD37-10
Server application hardening (Very Good)
ASD37-11
Operating system hardening (Very Good)
ASD37-17
TLS encryption between email servers (Limited)
ASD37-18
Restrict administrative privileges (Essential)
ASD37-20
Multi-factor authentication (Essential)
ASD37-23
Protect authentication credentials (Excellent)
ASD37-29
Host-based IDS/IPS (Very Good)
ASD37-31
Hunt to discover incidents (Very Good)
ASD37-32
Network-based IDS/IPS (Limited)
ASD37-33
Capture network traffic (Limited)
ASD37-34
Regular backups (Essential)
ASD37-35
Business continuity and disaster recovery plans (Very Good)
ASD37-36
System recovery capabilities (Very Good)
ASD37-01
Application control (Essential)
ASD37-02
Patch applications (Essential)
ASD37-03
Configure Microsoft Office macro settings (Essential)
ASD37-06
Email content filtering (Excellent)
ASD37-12
Antivirus software with heuristics (Very Good)
ASD37-15
User education (Limited)
ASD37-16
Antivirus software with signatures (Limited)
ASD37-19
Patch operating systems (Essential)
ASD37-22
Network segmentation (Excellent)
ASD37-25
Software firewall - inbound (Very Good)
ASD37-27
Outbound data loss prevention (Very Good)
ASD37-28
Continuous incident detection and response (Excellent)
ASD37-37
Personnel management (Very Good)

How this is calculated

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