NIST Cybersecurity Framework 2.0
RS - Respond

NIST Cybersecurity Framework 2.0 NIST-CSF-RS.AN-03: Analysis is performed to establish what has taken place during an incident and the root cause of the incident

Analysis is performed to establish what has taken place during an incident and the root cause of the incident

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

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

NIST SP 800-53 Rev 5 · 6 controls

CIS Controls v8 · 3 controls

  • CIS-10.7 Use Behavior-Based Anti-Malware Software
  • CIS-8.11 Conduct Audit Log Reviews
  • CIS-8.5 Collect Detailed Audit Logs

FedRAMP High · 3 controls

  • AU-6 Audit Record Review, Analysis, and Reporting
  • IR-4 Incident Handling
  • IR-9(4) Information Spillage Response | Exposure to Unauthorized Personnel (IR-9(4))

FedRAMP Moderate · 3 controls

  • AU-6 Audit Record Review, Analysis, and Reporting
  • IR-4 Incident Handling
  • IR-9(4) Information Spillage Response | Exposure to Unauthorized Personnel (IR-9(4))

ISO 27001:2022 · 3 controls

  • 5.25 Assessment and decision on information security events
  • 5.26 Response to information security incidents
  • 5.28 Collection of evidence

ISO 27002:2022 · 3 controls

  • 5.25 Assessment and decision on information security events
  • 5.26 Response to information security incidents
  • 5.28 Collection of evidence

SOC 2 · 3 controls

  • SOC2-CC7.2 CC7.2 Monitoring system components for anomalies
  • SOC2-CC7.3 CC7.3 Evaluating security events to identify incidents
  • SOC2-CC7.5 CC7.5 Recovering from security incidents
  • ISM-1609 Consulting system owners before allowing intrusions to continue
  • ISM-1970 Dedicated malware analysis environment

CMMC 2.0 · 2 controls

HIPAA Security Rule · 2 controls

ISO 27701:2019 · 2 controls

  • 6.13 Information security incident management
  • 6.13.1 Management of information security incidents and improvements

NIST SP 800-171 Rev 3 · 2 controls

NIST SP 800-66 Rev 2 · 2 controls

PCI DSS 4.0 · 2 controls

  • 11.5.1.1 11.5.1.1 Service providers detect covert malware channels
  • 12.10.7 12.10.7 Response procedures for PAN found in unexpected locations
  • E8-APP-ML3 Application Control (ML3)
  • ASD37-33 Capture network traffic (Limited)
  • ASBv3-IR-4 Detection and analysis - investigate an incident

C5 (Germany) · 1 control

  • CIRCIA-2242c4 Required Contents of a Covered Cyber Incident Report
  • AUCSA-CIRB-REVIEW Conduct of no-fault post-incident reviews
  • DFARS-7012-f Access to additional information or equipment for forensic analysis
  • DSPF-P24 Information and technology security - incident management
  • Art. 14(4)(c) Final incident report within one month of the notification

GDPR · 1 control

  • GDPR-Art.33 Notification of a personal data breach to the supervisory authority

ISO 22301:2019 · 1 control

  • 10.2 Continual improvement

NIS2 Directive · 1 control

  • RS.AN-3 RS.AN-3: Forensics are performed
  • RS.AN-3 RS.AN-3: Forensics are performed

NIST SP 800-172 · 1 control

  • 3.6.1e Establish Security Operations Center (SOC)
  • RS.AN-03 RS.AN-03 Sequence of events, actors and root causes of the incident established

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.

Other controls in RS - Respond

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-03 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.

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.

Query this from an agent

The graph holds this control, the 62 it maps to, and the evidence behind each claim, over MCP and REST.