9.2.1 General
Conduct internal audits at planned intervals to provide information on whether the BCMS conforms both to the organization's own requirements for it and to the requirements of the standard, and whether it is effectively i
3
artefacts
0
held by a system
0
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
none for this control
governing documentDocuments that govern the control
- Audit schedule with planned intervals and evidence of adherence · Policy repository / GRC workspace
- Audit reports addressing conformity to internal requirements, to the standard, and to effective implementation · Policy repository / GRC workspace
- Coverage map showing the whole BCMS is audited across a cycle · 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 test conformity to the standard only and never to the organization's own BCMS requirements
- Effectiveness untested, with audit limited to documentation existence
- Coverage concentrated on easy areas, leaving parts of the BCMS unaudited for years
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 sheet