9.1 Monitoring, measurement, analysis and evaluation
The organization must determine what is to be monitored and measured, including security processes and controls; which methods of monitoring, measuring, analysing and evaluating will give valid results (comparable and reproducible methods are considered valid); when monitoring and measurement are done; who does them; when results are analysed and evaluated; and who does that analysis and evaluation. Documented information must be available as evidence of results, and the organization must judge how well it performs on security and how effective the ISMS is.
Source: ISO/IEC 27001:2022, 9.1. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open ISO/IEC 27001:2022 in the compliance library.
Clauses 4 to 10 are the management-system requirements: none of them can be excluded when an organisation claims conformity. The 93 Annex A controls are a reference set: one may be excluded with a justification in the Statement of Applicability. Certification bodies assess conformity; the evidence lists here are what auditors commonly ask for, not a list the standard prescribes.
These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- Metric results for processes and controls over time · Policy repository / GRC workspace
- Analysis and evaluation reports on security performance and ISMS effectiveness · Document repository
- Evidence the results fed management review · Policy repository / GRC workspace
governing documentDocuments that govern the control
- A measurement plan listing what is measured, methods, frequency, responsibilities and when and by whom results are analysed · Policy repository / GRC workspace
First move
Common gaps auditors find
- Metrics are collected but never analysed or evaluated
- Methods are not repeatable, so results cannot be compared
- Measurements cover activity counts rather than control effectiveness
- Responsibilities for measurement are unassigned
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheet8.3 Information security risk treatment · 9.2.1 Internal audit: general