NIST Cybersecurity Framework 2.0 NIST-CSF-RS.AN-06: Actions performed during an investigation are recorded, and the records' integrity and provenance are preserved

What else in your programme already covers this

This control maps to 40 controls across 26 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 · 5 controls

NIST800-AU-12 AU-12 Audit Record Generation
NIST800-AU-2 AU-2 Event Logging
NIST800-AU-6 AU-6 Audit Record Review, Analysis, and Reporting
NIST800-IR-4 IR-4 Incident Handling
NIST800-IR-5 IR-5 Incident Monitoring

SOC 2 · 3 controls

SOC2-CC7.4 CC7.4 Responding to security incidents
SOC2-CC7.5 CC7.5 Recovering from security incidents
SOC2-P6.3 P6.3 Record of unauthorised disclosures and breaches

AWS Well-Architected Security Pillar · 2 controls

SEC04-BP01 Configure service and application logging
SEC10-BP03 Prepare forensic capabilities

Australian Information Security Manual · 2 controls

ISM-0138 Maintaining the integrity of evidence
ISM-1803 Incident register entry contents

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

CCM-LOG-08 Log Records
CCM-SEF-03 Incident Response Plans

FedRAMP High · 2 controls

AU-12 Audit Record Generation
IR-5 Incident Monitoring

FedRAMP Moderate · 2 controls

AU-12 Audit Record Generation
IR-5 Incident Monitoring

HIPAA Security Rule · 2 controls

164.308(a)(6)(ii) Response and Reporting (Required)
164.316(b)(1) Documentation (Standard)

NIS2 Directive · 2 controls

Art.23.4.c Provide an intermediate report on status when the CSIRT or competent authority requests one
Art.23.4.d Submit a final report within one month, and a progress report where the incident is still running

NIST SP 800-66 Rev 2 · 2 controls

164.308(a)(6)(ii) Response and Reporting (Required)
164.316(b)(1) Documentation (Standard)

Australia Consumer Data Right - Banking (CDR) · 1 control

AUCDR-IS-STEP5 Step 5 - Manage and report security incidents

Australia My Health Records Act 2012 · 1 control

MYHR-SEC-6 Emergency access controls

Azure Security Benchmark · 1 control

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

C5 (Germany) · 1 control

C5-SIM-03 Documentation and reporting of security incidents

CIS Controls v8 · 1 control

CIS-17.4 Establish and Maintain an Incident Response Process

CMMC 2.0 · 1 control

IR.L2-3.6.2 Incident Reporting

Cyber Security Act 2024 (Australia) · 1 control

AUCSA-RAN-RPT Ransomware and cyber-extortion payment reporting obligation

DORA · 1 control

DORA-Art.17 ICT-related incident management process

GDPR · 1 control

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

ISO/IEC 42001:2023 · 1 control

7.5 Documented information

NIST SP 800-161 Rev 1 · 1 control

161R1-AU-10 Non-repudiation

NIST SP 800-171 Rev 3 · 1 control

03.06.02 Incident Monitoring, Reporting, and Response Assistance

NIST SP 800-61 Rev. 3 · 1 control

RS.AN-06 RS.AN-06 Investigation actions recorded with confidentiality and integrity preserved

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-06 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