9.2 Internal audit
Audit the BCMS internally on a planned basis, and run the audit programme that makes those audits objective, competent and consequential.
3
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
- Audit programme and completed audit reports · Policy repository / GRC workspace
- Auditor independence evidence · Policy repository / GRC workspace
governing documentDocuments that govern the control
- Findings tracked to 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
- Audits performed by the people who run the BCMS
- Programme planned but not completed, with deferrals unescalated
- Findings closed on assertion rather than on verified action
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 sheet9.1 Monitoring, measurement, analysis and evaluation · 9.2.1 General