COM-03 Internal audits of the information security management system
Have subject matter experts run internal audits at least annually to test whether the information security management system meets the identified legal, regulatory, self imposed and contractual requirements and internal
4
artefacts
0
held by a system
2
at each review
hard
to go live
Policy repository / GRC workspace
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
- Internal audit reports issued within the last twelve months · Policy repository / GRC workspace
- Independence and competence records for the auditors used · HR system / LMS
governing documentDocuments that govern the control
- Internal audit programme covering the full management system scope · Policy repository / GRC workspace
- Corrective action tracker showing findings through to verified closure · Policy repository / GRC workspace
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
- Programme repeats the same familiar areas and leaves parts of scope unaudited
- Auditors review processes they operate themselves
- Findings logged without risk assessment or a due date
- Actions marked complete with no evidence that they worked
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-02 Policy for planning and conducting audits · COM-04 Information on information security performance and management assessment of the ISMS