cm/controlmapping
Sources
NIST CSF 2.0 · Respond (RS)
RS.AN-03

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

frameworkNIST Cybersecurity Framework 2.0 sectionRespond (RS) topicsForensics frameworks5 2 2 4

Wrong or missing mapping? Report it

Equivalents of RS.AN-03 in other frameworks
FrameworkRequirementTitleLinkSource / reason
ISO 27001A.5.28Collection of evidenceCrosswalkSame topic: Forensics
2 loosely related (not mappings)
A.5.25 Assessment and decision on information security events Loosely related
Only shares CSF RS.AN-03: related, not a mapping
A.5.27 Learning from information security incidents Loosely related
Only shares CSF RS.AN-03: related, not a mapping
CIS v8.1CIS 17.8Conduct Post-Incident ReviewsLoosely relatedNo mapping. Only shares CSF RS.AN-03: related, not a mapping
SOC 2CC7.4Responding to identified security incidentsEditorialSame topic: Forensics (editorial pick)
PCI DSS10.3.2Logs protected from modificationCrosswalkSame topic: Forensics
4 loosely related (not mappings)
6.3.1 Vulnerabilities identified and risk-ranked Loosely related
Only shares CSF RS.AN-03: related, not a mapping
10.2.1 Audit logs enabled and active Loosely related
Only shares CSF RS.AN-03: related, not a mapping
10.2.2 Log entries record who, what, when, where and outcome Loosely related
Only shares CSF RS.AN-03: related, not a mapping
10.4.1 Security event and critical logs reviewed daily Loosely related
Only shares CSF RS.AN-03: related, not a mapping
CMMCAU.L2-3.3.6Reduction & ReportingCrosswalkSame topic: Forensics
1 loosely related (not mappings)
IR.L2-3.6.1 Incident Handling Loosely related
Only shares CSF RS.AN-03: related, not a mapping
800-53AU-7SI-2(7)Audit Record Reduction and Report Generation; Root Cause AnalysisCrosswalkSame topic: Forensics
1 loosely related (not mappings)
IR-4 Incident Handling Loosely related
Only shares CSF RS.AN-03: related, not a mapping
HIPAA§164.308(a)(1)(ii)(D)§164.308(a)(6)§164.308(a)(6)(ii)§164.312(b)Information System Activity Review; Security Incident Procedures…Loosely relatedNo mapping. Only shares CSF RS.AN-03: related, not a mapping
GDPR—No requirementNo mapping in our dataNo mapping in our data (only GDPR's security articles are mapped, editorially).
NIS23.5Incident responseCrosswalkSame topic: Forensics
Essential Eight—No requirementNo mapping in our dataNo mapping in our data (Essential Eight links are editorial only).
DORAArt.13(2)Art.17(2)Learning and evolving; ICT-related incident management processEditorialSame topic: Forensics (editorial pick)
CPS 234—No requirementNo mapping in our dataNo mapping in our data (CPS 234 is principles-based and its links are editorial).
Cyber Essentials—No requirementNo mapping in our dataNo mapping in our data (Cyber Essentials covers five technical controls only).

Crosswalk a published crosswalk (NIST, ENISA, CIS, PCI SSC) makes the link · Editorial ControlMapping's judgement where no crosswalk exists; the reason is shown · Loosely related only shares a CSF 2.0 outcome: worth checking, not a mapping · No mapping in our data nothing mapped in our data; often new work, but check the coverage notes. How links are sourced.