Actions performed during an investigation are recorded, and the records' integrity and provenance are preserved

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

gap from NIST CSF 2.0 → gap to NIST CSF 2.0 →

Wrong or missing mapping? Report it

Equivalents of RS.AN-06 in other frameworks
Framework	Requirement	Title	Link	Source / reason
ISO 27001	A.5.28	Collection of evidence	Crosswalk	Same topic: Forensics
CIS v8.1	—	No requirement	No mapping in our data	No mapping in our data (most CIS links are editorial: CIS's published crosswalk covers 49 of 153 safeguards).
SOC 2	CC7.4	Responding to identified security incidents	Editorial	Same topic: Forensics (editorial pick)
PCI DSS	10.3.2	Logs protected from modification	Crosswalk	Same topic: Forensics 5 loosely related (not mappings) 10.3.1 Read access to logs limited to need Loosely related Only shares CSF RS.AN-06: related, not a mapping 10.3.3 Logs promptly backed up to a central server Loosely related Only shares CSF RS.AN-06: related, not a mapping 10.3.4 File-integrity monitoring on logs Loosely related Only shares CSF RS.AN-06: related, not a mapping 10.5.1 Audit logs retained 12 months, three immediately available Loosely related Only shares CSF RS.AN-06: related, not a mapping 10.6.1 System clocks synchronised Loosely related Only shares CSF RS.AN-06: related, not a mapping
CMMC	AU.L2-3.3.6	Reduction & Reporting	Crosswalk	Same topic: Forensics 2 loosely related (not mappings) IR.L2-3.6.1 Incident Handling Loosely related Only shares CSF RS.AN-06: related, not a mapping IR.L2-3.6.2 Incident Reporting Loosely related Only shares CSF RS.AN-06: related, not a mapping
800-53	AU-7 SI-2(7)	Audit Record Reduction and Report Generation; Root Cause Analysis	Crosswalk	Same topic: Forensics 2 loosely related (not mappings) IR-4 Incident Handling Loosely related Only shares CSF RS.AN-06: related, not a mapping IR-6 Incident Reporting Loosely related Only shares CSF RS.AN-06: 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 related	No mapping. Only shares CSF RS.AN-06: related, not a mapping +3 more loosely related (not mappings) §164.314(a)(2)(i) Business Associate Contracts Loosely related Only shares CSF RS.AN-06: related, not a mapping §164.314(a)(2)(iii) Business associate contracts with subcontractors Loosely related Only shares CSF RS.AN-06: related, not a mapping §164.314(b)(2)(iv) Group Health Plan Implementation Specification Loosely related Only shares CSF RS.AN-06: related, not a mapping
GDPR	—	No requirement	No mapping in our data	No mapping in our data (only GDPR's security articles are mapped, editorially).
NIS2	3.5	Incident response	Crosswalk	Same topic: Forensics 1 loosely related (not mappings) 3.2 Monitoring and logging Loosely related Only shares CSF RS.AN-06: related, not a mapping
Essential Eight	—	No requirement	No mapping in our data	No mapping in our data (Essential Eight links are editorial only).
DORA	Art.13(2)Art.17(2)	Learning and evolving; ICT-related incident management process	Editorial	Same topic: Forensics (editorial pick)
CPS 234	—	No requirement	No mapping in our data	No mapping in our data (CPS 234 is principles-based and its links are editorial).
Cyber Essentials	—	No requirement	No mapping in our data	No 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.