Part of ISO 27001: Critical success factors, a series on building a management system that reflects how your organisation really runs.
What it is
A security event is anything that might affect information security: an incident, a near miss, a suspicious email someone reported, a supplier outage. Events are how reality tests your assumptions about risk.
In most control-centric frameworks a security event gets handled much like a break-fix IT incident: fix it, restore service, close the ticket. ISO 27001 asks how you are learning from it.
What the standard asks
Incident management sits in Annex A rather than the main clauses, but it's one of the areas where the management system shows most clearly. The relevant controls cover:
- planning and preparing for incidents, with roles and procedures (5.24)
- assessing events and deciding whether they're incidents (5.25)
- responding to incidents (5.26)
- learning from incidents to strengthen controls (5.27)
- collecting and preserving evidence (5.28)
- giving people a way to report events promptly (6.8)
Not every event is a nonconformity; most are inputs to learning about risks and controls. Where an event does reveal a nonconformity, clause 10.2 applies: correct it, find the cause and decide whether action is needed to stop it happening again.
What good looks like
- A low threshold for recording. Near misses and small events are captured, because they're the cheapest lessons you'll get.
- People know who to report to, and reporting is thanked rather than blamed.
- A running narrative for live events: what was known when, what was decided and by whom.
- Every closure asks what you learned. What does this tell us about our risks? Did a control fail, or was it the right control in the first place?
- Links back. Each event is linked to the risks and controls it touches, so the risk register reflects what actually happens.
- Trends reach the forum, not just the major incidents.
Evidence an auditor will ask for
- An event and incident log, including near misses
- Records of assessment, response and closure for each event
- Lessons learned, and the actions or risk updates that followed
- Forum minutes showing events and trends were reviewed
Common failure modes
- Only the big ones. A log with two incidents a year suggests either a very quiet organisation or nobody reporting. In my experience, auditors tend to assume the second.
- Closed without learning. The ticket says resolved; nothing changes in the risk register or the controls.
- Blame suppresses reporting. If reporting a mistake gets someone in trouble, you stop hearing about mistakes.
- Disconnected from risk. Events are recorded in one system and risks in another, and nobody joins them up.
How it connects
Feeds from
- Control operation, staff reports, suppliers and monitoring
Feeds into
- Risk analysis and the risk register
- The management forum
- The risk improvement plan, for corrective actions
Where it sits in the plan
Stage: Do, from day one. Start capturing events on day one, before anything else is in place. Even a simple log gives the first risk assessment real material to work with, and it's the clearest early sign that the ISMS reflects how the organisation actually runs. Event trends then feed Check every cycle.
The plan in the main article shows how this fits with everything else, and the bootstrapping guide covers each stage in detail.
Resources
Tom Whipp is the founder of RiskQuilt. He spent around thirty years in cyber and technology risk in UK financial services, including CISO and Director of Technology Risk roles.