EvidenceSheet

A.6.2 Terms and conditions of employment

State the security responsibilities of both the person and the organization in the employment agreement.

12
artefacts
0
held by a system
6
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

  • Signed employee contract with security clauses · HR system / LMS
  • Non disclosure agreement signed by employee · HR system / LMS
  • Annual security training attendance record · HR system / LMS
  • Signed security awareness acknowledgement form · HR system / LMS
  • Exit interview checklist with access revocation · HR system / LMS
  • Record of returned company assets · HR system / LMS

governing documentDocuments that govern the control

  • Contract amendments showing security role changes · Policy repository / GRC workspace
  • Contract template including security responsibilities · Vendor register / contract repository
  • Nda addendum for contractors · Vendor register / contract repository
  • Confidentiality policy acknowledgement form · HR system / LMS
  • Employee security policy acknowledgement log · Policy repository / GRC workspace
  • Termination letter referencing security obligations · 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

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

A.6.1 Screening · A.6.3 Information security awareness, education and training