Skip to content
People controls
ISO 27001A.6.5

ISO 27001 Annex A 6.5 Responsibilities after termination or change of employment

What it says

Information security responsibilities and duties that remain valid after termination or change of employment shall be defined, enforced and communicated to relevant personnel and other interested parties.

Quoted as published. Everything else on this page is written by Control Stack.

In plain English

Define, enforce and communicate the information security responsibilities and duties that remain valid after employment ends or changes, to relevant personnel and other interested parties.

Your organisation must define, enforce and communicate the information security responsibilities and duties that remain valid after someone's employment ends or changes, such as keeping client information confidential. All three parts apply:

  • Define: state which duties continue.
  • Enforce: act when someone breaches them, including after they have left.
  • Communicate: tell relevant personnel and other interested parties, meaning others with a stake, such as a supplier or customer. Your organisation decides who is relevant, based on its risks and context.

Why it matters

People who leave or move still know client details, pricing and system weaknesses. Unless the continuing duties were defined and communicated, your organisation has a weaker case if that knowledge is later disclosed or misused.

How to implement

  1. List the duties that continue after someone leaves or changes role.

    Cover confidential information and know-how gained on the job, and intellectual property, and say how long each one lasts. For a role change, note what still applies from the old role, such as not passing a former client's information to the new team.

  2. Write the duties into the terms people sign.

    Use employment contracts (Annex A 6.2 requires them to state security responsibilities) and confidentiality agreements (Annex A 6.6). Where an existing contract cannot be changed, get written legal advice on what already continues under it, and ask for a signed acknowledgement at exit.

  3. Add a step to your leaver and role-change checklist.

    Treat a role change as one role ending and another starting. Remind the person in writing which duties continue, keep their acknowledgement, and move any security roles they held, such as incident contact, to a named replacement.

  4. Tell other relevant people and interested parties what continues.

    Decide and record who is relevant, based on your risks: often the line manager and the customers and suppliers who dealt with the person. For staff supplied by another company, agree that it tells its people what continues (Annex A 5.20 covers agreeing security requirements with suppliers).

  5. Decide how you will enforce each duty.

    For someone still employed, use the disciplinary process (Annex A 6.4). For someone who has left, the remedy is usually the contract, so name who decides on legal action and know where the signed terms are.

Keep it running

Keep signed terms and acknowledgements for as long as the duties last and any claim could still be brought. Look again when contract templates or the leaver process change, or after a suspected disclosure by someone who has left.

Evidence and audit

  1. Check 1 of 4What an auditor asks for

    Ask for

    The list of continuing duties and the signed terms for a sample of employees and contractors.

    Look at

    Whether each duty on the list appears in what the person actually signed, including on older contracts, and how long it lasts.

    Good evidence

    Every listed duty, such as confidentiality and intellectual property, appears in the person's signed terms or a separate signed agreement, worded so that it continues after employment ends or changes. For an older contract that cannot be changed, written legal advice says what continues under it.

  2. Check 2 of 4What an auditor asks for

    Ask for

    Recent leavers and role changes from payroll or the personnel system, matched to exit records.

    Look at

    Whether people who changed role are covered as well as those who left, and whether each was told what continues.

    Good evidence

    Every sampled leaver and mover has a dated record showing the continuing duties were communicated to them.

  3. Check 3 of 4What an auditor asks for

    Ask for

    Records of suspected breaches of continuing duties, matched to incident, personnel and legal records, or the enforcement route if there are none.

    Look at

    Whether a suspected breach appears in those other records but not in the breach records, who decided what to do and what action followed.

    Good evidence

    Every suspected breach in those records has a named decision and the action taken. If there are none, the person named to decide on legal action produces a sampled leaver's signed terms on request, and those terms cover the continuing duties.

  4. Check 4 of 4What an auditor asks for

    Ask for

    The notices sent to other interested parties for a departure the auditor picks from payroll or contractor records, matched to the suppliers and customers that person dealt with.

    Look at

    Whether those suppliers and customers, and the employer of any supplied staff, were told, or were left off for a recorded reason.

    Good evidence

    The organisation has recorded who is relevant, any supplier or customer left off has a reason, and each party on the record was told what continues.

Mappings

Closest match in ASD Information Security Manual: ISM-0430, Same-day removal or suspension of access no longer required, which partially overlaps with this control.

ASD ISM

ASD Information Security Manual: 2 mappings

Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.

Get help with this control

ISO 27001 training

Mindset Cyber, a PECB Authorised Titanium Partner, sells official PECB ISO/IEC 27001 courses that map directly to the controls in this library.