A6.8 Information security event reporting
In any organization, security events are inevitable—but how quickly and effectively you detect and respond to them makes all the difference. ISO 27001 Control A6.8 Information security event reporting focuses on establishing a clear process for reporting information security events to ensure they are assessed, escalated, and resolved in a timely manner.
An “information security event” is any identified occurrence indicating a possible breach of security policies or failure of controls, whether it’s a phishing email, malware alert, lost device, or unauthorized access attempt.
Without proper event reporting, issues may go unnoticed until they escalate into major incidents, causing operational damage, reputational harm, or regulatory penalties.
Implementation Guide #
- Establish an Event Reporting Procedure
Create a formal, documented procedure that defines:
- What qualifies as an information security event
- Who is responsible for reporting and receiving events
- How events should be reported (channels, formats, timeframe)
- How events are tracked, analyzed, and escalated
Ensure this procedure is accessible and known to all employees.
- Define Reporting Channels
Provide easy and secure methods for employees to report security events:
- A dedicated email (e.g., security@company.com)
- Internal reporting portal or ticketing system
- Hotline or phone support
Ensure that employees know where and how to report events quickly without fear of blame.
- Train Staff
Train all employees on:
- How to identify security events (e.g., phishing, data loss, unauthorized access)
- The importance of timely reporting
- The step-by-step reporting process
Conduct refresher training periodically and include reporting practices in onboarding.
- Encourage a Security-First Culture
- Promote a no-blame culture to encourage honest and fast reporting.
- Recognize employees who report incidents promptly.
- Make reporting part of everyday awareness campaigns.
- Integrate with Incident Management
Ensure reported events are logged, analyzed, and categorized properly. If an event turns out to be a true incident, it should seamlessly feed into the incident response process as outlined in controls like A.5.25 to A.5.27.
Compliance with ISO 27001 A.6.8 #
To comply:
- Implement and document a standard process for event reporting.
- Make it easy for users to report suspicious activities.
- Assign responsibilities and maintain logs of reported events.
- Review reports regularly and analyze trends.
How to Pass an Audit #
Documents to Prepare:
- Information Security Event Reporting Procedure
- Logs of reported security events
- Staff awareness/training records
- Evidence of actions taken for past reported events
What the Auditor Will Check:
- Are reporting channels clearly defined and known to staff?
- Are events reported and logged consistently?
- Are response actions appropriate and timely?
- Is event reporting integrated with the broader incident response framework?
Common Mistakes #
- No formal reporting procedure – leading to inconsistent or missed reports.
- Lack of awareness – staff don’t know what or how to report.
- Fear-based culture – employees hide incidents out of fear of punishment.
- Failure to log or escalate reports – resulting in unresolved vulnerabilities.
ISO 27001 Controls and Attribute Values #
| Control | Attribute Value |
| A.6.8 Information Security Event Reporting | Preventive, Detective, Operational |
| Purpose | Preventive, Detective, Operational |
| Applicability | All employees, contractors, third-party users |
| ISO 27001 Domains | Human Resource Security, Incident Management, Monitoring and Review |
The faster an organization learns about a security event, the faster it can act. Clear, accessible, and non-punitive event reporting systems are critical in identifying weaknesses early and preventing full-blown incidents.
Create a simple motto for your team:
“See it. Report it. Secure it.”