5.5.3 Awareness
The awareness requirements of ISO/IEC 27001 apply to the PIMS, so people working under the organization's control must be aware of the policy, of their contribution, of the consequences of non conformity and of their rol
3
artefacts
0
held by a system
1
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
- Delivery records including contractors and new starters · HR system / LMS
governing documentDocuments that govern the control
- Awareness material covering privacy obligations and individual responsibilities · HR system / LMS
- A check that awareness landed, not merely that it was delivered · 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
- Privacy awareness folded into annual security training as a single slide
- Consequences to the individual whose information is processed never mentioned
- Contractors with access to personal data excluded
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