Chapter 20

Insider Threat Playbook

Insider threat investigations are the most technically complex and emotionally fraught incidents in IR. The attacker is an employee — with legitimate access, institutional knowledge, and employment law protections that external attackers don't have. The investigation must be thorough, legally sound, and handled with extreme discretion.

Scenario

A DLP alert fires on a Tuesday evening: a software engineer has uploaded 4.2 GB to personal Dropbox. The alert is triggered by a DLP policy that flags bulk uploads to consumer cloud storage services. The engineer's last day is Friday — the engineer accepted an offer from a direct competitor two weeks ago and gave notice Monday morning. The data includes source code repositories, internal technical documentation, and customer configuration data.

The IR team lead is notified at 9 PM. The question isn't just "what did they take" — it's also "what do we do tonight" when the engineer is still employed and access removal before investigating the full scope may destroy forensic evidence or trigger legal complications.

Three Categories of Insider Threat

Insider threats are not monolithic. The response, legal handling, and investigation approach differ significantly by type. Correctly categorizing the insider threat early shapes every subsequent decision.

CategoryDescriptionPrimary motivationResponse priority
Malicious insider Employee deliberately takes or damages company assets for personal benefit, competitive advantage, or malice. Includes: employees leaving for competitors, employees selling data to third parties, disgruntled employees sabotaging systems. Financial gain, competitive advantage, revenge Evidence preservation, legal action, full forensic scope
Negligent insider Employee causes security incident through negligent behavior — clicking phishing links, storing data insecurely, sharing credentials, using unauthorized personal devices for work. Convenience, lack of awareness, poor judgment Remediation, training, access cleanup — not typically punitive investigation
Compromised insider Employee's credentials or system are compromised by an external attacker who then acts with the insider's permissions. The employee is a victim, not a threat actor. N/A — the employee did not act maliciously Standard credential compromise response (see Chapter 19 / BEC playbook); care not to treat the employee as suspect
Common mistake: treating a compromised insider as a malicious one

Behavioral anomalies in user activity are frequently triggered by account compromise, not malicious intent. Before treating any insider threat investigation as punitive, confirm that the activity is attributable to the employee's deliberate actions rather than a compromised account. Evidence of compromise: authentication from unusual geographies, simultaneous sessions from multiple IPs, activity at hours inconsistent with the employee's normal work patterns. Evidence of deliberate action: on-premise activity at expected times, use of personal devices (company laptop), searches for specific data followed immediately by exfiltration.

Insider threat investigations are unique in that they cannot be conducted by security alone. HR and Legal must be involved from the start. This is not optional — conducting a covert investigation of an employee without HR and Legal awareness can expose the organization to employment law liability and can compromise any subsequent legal or disciplinary action.

  Stakeholder Roles in Insider Threat Investigations
  ═══════════════════════════════════════════════════════════════════

  SECURITY (IR team lead)
  ─────────────────────────────────────────────────────────────────
  Responsible for:
  → Technical investigation: what data was accessed, copied, transmitted
  → Evidence preservation: ensuring forensic evidence is collected and
    maintained in a legally defensible manner
  → Scope determination: what is the full extent of the incident
  → Detection: ongoing monitoring during investigation

  LEGAL COUNSEL
  ─────────────────────────────────────────────────────────────────
  Responsible for:
  → Advising on investigation scope and methods (what is legal)
  → Employment law guidance: what can you do without violating rights
  → Evidence preservation guidance: what must be preserved, how
  → Privilege: some investigation communications may be attorney-client
    privileged — legal counsel may want to "direct" the investigation
  → Exit agreement: NDAs, IP assignment clauses, non-compete (state-dependent)
  → Law enforcement referral decision

  HUMAN RESOURCES
  ─────────────────────────────────────────────────────────────────
  Responsible for:
  → Employment documentation: employee's access, role, responsibilities
  → Termination coordination: when and how access is revoked
  → Disciplinary process: ensuring process is followed; protects company
    from wrongful termination claims
  → Employee communication: who speaks to the employee, what they say

  RULE: No significant investigation step without notifying all three.
  A security team that investigates and then presents a finished report
  to Legal 2 weeks later may have already compromised the legal case.

Evidence Preservation: The Window Is Closing

In the scenario, the engineer has three days until their last day. After Friday, you lose: physical access to their corporate laptop, the ability to conduct a forensic interview while they are still employed, and any corporate controls you can exert over their behavior. Evidence preservation must happen before access is revoked — which means it must happen covertly before Friday.

  Insider Threat Evidence Preservation Priorities
  ═══════════════════════════════════════════════════════════════════

  IMMEDIATE (before access is revoked):
  ─────────────────────────────────────────────────────────────────
  → Remote forensic image of endpoint (corporate laptop) via EDR
    without alerting the employee (most EDR platforms support this)
  → Preserve all email in their mailbox (legal hold in M365/Google Workspace)
  → Preserve all Slack/Teams messages (legal hold or export)
  → Capture DLP logs for all exfiltration activity
  → Export SIEM/UEBA logs for the employee's activity over their tenure
  → Preserve cloud storage access logs (SharePoint, OneDrive, Dropbox
    corporate accounts, GitHub/GitLab activity)

  COORDINATE WITH LEGAL BEFORE:
  ─────────────────────────────────────────────────────────────────
  → Accessing personal email or personal cloud storage accounts
    (this may require a court order; doing it without one may be illegal)
  → Interviewing the employee (legal must be present or advise)
  → Any communication with the employee about the investigation
  → Access to personal devices (BYOD) — requires consent or court order

  DO NOT:
  ─────────────────────────────────────────────────────────────────
  → Delete or modify any data the employee created (preserves evidence
    and avoids spoliation claims)
  → Alert the employee to the investigation before Legal/HR are ready
  → Access personal accounts without legal authority
  → Take punitive action (access revocation, termination) before
    Legal and HR give the green light — may compromise legal remedies

User and Entity Behavior Analytics (UEBA)

UEBA platforms build behavioral baselines for individual users and flag deviations from those baselines. For insider threat investigations, UEBA provides two things: the alert that triggered the investigation (anomalous bulk upload), and historical context for the employee's activity pattern that helps establish intent and scope.

UEBA signalWhat it indicatesInvestigative value
Bulk access to sensitive files outside normal work hours Employee is collecting data during off-hours when monitoring may be reduced Establishes deliberate, non-incidental data collection; pattern inconsistent with work task
Access to files outside normal job function Employee is reaching into areas of the company they don't normally work with Suggests targeted data collection, not accidental access
Large data volume upload to personal cloud storage Active exfiltration Identifies exfiltration channel; combined with content type identifies what was taken
Searches for specific sensitive topics (competitors, M&A, customer lists) Targeting — employee is looking for specific valuable data Establishes intent and scope; search queries show what they were looking for
Badge access after hours in server room or sensitive areas Physical access to hardware outside normal work patterns May indicate data theft via physical media (USB drive)
Activity spike in the two weeks before resignation / announcement Pre-departure data collection — classic "I'm leaving so I'll grab what I need" behavior Establishes timeline relative to departure decision

Exfiltration Channels and Detection

Insider threat exfiltration uses different channels depending on the insider's access and technical sophistication. Understanding the channels helps scope the investigation — you need to look at all plausible channels, not just the one that triggered the initial alert.

  Common Insider Exfiltration Channels and Detection Methods
  ═══════════════════════════════════════════════════════════════════

  CLOUD STORAGE SERVICES (Dropbox, Google Drive, OneDrive personal)
  ─────────────────────────────────────────────────────────────────
  Detection: DLP policy on uploads to consumer cloud storage;
             proxy logs showing large HTTPS uploads to cloud service domains;
             UEBA volume anomaly
  Key evidence: upload timestamps, file names/types, total volume
  Investigation note: if data was uploaded to personal Dropbox on a
  corporate device, Dropbox corporate account may have access logs;
  personal Dropbox requires a subpoena or law enforcement cooperation

  EMAIL (personal Gmail, Yahoo, ProtonMail)
  ─────────────────────────────────────────────────────────────────
  Detection: DLP policy on attachments sent to external personal domains;
             email gateway logs showing large attachments to personal email
  Key evidence: To address, Subject, attachment names, timestamps
  Investigation note: email body and attachment content visible in
  corporate email gateway logs

  USB / REMOVABLE MEDIA
  ─────────────────────────────────────────────────────────────────
  Detection: DLP/endpoint agent logging of USB device connections and
             file copy events; Sysmon EventID 6 (driver load) for
             removable media on Windows
  Key evidence: Device serial number, files copied, timestamps
  Investigation note: very hard to detect after the fact if endpoint
  agent wasn't monitoring at the time; physical access logs

  AIRDROP / LOCAL NETWORK TRANSFER
  ─────────────────────────────────────────────────────────────────
  Detection: Network traffic analysis; endpoint agent detecting AirDrop
             share; anomalous LAN traffic to unknown MAC addresses
  Key evidence: Destination MAC address, file transfer events
  Investigation note: difficult to detect; most DLP solutions miss this

  PRINT / SCREENSHOT
  ─────────────────────────────────────────────────────────────────
  Detection: Print server logs; screen capture monitoring (if deployed);
             physical security cameras in print areas
  Key evidence: Print job logs showing document names and volumes
  Investigation note: no technical prevention; primarily detective

Q & A

Q: The engineer's last day is Friday. Legal says we should not alert the employee to the investigation before then. Do we let them continue working and potentially exfiltrating more data?

This is a legal strategy decision, not a security one — defer to Legal. The reason Legal may want to delay: alerting the employee allows them to delete evidence from personal devices and accounts before you can obtain a court order, and may compromise any civil lawsuit for trade secret misappropriation. The security countermeasure while maintaining silence: covertly restrict access without the employee knowing. Many DLP and endpoint management platforms allow you to silently block specific upload destinations (Dropbox) without an error message that would alert the employee. You can also apply a "shadow" access restriction that allows the employee to see their existing access but blocks any new exfiltration attempts. This prevents further damage while preserving the legal strategy. The alternative — immediately restricting access — may be legally cleaner in some jurisdictions but alerts the employee and allows evidence destruction.

Q: How do you know if the 4.2 GB upload contained trade secrets versus the employee's personal files they're taking with them?

DLP classification is your first source: did the DLP policy that fired classify the content as confidential or proprietary? If the policy is based on content inspection (not just file size), it may have already identified specific document types or content patterns. Beyond DLP: review the specific file names and types in the upload log — does this match business-sensitive content (source code, customer data, financial records) or personal content (photos, personal documents)? If the EDR agent logged individual file copy events, you have a file-by-file list. For files where the names are ambiguous, Legal can subpoena Dropbox for file contents if a lawsuit is filed. The initial threshold for action is not "was it definitely trade secrets" — it's "was there sufficient evidence to investigate further." Uploading 4.2 GB of company data to personal cloud storage on the day after giving notice to leave for a competitor clears that threshold.

Q: What legal remedies does the company have if the investigation confirms intentional trade secret theft?

Several parallel tracks depending on jurisdiction and facts: (1) Civil litigation: the Defend Trade Secrets Act (DTSA) in the US provides a federal civil cause of action for trade secret misappropriation. An expedited temporary restraining order (TRO) can be obtained requiring the employee to preserve and return all copied data immediately — and can prevent them from using the information at their new employer. (2) Criminal referral: trade secret theft above certain thresholds is a federal crime under the Economic Espionage Act. Refer to FBI if the evidence supports criminal charges. (3) Injunctive relief against the new employer: if the competitor is benefiting from the stolen data, the company can sue the competitor as well. (4) Exit agreement enforcement: if the employee signed NDA and IP assignment agreements, enforce them. The forensic evidence collected during the IR investigation is the foundation for all of these legal remedies — which is why proper evidence preservation and chain of custody documentation is critical.

Q: An employee reports their coworker is selling customer data on the dark web. How do you start an insider threat investigation without tipping off the suspect?

Start immediately but covertly: (1) Notify Legal and HR before any investigation action. This investigation may require very careful handling given the seriousness of the allegation. (2) Apply legal hold to the suspected employee's email and messaging accounts without any employee-visible notification. (3) Review DLP logs and UEBA data for the suspected employee over the past 90 days — look for bulk data access and exfiltration patterns that correlate with customer data. (4) Check dark web intelligence sources for actual evidence of the alleged data — this validates the tip and identifies what specific data may have been taken. If you find actual customer records for sale, that is strong evidence and changes the urgency. (5) Preserve evidence before restricting access — once the employee is restricted or terminated, their ability to delete evidence from corporate systems drops significantly, but the window to preserve existing evidence closes. (6) Law enforcement referral: selling customer data may be a violation of multiple statutes. Legal counsel should assess whether FBI referral is appropriate given the evidence. Do not tell the reporting employee what investigative steps you're taking.

Q: After the investigation, the company decides not to pursue legal action. How do you reduce the risk of this happening again?

Three categories of improvement: (1) Technical controls — DLP policy coverage should alert on bulk uploads to any consumer cloud storage service, not just the one caught in this incident. Block USB write access on corporate endpoints by policy (whitelist specific approved USB devices). Implement data classification so the most sensitive data has the strongest controls. (2) Process controls — offboarding process should include a systematic review of DLP alerts for departing employees in their final two weeks, with UEBA analysis of their data access patterns. HR should provide IT security with notice of departures to competitors so monitoring can be enhanced for that specific window. Exit interviews should explicitly cover NDA reminders and IP assignment acknowledgment. (3) Detection improvement — deploy UEBA rules specifically looking for the pre-departure data collection pattern: access volume spike + destination change (corporate to personal storage) in the two weeks before a flagged departure.