How do we…
How do we decide what to monitor and measure in our ISMS, and who evaluates it?
Add to board memoOpen the memo
The short answer
- Recommendation
- Write a short measurement plan: for each objective and each important control or process, the measure, how it is collected, how often, who collects it and who analyses and evaluates it. Report trends to the management review and record the decision when a measure misses.
- Reasoning
- The standard asks you to decide what to monitor and measure, by which method, when, who does it and who analyses and evaluates the results, and to keep the results as evidence, so you can evaluate the performance and effectiveness of the ISMS. Auditors sample the measures over the operating period and ask what you did when one missed its target. Measures that are collected but never analysed are a regular finding.
- Considerations
- The standard's text and the measurement guidance standard, ISO/IEC 27004, are paywalled. The requirements here come from the pack and public guides.
- The pack's four headline measures track readiness to certify. They do not replace measures of how the ISMS performs once it runs.
- Whether a written procedure for measurement is mandatory is disputed in public guides. A written plan is the safe form.
The decision, step by step
Select any step for the reasoning behind it and where the pack covers it.
- Start
- Step
- Decision
- Outcome
Keyboard: Tab to a step, arrow keys move along the flow, Enter pins its explanation, + and − zoom, 0 fits the diagram, Esc closes. The text version below has the same content.
Where a step quotes a number, it is the default in the CISO Times pack. Your own standard may set a different one.
Read as text
The same flow written out: each step, its reasoning and where the pack covers it. 17 steps.
Start
We must show we monitor and measure the ISMS
The auditor wants to see that you know whether the ISMS works, from measures that were defined, collected and read. The pack's checklist lists the results of monitoring and measurement as a required record: a measurement plan and the periodic reports.
In the pack
- P08-A05 Mandatory ISMS Documentation ChecklistRequired Documents
- P08-A10 Stage 1 and Stage 2 Audit Preparation GuideWhat the auditor samples, by clause
Decision
Does each objective have a measure, an owner and a target?
Objectives that cannot be measured cannot be monitored. The pack asks for objectives with a measure, a target, an owner, the resources, a date and how results will be evaluated. If any lacks one of these, answer no.
- Yes: Pick the controls and processes whose effectiveness you will check
- No, or not known: Add the missing measure, owner or target
In the pack
- P08-A05 Mandatory ISMS Documentation ChecklistRequired Documents
Step
Add the missing measure, owner or target
Go back to the objectives and give each what it lacks. An objective measured as 'better security' will fail the first question an auditor asks.
In the pack
- P08-A05 Mandatory ISMS Documentation ChecklistRequired Documents
Step
Pick the controls and processes whose effectiveness you will check
Take the ones that treat your biggest risks and the blocking items the pack names, such as the risk assessment, the internal audit programme and the management review. Check whether the control works, for example by sampling its records, not only whether it exists.
In the pack
- P08-A02 ISO 27001 Implementation Methodology & Project PlanBlocking items
- P08-A10 Stage 1 and Stage 2 Audit Preparation GuideWhat the auditor samples, by clause
Step
Keep the set small enough that someone reads every figure
The pack's own headline set has four measures, reported monthly. A handful that are read and acted on beats a long list that nobody opens. Drop a measure that informs no decision.
In the pack
- P08-A02 ISO 27001 Implementation Methodology & Project PlanHeadline measures
Decision
Can you collect each figure from records you already keep?
A measure that needs new tooling or a manual count each month tends to lapse. Prefer a figure from tickets, logs, trackers or registers. If a figure needs something you do not have, answer no.
- Yes: Would two people collecting it get the same figure?
- No, or not known: Choose a measure you can collect, or add the cheapest source
In the pack
- P08-A05 Mandatory ISMS Documentation ChecklistRequired Documents
Step
Choose a measure you can collect, or add the cheapest source
Replace the measure with one you can collect from existing records, or add the smallest source that gives the figure. Do not keep a measure you cannot collect regularly: gaps in the series are the first thing an auditor sees.
In the pack
- P08-A10 Stage 1 and Stage 2 Audit Preparation GuideWhat the auditor samples, by clause
Decision
Would two people collecting it get the same figure?
Methods should give comparable and reproducible results, or the trend means nothing. Write the source, the filter and the period, so the figure does not move with whoever collects it. If you are not sure, answer no.
- Yes: Write the plan: measure, method, frequency, collector, analyst
- No, or not known: Write the definition: source, filter, period
In the pack
- P08-A05 Mandatory ISMS Documentation ChecklistRequired Documents
Step
Write the definition: source, filter, period
One line per measure is enough. See the metric question for the form. Include what counts as an event, from which system, and over which period.
In the pack
- P08-A05 Mandatory ISMS Documentation ChecklistRequired Documents
Step
Write the plan: measure, method, frequency, collector, analyst
The pack's checklist describes the plan as what is measured, how, when, and who analyses it, plus the periodic reports. Name the person who collects and the person who analyses and evaluates. They may be the same in a small team, but the evaluation must be recorded. Choose an analyst who understands the control and can act on the figure, often the process owner. The ISMS manager reads across the set and top management evaluates the whole in the review.
- Then: Decide where results go
In the pack
- P08-A05 Mandatory ISMS Documentation ChecklistRequired Documents (rule MD-13)
Step
Decide where results go
Send results to the ISMS manager on a regular cycle, and show trends over recent periods in the management review. The review pack asks for monitoring and measurement results against targets, as trends, from the measure owners.
In the pack
- P08-A09 Management Review Meeting PackThe pre-read pack, with owners
- P08-A09 Management Review Meeting PackThe agenda
Step
Collect on schedule and keep the results
Records over the operating period are what the auditor samples, so missing months are a problem. Keep the raw figure, the date and who collected it.
In the pack
- P08-A10 Stage 1 and Stage 2 Audit Preparation GuideWhat the auditor samples, by clause
- P08-A02 ISO 27001 Implementation Methodology & Project PlanThe rules (rule IS-05)
Decision
Did any measure miss its target or trend the wrong way?
Evaluation means reading the result and deciding what it means. If a measure missed, the auditor will ask what was done. If you have not read the results, answer yes and read them.
- Yes, or not known: Record the decision; log a nonconformity if a requirement is missed
- No: Record the conclusion anyway
In the pack
- P08-A10 Stage 1 and Stage 2 Audit Preparation GuideWhat the auditor samples, by clause
Step
Record the decision; log a nonconformity if a requirement is missed
A miss may need no action, a change to the target, a new control or a corrective action. Write which, with the reason. If a requirement of the standard or your own policy is not met, log it as a nonconformity.
In the pack
- P08-A08 ISMS Internal Audit Programme & ProcedureStage 7 — Nonconformity and corrective action
Step
Record the conclusion anyway
'Acceptable, no action' is a conclusion, but it must be written down with the date and the person. An evaluation nobody recorded looks like no evaluation.
In the pack
- P08-A09 Management Review Meeting PackThe decisions to record
Step
Put the trends in the management review pack
Include the results as trends over several periods, with the measure owner's reading. Top management then decides what needs action, and the minutes become evidence of evaluation.
In the pack
- P08-A09 Management Review Meeting PackThe agenda
- P08-A09 Management Review Meeting PackThe pre-read pack, with owners
Outcome
Measures defined, collected, evaluated and read
Review the plan at each management review: drop measures nobody used and add one where a decision lacked a figure. Do not describe the measures as proof that the ISMS is effective. They are the evidence on which the review forms its view.
In the pack
- P08-A02 ISO 27001 Implementation Methodology & Project PlanHeadline measures
Practical checklist
- List the objectives and the controls and processes whose effectiveness matters most.
- Choose a few measures you can collect from records you already keep.
- Write each definition so that two people would get the same figure.
- Name who collects each measure and who analyses and evaluates it, and how often.
- Report trends, not snapshots, to the management review.
- Record what was decided when a measure missed its target, and open a nonconformity if a requirement is not met.
Evidence to have ready
- The measurement plan: measure, method, frequency, collector, analyst.
- Dated results over the operating period, with the evaluation of each.
- Management review minutes showing the results and the decisions taken.
Assumptions
- Your objectives are set, or about to be, so there is something to measure against.
- You have, or will have, a management review that takes the results.
- You aim for ISO/IEC 27001:2022. Any other standard you follow may ask for more.
Not covered here
- Writing the objectives themselves. That is “How do we write an information security policy and objectives that stand up to an ISO 27001 audit?”.
- Defining a single metric so it means the same each month. That is “How do we define a security metric so the number means the same every month?”.
- Checking a metric's data before it is reported. That is “How do we check a metric's data before it is reported?”.
- Deciding which metrics the board sees. That is “How do we choose which metrics the board sees?”.
Related questions
- How do we write an information security policy and objectives that stand up to an ISO 27001 audit?
- How do we define a security metric so the number means the same every month?
- How do we run a management review that actually decides things?
- If an internal audit, an incident or a complaint shows a nonconformity, then how do we correct it and stop it coming back?
- How do we keep our ISO 27001 certificate after the certification audit?