HR-02 Employment terms and conditions
Bind internal and external personnel through their employment or engagement terms to the applicable security policies, and capture a documented acknowledgement of the security policy and its subordinate instructions befo
4
artefacts
0
held by a system
0
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
none for this control
governing documentDocuments that govern the control
- Employment and contractor agreement templates showing the information security obligation clause · Vendor register / contract repository
- Signed or electronically captured policy acknowledgements for a sample of personnel · HR system / LMS
- Comparison report of acknowledgement timestamps against account provisioning timestamps · Policy repository / GRC workspace
- Onboarding checklist that makes acknowledgement a precondition for account creation · 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
- Accounts opened first and the acknowledgement chased up afterwards
- Acknowledgement recorded against a policy version that has since been superseded
- Agency and freelance personnel sign no equivalent undertaking
- Acknowledgement taken once at hire and never renewed after major policy revisions
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 sheetHR-01 Verification of qualification and trustworthiness · HR-03 Security training and awareness programme