6.4.1 Prior to employment
Screening and terms and conditions of employment must be applied as the base security guidance requires, read as covering the privacy exposure that the role carries.
3
artefacts
0
held by a system
2
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
- Screening records proportionate to the personal data the role will reach · Identity provider / directory
- Records for contractors and agency staff on the same basis · Document repository
governing documentDocuments that govern the control
- Employment terms carrying confidentiality and data handling obligations · Document 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
- Screening depth set by seniority rather than by data access
- Contractors engaged without equivalent terms
- Terms silent on obligations that survive employment
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 sheet6.3.2 Mobile devices and teleworking · 6.4.2 During employment