A.5.35 Independent review of information security
Have the security approach and its implementation reviewed independently on a cadence and after significant change.
12
artefacts
0
held by a system
7
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
- Annual review calendar · Document repository
- Board approved review schedule · Policy repository / GRC workspace
- Independent review report · Document repository
- Executive summary of security review · Document repository
- Record of major security change · SIEM / log platform
- Change impact assessment log · SIEM / log platform
- Post change review meeting minutes · SIEM / log platform
governing documentDocuments that govern the control
- Review frequency policy · Policy repository / GRC workspace
- Findings and recommendations document · Document repository
- Reviewer cv and certifications · Document repository
- Conflict of interest statement · Policy repository / GRC workspace
- Contractual agreement for independent audit · Vendor register / contract 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
- reviews performed by internal staff only
- infrequent or ad-hoc review cadence
- lack of documented reviewer independence
- findings not tracked to remediation
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.34 Privacy and protection of personal identifiable information (PII) · A.5.36 Compliance with policies, rules and standards for information security