EvidenceSheet

6.5 Responsibilities after termination or change of employment

Requires the security duties and responsibilities that survive the end of employment, or a move to a different role, to be defined, communicated to the people concerned and enforced.

5
artefacts
0
held by a system
3
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

  • Evidence these were communicated to the individual at the point of departure or change, with acknowledgement · HR system / LMS
  • Records of access removal or adjustment on role change, showing old entitlements withdrawn · Identity provider / directory
  • Evidence covering contractors and third party personnel on the same basis · Vendor register / contract repository

governing documentDocuments that govern the control

  • Documented responsibilities that remain in force after employment ends or after a change of role, such as confidentiality and non disclosure · Policy repository / GRC workspace
  • The leaver and mover procedure showing the security steps and their completion within a defined timeframe · 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

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

6.4 Disciplinary process · 6.6 Confidentiality or non-disclosure agreements