A.6.8 Information security event reporting
A mechanism is to be provided so personnel can report information security events they notice or suspect, promptly and through the right channels. Purpose (stated in ISO/IEC 27002:2022): supports timely, consistent and effective reporting of events personnel can identify. As an Annex A reference control, it is compared with the controls determined in risk treatment (6.1.3 c) and recorded in the Statement of Applicability as included or excluded, with the justification and implementation status (6.1.3 d); implementation guidance is ISO/IEC 27002:2022 6.8.
Source: ISO/IEC 27001:2022, A.6.8. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open ISO/IEC 27001:2022 in the compliance library.
Clauses 4 to 10 are the management-system requirements: none of them can be excluded when an organisation claims conformity. The 93 Annex A controls are a reference set: one may be excluded with a justification in the Statement of Applicability. Certification bodies assess conformity; the evidence lists here are what auditors commonly ask for, not a list the standard prescribes.
These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- Records of events reported by personnel, with time from observation to report · Document repository
governing documentDocuments that govern the control
- Statement of Applicability entry for control A.6.8, showing inclusion or justified exclusion, implementation status and the risks it treats · Policy repository / GRC workspace
- A documented reporting procedure naming the point of contact and the channels available, such as a portal, hotline or mailbox · Policy repository / GRC workspace
- Awareness material telling personnel and users what to report, how quickly and where · HR system / LMS
- Guidance instructing people not to test suspected vulnerabilities themselves · Policy repository / GRC workspace
First move
Common gaps auditors find
- Staff do not know where or how to report, so events surface late
- The channel is a single person's inbox with no cover
- Users try to verify suspected vulnerabilities themselves
- Human errors and near misses go unreported because reporting is seen as blame
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheet