COM-04 Information on information security performance and management assessment of the ISMS
Report information security performance within the scope of the management system to top management on a regular basis, and carry that information into a management review of the system held at least once a year.
4
artefacts
0
held by a system
3
at each review
hard
to go live
Document repository
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- Management review minutes addressing security performance · Policy repository / GRC workspace
- Attendance record evidencing top management presence at the review · HR system / LMS
- Decisions and resource allocations arising out of the review · Document repository
governing documentDocuments that govern the control
- Performance reporting pack presented to top management · Document repository
First move
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
Common gaps auditors find
- Review held less often than once a year or skipped in a busy period
- Reporting shows activity counts with no judgement on suitability or effectiveness
- Review conducted by the security function alone without top management
- Decisions taken but never assigned an owner or a deadline
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 sheetCOM-03 Internal audits of the information security management system · COS-01 Technical safeguards