ISO 27002:2022
Organizational controls – ISO 27002:2022

ISO 27002:2022 5.28: Collection of evidence

Procedures are to be set up and followed for identifying, collecting, acquiring and preserving evidence connected with information security events. Purpose: handle incident evidence consistently and effectively so it can support disciplinary or legal action. Guidance: internal procedures govern evidence intended for disciplinary or legal use and take account of the rules in each relevant jurisdiction so the evidence has the best chance of being accepted. They should explain how to identify, collect, acquire and preserve evidence for different storage media and devices and for devices that are powered on or off. Evidence generally has to be gathered in a way a national court or other disciplinary forum will accept, which means being able to show that records are complete and untouched, that copies of electronic evidence are very likely identical to the originals, and that the systems it came from were working properly when it was recorded. Where possible, personnel and tools should hold certification or other qualification, strengthening the preserved evidence. When digital evidence crosses organizational or jurisdictional lines, the organization must make sure it is entitled to collect it. Other information: whether an event will lead to court action is often unclear at first, so evidence can be lost, deliberately or not, before the seriousness is understood; seek legal or law enforcement advice early; ISO/IEC 27037 covers digital evidence handling and the ISO/IEC 27050 series covers electronic discovery.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

This control maps to 78 controls across 30 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 · 10 controls

  • NIST-CSF-DE.AE-06 Information on adverse events is provided to authorized staff and tools
  • NIST-CSF-DE.CM-01 Networks and network services are monitored to find potentially adverse events
  • NIST-CSF-DE.CM-09 Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events
  • NIST-CSF-PR.PS-04 Log records are generated and made available for continuous monitoring
  • 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
  • NIST-CSF-RS.MI-02 Incidents are eradicated

SOC 2 · 7 controls

  • SOC2-CC2.1 CC2.1 Relevant, quality information to support internal control (COSO principle 13)
  • SOC2-CC4.1 CC4.1 Ongoing and separate evaluations of control (COSO principle 16)
  • 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.2 P6.2 Record of authorised disclosures
  • SOC2-P6.3 P6.3 Record of unauthorised disclosures and breaches

FedRAMP High · 5 controls

  • AU-11 Audit Record Retention
  • AU-9 Protection of Audit Information
  • IR-2 Incident Response Training
  • IR-6 Incident Reporting
  • IR-9(4) Information Spillage Response | Exposure to Unauthorized Personnel (IR-9(4))

FedRAMP Moderate · 5 controls

  • AU-11 Audit Record Retention
  • AU-9 Protection of Audit Information
  • IR-2 Incident Response Training
  • IR-6 Incident Reporting
  • IR-9(4) Information Spillage Response | Exposure to Unauthorized Personnel (IR-9(4))

ISO/IEC 27037:2012 · 5 controls

  • 5.2 5.2 Principles of digital evidence
  • 5.4.1 5.4.1 Overview
  • 5.4.4 5.4.4 Acquisition
  • 6.1 6.1 Chain of custody
  • 7.1.4 7.1.4 Preservation
  • ISM-0043 Cyber security incident response plan contents
  • ISM-0137 Legal advice before allowing intrusions to continue
  • ISM-0138 Maintaining the integrity of evidence
  • 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 27701:2019 · 3 controls

  • 6.13.1 Management of information security incidents and improvements
  • 6.9.4 Logging and monitoring
  • 8.5.4 Notification of PII disclosure requests

ISO/IEC 27042:2015 · 3 controls

  • 11.2 11.2 Mechanisms for demonstration of proficiency
  • 5.2 5.2 Continuity
  • 6.2 6.2 General principles

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

CMMC 2.0 · 2 controls

ISO/IEC 27041:2015 · 2 controls

  • 5.6.3 5.6.3 Uncertainty and risk evaluation
  • 5.8.3 5.8.3 Verification of tools

NIST SP 800-161 Rev 1 · 2 controls

  • ASD37-33 Capture network traffic (Limited)

C5 (Germany) · 1 control

  • C5-SIM-03 Documentation and reporting of security incidents
  • CFTC-SS-20 Production of System Safeguards Books and Records

CIS Controls v8 · 1 control

DORA · 1 control

HIPAA Security Rule · 1 control

ISO 27001:2022 · 1 control

  • 5.28 Collection of evidence

ISO 27018:2019 · 1 control

  • 16.1.7 Collection of evidence

PCI DSS 4.0 · 1 control

  • 12.10.7 12.10.7 Response procedures for PAN found in unexpected locations
  • 0029 0029 Investigate incidents under the Australian Government Investigations Standards
  • PICERL-I2 Evidence Collection

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 Organizational controls – ISO 27002:2022

You are reading one control. How much of ISO 27002:2022 have you already done?

ISO 27002:2022 5.28 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of ISO 27002:2022 your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 79 of 93 ISO 27002:2022 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. 180 were rejected on the NIST SP 800-53 Rev 5 pair alone.

Query this from an agent

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