Study guide

3.5 Organizational Controls: Incident Management & Evidence (A.5.24–A.5.28)

PECB ISO/IEC 27001 Lead Implementer Study Guide Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: ISMS Fundamentals & Regulatory Context

1.1 ISO/IEC 27000 Standards Family & Information Security Principles 1.2 Context of the Organization & Interested Parties (Clauses 4.1 & 4.2) 1.3 Determining ISMS Scope & Boundaries (Clause 4.3) 1.4 Leadership, Commitment & Security Policy (Clauses 5.1, 5.2, 5.3)

2 Chapter 2: Planning the ISMS, Risk Management & Support

2.1 Gap Analysis & Implementation Project Initiation 2.2 Information Security Risk Assessment Framework (Clause 6.1.2 & ISO 27005) 2.3 Risk Evaluation & Risk Treatment Methodology 2.4 Statement of Applicability (SoA) & Control Selection (Clause 6.1.3) 2.5 Information Security Objectives & Planning (Clauses 6.2 & 7.1) 2.6 Support Processes: Competence, Communication & Documented Information (Clauses 7.2–7.6)

3 Chapter 3: Implementing Annex A Organizational & People Controls

3.1 Organizational Controls: Governance, Roles & Threat Intelligence (A.5.1–A.5.8) 3.2 Organizational Controls: Asset Management & Information Classification (A.5.9–A.5.14) 3.3 Organizational Controls: Access Control & Identity Management (A.5.15–A.5.18) 3.4 Organizational Controls: Supplier Relationships & Cloud Security (A.5.19–A.5.23) 3.5 Organizational Controls: Incident Management & Evidence (A.5.24–A.5.28) 3.6 Organizational Controls: Continuity, Legal & Compliance (A.5.29–A.5.37) 3.7 People Controls: Screening, Awareness & Remote Working (A.6.1–A.6.8)

4 Chapter 4: Implementing Annex A Physical & Technological Controls

4.1 Physical Controls: Secure Areas & Equipment Protection (A.7.1-A.7.14) 4.2 Technological Controls: Endpoint & User Security (A.8.1-A.8.6) 4.3 Technological Controls: Network Security, Cryptography & Vulnerability Management (A.8.7-A.8.14) 4.4 Technological Controls: Operations, Logging, Web Filtering & Monitoring (A.8.15-A.8.24) 4.5 Technological Controls: Secure Development Lifecycle & Coding (A.8.25-A.8.34)

5 Chapter 5: ISMS Performance Evaluation & Internal Audit

5.1 Monitoring, Measurement, Analysis & Evaluation (Clause 9.1 & ISO 27004) 5.2 ISMS Internal Audit Program & Principles (Clause 9.2 & ISO 19011) 5.3 Conducting the Internal Audit & Gathering Audit Evidence 5.4 Management Review Process & Decisions (Clause 9.3)

6 Chapter 6: Continual Improvement & Certification Audit

6.1 Nonconformity & Corrective Action Management (Clause 10.1) 6.2 Continual Improvement & Maturity Enhancement (Clause 10.2) 6.3 Stage 1 Certification Audit Preparation & Document Review 6.4 Stage 2 Certification Audit, Findings & 3-Year Surveillance Cycle

3.5 Organizational Controls: Incident Management & Evidence (A.5.24–A.5.28)

Key Takeaways Explain This Topic AI

A.5.24 requires planning and preparation for information security incident management, including roles, procedures, and communication paths before incidents occur.

A.5.25 and A.5.26 separate event assessment/decision-making from incident response actions so organizations escalate only confirmed incidents with appropriate severity.

A.5.27 requires learning from incidents and near-misses to strengthen controls, playbooks, and risk assessments after events close.

A.5.28 requires processes to identify, collect, acquire, and preserve information that can serve as evidence, maintaining chain of custody where legal action is possible.

PECB Domain 4 scenarios commonly test whether implementers can establish an incident response team, triage events, and preserve forensic evidence without destroying logs.

Last updated: July 2026

3.5 Organizational Controls: Incident Management & Evidence (A.5.24–A.5.28)

Information security incidents are inevitable; unmanaged incidents become certification failures. Controls A.5.24 through A.5.28 form the incident-management chain in ISO/IEC 27001:2022 Annex A Theme 5 (Organizational controls). PECB Lead Implementer Domain 4 expects candidates to design these controls as an end-to-end process—from preparation and triage through response, lessons learned, and evidence preservation—not as a single “call the SOC” bullet in the SoA.

Control Map (A.5.24 – A.5.28)

Control Title Lead Implementer deliverable

A.5.24 Information security incident management planning and preparation Incident management policy, roles (IRT), contact trees, severity model, playbooks

A.5.25 Assessment and decision on information security events Event triage criteria, classification workflow, decision authority

A.5.26 Response to information security incidents Containment, eradication, recovery procedures; communications

  • A.5.27 Learning from information security incidents Post-incident review process, corrective-action linkage
  • A.5.28 Collection of evidence Forensic readiness, chain-of-custody, legal hold procedures
  • Planning and Preparation (A.5.24)

Control A.5.24 requires the organization to plan and prepare for managing information security incidents by defining, establishing, and communicating processes, roles, and responsibilities. Lead Implementers typically deliver:

Incident management policy approved by Top Management, aligning with legal/regulatory notification duties identified under Clause 4.2 and control A.5.31 .

Incident Response Team (IRT) with named roles: incident manager, technical responders, communications lead, legal/privacy liaison, and business-unit contacts.

Severity / priority model (for example, Sev-1 customer-data breach vs. Sev-4 isolated malware alert) that drives escalation timelines.

Playbooks for common scenarios: ransomware, credential compromise, DDoS, lost devices, insider misuse, and cloud misconfiguration exposure.

Tools and retainers — SIEM/SOAR access, out-of-band communications, breach-counsel and forensics retainers, backup restoration runbooks.

Preparation is tested on the exam: an organization that “responds ad hoc” fails A.5.24 even if it eventually contains an attack.

Event Assessment vs. Incident Response (A.5.25 & A.5.26)

Control A.5.25 addresses information security events —observable occurrences that may or may not indicate a compromise. Personnel must assess events and decide whether they should be classified as information security incidents . Triage criteria include indicators of compromise, affected asset criticality, potential CIA impact, and regulatory exposure.

Control A.5.26 applies once an event is confirmed as an incident. Response activities typically follow: Detect → Triage (A.5.25) → Declare Incident → Contain → Eradicate → Recover → Communicate → Close → Learn (A.5.27)

Response actions include isolating systems, resetting credentials, blocking indicators, engaging suppliers under A.5.20/A.5.23 , notifying interested parties per Clause 7.4 plans, and restoring from known-good backups ( A.8.13 ). Lead Implementers ensure response authority is pre-delegated so responders need not wait for executive email approval during Sev-1 events.

Learning from Incidents (A.5.27)

Control A.5.27 requires knowledge gained from incidents and information security events to strengthen controls. Effective post-incident reviews answer:

What failed (people, process, technology)?

Which Annex A controls or Clause 6.1 risk assumptions were incorrect?

What corrective actions (Clause 10.1 ) and continual-improvement opportunities (Clause 10.2 ) are required?

Do playbooks, detection rules, and training need updates?

Near-misses and false-positive storms also generate learning: noisy alerts that bury real incidents are themselves an ISMS performance problem under Clause 9.1.

Collection of Evidence (A.5.28)

Control A.5.28 requires the organization to establish and implement procedures for the identification, collection, acquisition, and preservation of information that can serve as evidence. Lead Implementers establish forensic readiness :

Preserve volatile data and logs before remediation wipes artifacts.

Maintain chain of custody (who handled evidence, when, and how it was stored).

Use write-blocking and hash verification for media images when legal action is plausible.

Coordinate with legal counsel before imaging systems subject to attorney-client or privacy constraints.

Retain evidence for periods required by law, contracts, and the documented-information retention schedule (Clause 7.5).

A common exam trap: restoring from backup immediately without snapshotting compromised systems can destroy evidence needed for prosecution or insurance claims.

Integration with ISMS Clauses

Incident controls are not isolated Annex A entries. They connect to:

Clause 6.1.2 / 6.1.3 — residual risk assumes detection and response capability.

Clause 7.4 — external breach notifications and customer communications.

Clause 8.1 — operational planning and control of incident processes.

Clause 9.1 / 9.3 — incident metrics and management-review inputs.

Clause 10.1 — nonconformities revealed by incidents.

Practical Implementation Scenario

Scenario: A fintech detects unusual API traffic. The NOC is unsure whether it is a load test or credential stuffing. No severity model exists, and engineers begin patching production logs in place.

Lead Implementer guidance: Apply A.5.25 triage using predefined criteria, declare a Sev-2 incident under A.5.26, preserve logs and API gateway captures under A.5.28 before remediation, execute containment (rate limits, credential resets), notify the privacy lead for potential notification assessment, and schedule an A.5.27 post-incident review that updates WAF rules, monitoring use cases, and the risk register.