Skip to main content

Employee offboarding review

How an AI SOC reviews offboarding: find terminated workers who are still active, check what they did before leaving, and ticket any access left behind.

Use case
Updated

The short answer

An offboarding review confirms that a departing employee's access is gone and that nothing unusual happened before they left. Cotool runs offboarding reviews with response agents, and its example detection finds people HR terminated who are still active in Okta.[1][2]

The problem

Adversaries abuse inactive accounts, such as those of people who have left the organization, because no one is there to notice the activity.[7]

Third-party app access is granted per user, and Google's token activity reports list every grant and revocation, so a review can see which apps a departing user authorized.[8]

How an AI SOC handles it

  1. Find leavers who are still active

    An hourly detection compares terminated workers in the HR system with active Okta users and sends each match to triage.[2]

  2. Check other access

    The agent checks the person's Google Workspace OAuth grants and recent 1Password activity.[8][9]

  3. Review the last weeks

    The agent looks for unusual Drive downloads or copies of shared-vault items before the last day.[1][9]

  4. Ticket what remains

    Access that still needs removing goes into a Jira or Linear ticket for the system owners.[3][4]

  5. Remove access with approval

    Where it has write access, the agent proposes suspending the account or revoking sessions for a person to approve.[1][5]

Example

Terminated but still active (T1078)python
leavers = tools.call("rippling_queryWorkers",
                    status="TERMINATED")
active = tools.call("okta_listUsers",
                    filter='status eq "ACTIVE"')
gone = {w["work_email"] for w in leavers}
emit_results([u for u in active if u["email"] in gone])

The detection from Cotool's Detect page. It runs every hour with no log source, calling Rippling and Okta directly, and each result goes to triage.[2]

What people approve

  • Suspending an account or revoking sessions is a state-changing action that can require a person's approval.[5]
  • Response agents cannot close an alert as True Positive. When an agent confirms malicious activity, it escalates the alert and a person closes it.[6]

How Cotool handles it

  • Cotool detections can run against the tools where data already lives, so this check needs no ingested log source.[2]

Integrations used

Sources

  1. Respond to every signal (Cotool Respond) · accessed November 16, 2026
  2. Detection engineering (Cotool Detect) · accessed November 16, 2026
  3. Jira integration (Cotool docs) · accessed November 16, 2026
  4. Linear integration (Cotool docs) · accessed November 16, 2026
  5. AI SOC (Cotool) · accessed November 16, 2026
  6. Alerts (Cotool docs) · accessed November 16, 2026
  7. Valid Accounts, T1078 (MITRE ATT&CK) · accessed November 16, 2026
  8. Manage OAuth token audit activity (Google Workspace Admin SDK) · accessed November 16, 2026
  9. 1Password Events API (1Password Developer) · accessed November 16, 2026

Related use cases

All use cases

Related reading

Attackers are scaling with tokens

Cotool helps defenders operate at machine speed. See how security teams are scaling Detection & Response.

Book a demo