A.5.37 Documented operating procedures
Document operating procedures for information processing facilities and make them available to those who need them.
9
artefacts
3
held by a system
0
at each review
moderate
to go live
SIEM / log platform
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Email distribution log · SIEM / log platform
- Version control repository commit history.txt · Source control / CI pipeline
- Physical access log to facility control room · Physical access / facilities
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Server room startup shutdown procedure · Policy repository / GRC workspace
- Backup process workflow · Policy repository / GRC workspace
- Incident response operational guidelines · Policy repository / GRC workspace
- Intranet procedure page access report · Policy repository / GRC workspace
- Procedure change log · Policy repository / GRC workspace
- User access log to procedure repository · Policy repository / GRC workspace
First move
Start with the 3 of 9 artefacts that already live in a system (SIEM / log platform); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- outdated procedures still in use
- no evidence of distribution to staff
- missing version control for revisions
- procedures not aligned with actual practice
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 sheetA.5.36 Compliance with policies, rules and standards for information security · A.6.1 Screening