logo
language iconarrow
menu icon

ISO/IEC 27001:2022

27001-20 Events and incidents

3 min read · V, IA

All articles

For: V, IA
Source: ISO/IEC 27001:2022(en), English. Table A.1, A.5.24 to A.5.28 and A.6.8

The table separates the information security event from the information security incident. A.5.25 requires events to be assessed and a decision to be made on whether they are to be classified as incidents. A.6.8 concerns the reporting of observed or suspected events. Clause 10 addresses the nonconformity and does not name incidents, see 27001-11.

To the extent the respective control is necessary under 6.1.3:

A.5.24: plan and prepare for managing information security incidents by defining, establishing and communicating the processes, roles and responsibilities of incident management.

A.5.25: assess information security events and decide whether they are to be classified as information security incidents.

A.5.26: respond to information security incidents in accordance with the documented procedures.

A.5.27: use knowledge gained from incidents to strengthen and improve the information security controls.

A.5.28: establish and implement procedures for the identification, collection, acquisition and preservation of evidence related to information security events.

A.6.8: provide a mechanism so that personnel can report observed or suspected information security events through appropriate channels in a timely manner. The people control stands here because it is the reporting of events. The other people controls are in 27001-23.

The table names no time limit in hours, no authority and no evidence format. A.5.26 presupposes documented procedures, to the extent the control is necessary. It does not name the content of the procedures.

Not in this text: a reporting obligation under a particular law, a forensic method, and the equating of event, incident and nonconformity.