5.7.2 Internal audit
The internal audit requirements of ISO/IEC 27001 apply to the PIMS, so internal audit must test conformity and effective implementation of the privacy extension as well as of the security management system.
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
- Audit reports addressing privacy conformity and effectiveness · Data governance / DLP tooling
- Auditor independence and competence evidence for privacy subject matter · HR system / LMS
governing documentDocuments that govern the control
- Audit programme covering PIMS clauses and the applicable control annex · Policy repository / GRC workspace
- 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
- Audit scope inherited from the ISMS, so PIMS clauses are never sampled
- Auditors competent in security auditing a legal and regulatory subject they do not know
- Findings raised against documentation existence rather than operating effectiveness
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 sheet5.7.1 Monitoring, measurement, analysis and evaluation · 5.7.3 Management review