ISO 27001:2022 5.28: Collection of evidence

What else in your programme already covers this

This control maps to 68 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.

NIST SP 800-53 Rev 5 · 9 controls

NIST800-AU-10 AU-10 Non-repudiation
NIST800-AU-11 AU-11 Audit Record Retention
NIST800-AU-12 AU-12 Audit Record Generation
NIST800-AU-2 AU-2 Event Logging
NIST800-AU-9 AU-9 Protection of Audit Information
NIST800-IR-4 IR-4 Incident Handling
NIST800-IR-7 IR-7 Incident Response Assistance
NIST800-IR-9 IR-9 Information Spillage Response
NIST800-SR-4 SR-4 Provenance

FedRAMP High · 7 controls

AU-11 Audit Record Retention
AU-12 Audit Record Generation
AU-2 Event Logging
AU-6(3) Correlate Audit Record Repositories
AU-9 Protection of Audit Information
IR-2 Incident Response Training
IR-4 Incident Handling

FedRAMP Moderate · 7 controls

AU-11 Audit Record Retention
AU-12 Audit Record Generation
AU-2 Event Logging
AU-6(3) Correlate Audit Record Repositories
AU-9 Protection of Audit Information
IR-2 Incident Response Training
IR-4 Incident Handling

NIST Cybersecurity Framework 2.0 · 6 controls

NIST-CSF-DE.AE-02 Potentially adverse events are analyzed to better understand associated activities
NIST-CSF-DE.AE-04 The estimated impact and scope of adverse events are understood
NIST-CSF-DE.AE-06 Information on adverse events is provided to authorized staff and tools
NIST-CSF-RS.AN-03 Analysis is performed to establish what has taken place during an incident and the root cause of the incident
NIST-CSF-RS.AN-06 Actions performed during an investigation are recorded, and the records' integrity and provenance are preserved
NIST-CSF-RS.AN-07 Incident data and metadata are collected, and their integrity and provenance are preserved

ISO 27701:2019 · 4 controls

6.13.1 Management of information security incidents and improvements
7.3.8 Providing copy of PII processed
7.3.9 Handling requests
8.3 Obligations to PII principals

SOC 2 · 4 controls

SOC2-CC7.1 CC7.1 Detecting configuration changes and new vulnerabilities
SOC2-CC7.3 CC7.3 Evaluating security events to identify incidents
SOC2-CC7.4 CC7.4 Responding to security incidents
SOC2-P6.3 P6.3 Record of unauthorised disclosures and breaches

Azure Security Benchmark · 3 controls

ASBv3-IR-4 Detection and analysis - investigate an incident
ASBv3-IR-7 Post-incident activity - conduct lesson learned and retain evidence
ASBv3-LT-6 Configure log storage retention

ISO 27002:2022 · 3 controls

5.28 Collection of evidence
5.33 Protection of records
6.8 Information security event reporting

NIS2 Directive · 3 controls

Art.23.4.b Submit an incident notification within 72 hours, with an initial assessment and indicators of compromise
Art.23.4.d Submit a final report within one month, and a progress report where the incident is still running
Art.32 Cooperate with supervision: inspections, security audits, scans and requests for information and evidence

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

CCM-LOG-02 Audit Logs Protection
CCM-LOG-09 Log Protection

EU AI Act · 2 controls

EUAI-Art.12 Record-keeping (logs)
EUAI-Art.73 Reporting of serious incidents

NIST SP 800-161 Rev 1 · 2 controls

161R1-AU-10 Non-repudiation
161R1-AU-14 Session Audit

NIST SP 800-171 Rev 3 · 2 controls

03.03.08 Protection of Audit Information
03.06.02 Incident Monitoring, Reporting, and Response Assistance

ASD Strategies to Mitigate Cyber Security Incidents · 1 control

ASD37-33 Capture network traffic (Limited)

AWS Well-Architected Security Pillar · 1 control

SEC10-BP03 Prepare forensic capabilities

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-3 Audit logging and access monitoring

C5 (Germany) · 1 control

C5-SIM-03 Documentation and reporting of security incidents

CFTC System Safeguards (17 CFR 37, 38, 39, 49) · 1 control

CFTC-SS-20 Production of System Safeguards Books and Records

CMMC 2.0 · 1 control

AU.L2-3.3.8 Audit Protection

DORA · 1 control

DORA-Art.17 ICT-related incident management process

HIPAA Security Rule · 1 control

164.308(a)(6)(ii) Response and Reporting (Required)

NIST SP 800-66 Rev 2 · 1 control

164.308(a)(6)(ii) Response and Reporting (Required)

PCI DSS 4.0 · 1 control

12.10.7 12.10.7 Response procedures for PAN found in unexpected locations

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 ISO 27001:2022 have you already done?

ISO 27001:2022 5.28 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of ISO 27001:2022 your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 79 of 93 ISO 27001:2022 controls already carry evidence.

If you hold NIST SP 800-53 Rev 584.9% covered · 14 gaps If you hold ISO 27001:201383.9% covered · 15 gaps If you hold FedRAMP Moderate80.6% covered · 18 gaps If you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.174.2% covered · 24 gaps If you hold C5 (Germany)69.9% covered · 28 gaps If you hold NIST Cybersecurity Framework 2.063.4% covered · 34 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. 170 were rejected on the NIST SP 800-53 Rev 5 pair alone.

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