Module 10: Employee Off‑Boarding & AI Access Termination - DRAFT

Why Off‑Boarding Is a Security Event

Departures are high-risk moments for:

• Residual access to AI tools.
• Forgotten API keys and integrations.
• Unreviewed AI-generated drafts and histories containing client or internal context.

Treat off‑boarding as a coordinated security action, not just HR paperwork.

---

Scope

Applies when:

• An Employee resigns.
• An Employee is terminated.
• A contractor’s engagement ends.
• A role change removes access to certain systems.

---

Day‑Of‑Departure Checklist (AI-Specific)

Access

• Disable SSO access to all approved AI platforms.
• Revoke platform logins and MFA.
• Remove admin/elevated roles first.

API Keys

• Identify keys associated with the departing Employee.
• Revoke personal keys.
• Rotate any shared keys to which they had access.
• Update scripts, integrations, and automations using those keys.

Data & Sessions

• Review AI conversation histories and decide which to:
  • Archive with updated ownership, or
  • Delete, per policy.
• Secure any downloaded AI outputs that include client or sensitive data.

---

Within 48 Hours

• Reassign ownership of:
  • Custom prompts/templates used in work.
  • AI agents/workflows maintained by the Employee.
• Review active engagements:
  • Identify AI-assisted deliverables.
  • Confirm review status.
• Reclaim licenses/seats on AI platforms.

---

30–90 Day Follow-Up

• Audit for residual access and missed keys.
• Confirm no continuing logins or activity.
• Close the off‑boarding record once checks are complete.

---

Work Product Handling

• Approved deliverables: remain part of engagement or project records.
• Draft/unreviewed outputs: must be reviewed by remaining team members before use.
• Outputs sent without proper review: handle through the incident process.