Clause 9 – Performance evaluation

Clause 9.1 Monitoring, measurement, analysis and evaluation

Mandatory requirement Documented information required

What it means in plain language

Decide what you measure to know whether security works (e.g. incidents, patching, training), how and when you measure, who analyses the results, and then evaluate performance and effectiveness.

Is it mandatory? Yes. Clauses 4–10 are the management-system requirements; all of them must be met to be certified, and none can be excluded.

Documented information

  • Evidence of the monitoring and measurement results.

Why this requirement matters

Teams should choose measurements that show whether security performance and control effectiveness are improving, staying stable, or drifting. Connect the measurement plan to objectives, logging and monitoring, analysis responsibilities, and management review so data turns into decisions rather than isolated reports. A strong implementation identifies who measures each indicator, how often it is reviewed, what thresholds matter, and which records prove the analysis was performed and acted upon.

Common auditor findings to check for

Potential gaps to test in your own environment, not a claim about observed audit frequency.

  • KPI dashboards exist, but the organisation has not defined why each metric is relevant to an information security objective or risk outcome.
  • Measurement data is collected, yet no named reviewer analyses trends or explains what action should follow a worsening result.
  • Results are presented to management, but the underlying definitions, data sources, and time periods differ between reports, reducing comparability.

How you can implement it

Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.

  • Build a measurement plan that maps each metric to an objective, risk, or control area, such as patch latency, encryption coverage, incident closure time, phishing outcomes, or open corrective actions. State the owner, source system, method of calculation, review cadence, and the decision threshold that triggers discussion.
  • Use the Information Security Objectives template to link targets and actuals, then feed the numbers into the management review procedure. The ISMS manager should prepare a concise trend pack, while control owners explain outliers, data gaps, and planned improvements.
  • For operational credibility, define whether the measure is automated, sampled, or manually compiled, and keep the rule consistent over time. If the source changes, record the reason and the impact on trend comparability so reviewers do not mistake a measurement change for real improvement.
  • Capture evidence that the organisation evaluated performance, not just collected data: annotated dashboards, meeting minutes, actions assigned, and follow-up due dates. If a result is poor, note the chosen response, such as corrective action, process adjustment, or a revised target, with accountable owners.

What an auditor will ask to see

  • Metric definition sheet showing formula, owner, source, frequency, and threshold.
  • Trend dashboard or spreadsheet with dated measurement results and analysis comments.
  • Management review minutes referencing the metrics, decisions, and follow-up actions.
  • Information Security Objectives template populated with target, actual, and action fields.

Baseline documents in the kit

These free kit documents help you document or evidence clause 9.1. Each one is tailored to your organization when you build your kit.

Connect this work to your ISMS

Review the dependencies with 6.2 — Information security objectives and planning to achieve them and 9.3 — Management review. Keep the ownership and evidence consistent across these activities.

Plan your ISO/IEC 27001 implementation timeline for the wider implementation context.

Use the SIG and CAIQ questionnaire accelerator to find supporting documents. A mapping is a starting point: verify your actual operating evidence before answering a buyer.

For help adapting this to your environment, explore ISO/IEC 27001 consulting, starting with a free one-hour consultation.

Get these documents tailored to your organization

109 ready-to-edit documents, including all 19 mandatory ones, tailored from a short scoping questionnaire and linked to your risk register and SoA.

Start free

Plain-language interpretation by an ISO/IEC 27001 lead implementer, not the official text of ISO/IEC 27001:2022.