5.5.2 Competence
The competence requirements of ISO/IEC 27001 apply to the PIMS, so the organization must determine, ensure, act on and evidence the competence of people whose work affects privacy performance as well as security performa
4
artefacts
0
held by a system
2
at each review
hard
to go live
HR system / LMS
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
- Evidence of education, training or experience per role holder · Identity provider / directory
- Retained competence records · HR system / LMS
governing documentDocuments that govern the control
- Competence profile for privacy roles · Policy repository / GRC workspace
- Gap actions with an evaluation of effectiveness · HR system / LMS
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
- Security competence records reused for privacy roles that need legal and regulatory knowledge
- Competence assumed from job title
- Actions taken but never evaluated
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