Part of ISO 27001: Critical success factors, a series on building a management system that reflects how your organisation really runs.
What it is
Metrics tell the management forum whether controls are working and whether you're moving towards your objectives. They're the routine half of the feedback loop; security events are the other half.
Automation without good definitions just lets you produce high volumes of data. The value is usually in condensing it.
What the standard asks
Clause 9.1 asks you to decide:
- what needs to be monitored and measured, including processes and controls
- the methods to use, so the results are comparable and reproducible
- when monitoring and measuring happen, and who does it
- when the results are analysed and evaluated, and by whom
You need to keep evidence of the results and evaluate both your information security performance and the effectiveness of the ISMS as a whole.
What good looks like
- A handful of measures, each tied to an objective or a key control.
- Each metric has a definition, an owner and a threshold, so everyone knows what good looks like and what triggers action.
- Trends rather than snapshots. The forum sees direction of travel, not a single month's number.
- Metrics lead to decisions. When one crosses its threshold, an action or a risk update follows.
Evidence an auditor will ask for
- Definitions of what is measured, how, when and by whom
- The results over time
- Forum minutes showing the results were reviewed and acted on
Common failure modes
- Vanity metrics. Phishing emails blocked, patches deployed: big numbers that say little about risk.
- The forty-KPI dashboard. Nobody can tell which three matter, so none of them gets discussed.
- Measured but never discussed. A report that nobody reads is always worthless.
- No thresholds. Numbers without a line in the sand can't prompt a decision.
How it connects
Feeds from
- Control operation, which produces the data
- Your objectives, set as part of the scope
Feeds into
- The management forum
- Risk analysis, when results change the picture of a risk
- The risk improvement plan, when action is needed
Where it sits in the plan
Stage: Check. A first set of metrics is agreed once controls are running and gathered in Check. Expect to refine them every cycle; the forum is the best judge of which measures earn their place.
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.