Insider Risk during layoffs, reorgs and M&A

Big changes are when access, pressure and opportunity meet: a layoff list, a reorg that shrinks a role, a deal that isn't public yet. Above investigates access and data for the people and systems a change affects, scoped by HR or Legal, without guessing anyone's mood.

Two office campuses on separate plots, joined by a narrow footbridge with a gap in its middle.

INC-028An IT admin on a layoff list

Confirmed threat

A hidden admin and a backup wipe

  1. OktaHidden admin account created
  2. AWSBackup cleanup job scheduled
  3. CrowdStrike FalconShell history cleared

Response Disable both accounts and the job

Why speed matters in a period of change

  • $21.9M

    a year when incidents take more than 90 days to contain, against $14.2M under 30 days. Ponemon Institute, 2026 Cost of Insider Risks.

  • 67 days

    on average to contain an insider incident. Ponemon Institute, 2026 Cost of Insider Risks.

  • 4 years

    in prison for a developer whose kill switch fired when he was put on leave, after a reorg cut his role. US Department of Justice, 2025.

Why change makes Insider Risk hard to see

“Everybody's activity changes at once”

Handoffs, exports and access requests spike during a change, so every baseline breaks at the moment you need one.

“Nobody removed the old access”

A reorg moves people but rarely takes back what they had. An acquisition adds a second identity system that no one has reviewed.

“We can't share the list”

A layoff list or a deal can't be widely known, so security often has to protect people and systems it hasn't been told about.

The night before the reorg

The night before the reorg

Above investigative agents

  • Timeline
  • Contextual analysis
  • Reasoning
  • Recommended actions

Ready for security, HR, and legal to act on together.

What the investigation hands you

Ready for security, HR, and legal to act on together.

The night before the reorgINC-028 · An IT admin on a layoff list

Confirmed threat

A hidden admin and a backup wipe

Admins create accounts and schedule jobs every week; no rule could see intent.

The evidence

  • Workday
  • ServiceNow
  • Okta
  • AWS
  • CrowdStrike Falcon

The HR event, the generic admin account, the backup-job export, the Saturday job and the cleared history, inside the 30-day window.

The response

  1. Disable both accounts and the job
  2. Preserve the evidence
  3. Bring in Legal and HR before notification

A human confirms

Talk to a human, 30 minutes

A solutions engineer walks you through a real case.

How Above investigates during a period of change

  1. HR or Legal names the people in scope, on a watch list.

  2. Exports, privilege changes and leftover access. No sentiment scoring.

  3. The record shows who was in scope, why, and what was found.

  • Workday
  • HiBob
  • Okta
  • Microsoft Entra
  • AWS
  • ServiceNow
  • GitHub
  • Google Drive

Evidence this investigation reads

Signals Above reads during layoffs, reorgs and M&A

Read for the people in scope, for the length of the event.

Show the signals from
  • HR events that define the window

    Workday, HiBob

    Layoff notices, role changes, transfers and terminations.

  • Access left over after a move

    Okta, Microsoft Entra

    Old-role groups the new job doesn't need.

  • Privilege changes during the window

    Microsoft Entra, AWS

    Admin rights granted or used by people in scope.

  • Changes outside change control

    AWS, ServiceNow

    Production changes with no change request.

  • Code that references its author

    GitHub

    Logic tied to one person's account: how kill switches work.

  • Bulk exports by people in scope

    Google Drive

    Large downloads in the days after an announcement.

  • Deal material beyond the deal team

    Google Drive

    Deal folders opened or shared outside the named team.

  • Logging switched off or records deleted

    AWS

    Cloud logging disabled or audit records removed.

  • Two identity systems after an acquisition

    Okta, Microsoft Entra

    Accounts in both identity providers, reviewed by neither.

Event-based, never mood-based

Periods of change are hard on people. Above doesn't infer emotions, score engagement or read messages for tone, and AI that infers emotions at work is banned in the EU under the AI Act. It investigates access and data for a group HR and Legal define, for as long as they define it.

  • HR or Legal decides who is in scope, and why.
  • People stay pseudonymized, and every unmask is logged.
  • No sentiment, emotion or productivity scoring.

Related use cases

Malicious insider and IP theft

Legitimate access used to steal, leak or sabotage. Above separates intent from the job and builds the record.

  • Departing employee data theft

    Customer lists, pricing and code that leave in the weeks around a resignation.

  • AI agent insider threat

    What AI agents did with the access they were given, who they acted for, and whether it matched the ask.

Questions about layoffs, reorgs and M&A

Why does Insider Risk rise during layoffs and M&A?

Access, pressure and opportunity change at the same time. People losing their jobs may take work they feel they own, people whose role shrinks may keep access they no longer need, and deal teams hold material that is valuable before it's public. In a 2025 federal case, a developer whose role was cut in a reorg planted a kill switch.

Should we monitor employees more closely before a layoff?

Watch the access and data that matter, for the people in scope, for a defined period, with HR and Legal's approval. Don't score sentiment or productivity. It's intrusive, and AI that infers emotions at work is banned in the EU.

Who should trigger the review?

HR or Legal, because they know the event and who it affects; security runs the investigation. That matches NIST SP 800-53 PM-12, which calls for a cross-discipline insider threat team and asks for legal counsel and the privacy official to be involved.

What about people at the company we acquire?

Connect both companies' identity providers and Above reads access across them in one case. A person who holds rights in both shows up once, with everything they can reach, so leftover or duplicated access from the deal is found and reviewed before it becomes the way data leaves.

Get through the change with your data intact

See how an event-based investigation is scoped, run and closed.