NIST Cybersecurity Framework 2.0 NIST-CSF-RS.AN-08: An incident's magnitude is estimated and validated

What else in your programme already covers this

This control maps to 46 controls across 27 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

ISO 22301:2019 · 4 controls

10.1 Nonconformity and corrective action
10.2 Continual improvement
8.6 Evaluation of business continuity documentation and capabilities
9.3.2 Management review input

NIST SP 800-53 Rev 5 · 4 controls

NIST800-AU-6 AU-6 Audit Record Review, Analysis, and Reporting
NIST800-IR-4 IR-4 Incident Handling
NIST800-PM-12 PM-12 Insider Threat Program
SP800-53-SI System and Information Integrity Family

CMMC 2.0 · 3 controls

AU.L2-3.3.3 Event Review
CM.L2-3.4.4 Security Impact Analysis
IR.L2-3.6.1 Incident Handling

PCI DSS 4.0 · 3 controls

10.4.3 10.4.3 Exceptions and anomalies from log review addressed
10.7.3 10.7.3 Respond promptly to critical security control failures
12.10.6 12.10.6 Plan evolved from lessons learned and industry developments

C5 (Germany) · 2 controls

C5-SIM-02 Processing of security incidents
C5-SIM-05 Evaluation and learning process

CIS Controls v8 · 2 controls

CIS-16.3 Perform Root Cause Analysis on Security Vulnerabilities
CIS-17.8 Conduct Post-Incident Reviews

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 2 controls

CCM-SEF-05 Incident Response Metrics
CCM-SEF-06 Event Triage Processes

FedRAMP High · 2 controls

IR-4 Incident Handling
IR-9 Information Spillage Response (IR-9)

FedRAMP Moderate · 2 controls

IR-4 Incident Handling
IR-9 Information Spillage Response (IR-9)

ISO 27001:2022 · 2 controls

5.27 Learning from information security incidents
8.16 Monitoring activities

ISO 27002:2022 · 2 controls

5.26 Response to information security incidents
5.27 Learning from information security incidents

ISO 27701:2019 · 2 controls

5.8.1 Nonconformity and corrective action
6.13.1 Management of information security incidents and improvements

ISO/IEC 42001:2023 · 2 controls

10.2 Nonconformity and corrective action
9.1 Monitoring, measurement, analysis and evaluation

AWS Well-Architected Security Pillar · 1 control

SEC10-BP08 Establish a framework for learning from incidents

Australian Information Security Manual · 1 control

ISM-1909 Root cause analysis of vulnerabilities

Azure Security Benchmark · 1 control

ASBv3-IR-7 Post-incident activity - conduct lesson learned and retain evidence

CIRCIA (Cyber Incident Reporting for Critical Infrastructure Act) · 1 control

CIRCIA-2241 Cyber Incident Review and Threat Indicator Sharing

DFARS 252.204-7012 - Safeguarding Covered Defense Information · 1 control

DFARS-7012-g Cyber incident damage assessment activities

DORA · 1 control

DORA-Art.13 Learning and evolving

HIPAA Security Rule · 1 control

164.308(a)(6)(i) Security Incident Procedures (Standard)

NIS2 Directive · 1 control

Art.23.4.d Submit a final report within one month, and a progress report where the incident is still running

NIST SP 800-171 Rev 3 · 1 control

03.06.01 Incident Handling

NIST SP 800-218 · 1 control

SP800-218-RV.3.1 Analyze Vulnerabilities to Identify Root Causes

NIST SP 800-61 Rev. 3 · 1 control

RS.AN-08 RS.AN-08 Incident magnitude estimated by searching known and potential targets

NIST SP 800-66 Rev 2 · 1 control

164.308(a)(6)(i) Security Incident Procedures (Standard)

SEC Cybersecurity Disclosure Rule · 1 control

SEC-CYB-01 Material Cybersecurity Incident Determination

SOC 2 · 1 control

SOC2-CC7.5 CC7.5 Recovering from security incidents

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

You are reading one control. How much of NIST Cybersecurity Framework 2.0 have you already done?

NIST Cybersecurity Framework 2.0 NIST-CSF-RS.AN-08 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of NIST Cybersecurity Framework 2.0 your existing evidence covers. Hold ISO 27001:2022 and 73 of 106 NIST Cybersecurity Framework 2.0 controls already carry evidence.

If you hold ISO 27001:202268.9% covered · 33 gaps If you hold NIST SP 800-53 Rev 567.9% covered · 34 gaps If you hold C5 (Germany)67% covered · 35 gaps If you hold FedRAMP Moderate63.2% covered · 39 gaps If you hold ISO 27002:202258.5% covered · 44 gaps If you hold CIS Controls v853.8% covered · 49 gaps

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 174 were rejected on the ISO 27001:2022 pair alone.

See the released pairs, $299 each Browse the graph free