A.6.8 A.6 · People Controls

A.6.8 — Information security event reporting

Provide a mechanism for personnel to report observed or suspected IS events through appropriate channels in a timely manner.

Also written as A6.8, Annex A 6.8, ISO 27001:2022 A.6.8, ISO27001 A.6.8.

Written by Jett N. · Last reviewed

What ISO 27001 A.6.8 requires

Information security event reporting is one of 8 People Controls in ISO/IEC 27001:2022 Annex A. Provide a mechanism for personnel to report observed or suspected IS events through appropriate channels in a timely manner. People controls are tested against HR records, so the evidence usually lives outside the security team — joiner/mover/leaver files, training completions, and signed acknowledgements need to reconcile with your current headcount.

Audit evidence assessors look for

When preparing your Statement of Applicability (SoA) for A.6.8, gather artefacts such as:

  • IS event reporting procedure with clear contact details
  • Communication channels for reporting (helpdesk number, phishing report button)
  • Training records covering how and when to report events
  • Sample IS event reports logged and triaged

How A.6.8 maps to SOC 2 and NIST CSF

If you run more than one framework, the same evidence usually satisfies all of them. A.6.8 aligns with:

SOC 2: CC2.2 Internal communication, CC2.3 External communication, CC7.3 Security event evaluation

NIST CSF 2.0: DE.AE-06 Event information provided to stakeholders, RS.MA-02 Incident report triage and validation

ISO 27001:2013 mapping

A.6.8 consolidates the following ISO 27001:2013 control(s): A.16.1.2, A.16.1.3. If you are transitioning an existing ISMS, map your prior evidence for these to A.6.8 in your updated SoA.

Map A.6.8 to NIST CSF & SOC 2 →
Crosswalk this control in the Control Mapper & Gap Assessment.
Document the risk →
Record treatment for gaps against A.6.8 in the Risk Register.

Related Annex A controls

A.5.25 Assessment and decision on information security events A.5.10 Acceptable use of information and other associated assets A.6.3 Information security awareness, education and training A.5.5 Contact with authorities A.5.6 Contact with special interest groups A.5.20 Addressing information security within supplier agreements

See all 8 People Controls →

Frequently asked questions

Is ISO 27001 A.6.8 mandatory?

Annex A controls are not mandatory in the abstract. Clause 6.1.3 requires you to compare your risk treatment plan against Annex A and justify, in the Statement of Applicability, any control you exclude. If your risk assessment surfaces a risk that A.6.8 addresses, excluding it needs a documented, risk-based rationale that an auditor will test.

How do auditors test ISO 27001 A.6.8?

In two passes. First design: does a documented control exist, is it owned, and does it address the risk? Then operating effectiveness: the auditor samples records from across the audit period to confirm the control actually ran. A Stage 2 audit will typically pull several samples, so evidence that only exists for the month before the audit is a common finding.

How often should A.6.8 be reviewed?

ISO 27001 sets no fixed interval — it requires review at "planned intervals" and after significant change. Annual review is the norm most certification bodies expect, with an out-of-cycle review triggered by incidents, major system changes, restructures, or new regulatory obligations. Record the review date and outcome either way; an undated control is treated as unreviewed.

What does ISO 27001 A.6.8 map to in SOC 2 and NIST CSF?

A.6.8 aligns with SOC 2 CC2.2, CC2.3, CC7.3 and NIST CSF DE.AE-06, RS.MA-02. Evidence gathered for one framework will usually satisfy the others, which is the basis for a test-once, satisfy-many control library.

What was A.6.8 in ISO 27001:2013?

A.6.8 consolidates 2 control(s) from the 2013 edition: A.16.1.2, A.16.1.3. When transitioning, re-point the existing evidence rather than rebuilding it — the underlying requirement has not changed materially.