Playbooks

T1078

Insider Threat Response Playbook

A structured playbook for detecting, triaging, investigating, and responding to insider threats — from negligent insiders and credential theft to malicious data exfiltration by trusted employees.

View on Graph

What This Playbook Covers

  • This playbook handles confirmed or suspected insider threat activity. “Insider threat” covers three distinct scenarios, each with different detection signals and response procedures
  • It does not cover external attackers who have compromised an insider account — that is credential theft response. The distinction matters because the remediation is different

Insider Threat Types

TypeDescriptionMotivationTypical Indicators
Malicious insiderEmployee or contractor deliberately stealing data, sabotaging systems, or abusing accessFinancial gain, revenge, ideology, competitive advantageLarge data transfers, unusual access patterns, privilege escalation
Negligent insiderUser who violates policy through carelessness — sharing credentials, falling for phishing, misconfiguring systemsConvenience, lack of awareness, time pressureCredential sharing, shadow IT, policy violations
Compromised insiderLegitimate user whose credentials are stolen by an external attackerExternal actorAnomalous authentication, impossible travel, lateral movement

Phase 0: Determine the Insider Threat Type (0-15 minutes)

Before executing response actions, classify the incident. The wrong classification leads to the wrong response.

Malicious Insider Indicators

IndicatorWhat to CheckConfidence
Mass file access/downloadFile server logs, DLP alerts — hundreds or thousands of files accessed in a short windowHigh
External data transferDLP alerts, email logs, web proxy — data sent to personal email, cloud storage, or USBHigh
Privilege escalationEvent ID 4728, 4732 — user added themselves or a colleague to a privileged groupHigh
Unusual work hoursAuthentication logs, badge access — activity at 2 AM from someone who normally works 9-5Medium
Job dissatisfaction signalsHR data — recent resignation, poor performance review, policy violation warningsContextual
Data deletion/destructionFile audit logs, volume shadow copy deletion — deliberate destruction of evidenceCritical

SPL query — detect mass file access:

index=fileserver Operation=Read OR Operation=Access
| stats count by UserName, SourceFile, _time
| eventstats dc(SourceFile) as UniqueFiles by UserName, date_hour
| where UniqueFiles > 500
| eval alert = "HIGH — " . UserName . " accessed " . UniqueFiles . " unique files in one hour — potential data staging"
| table _time, UserName, UniqueFiles, alert
| sort - UniqueFiles

Negligent Insider Indicators

IndicatorWhat to CheckConfidence
Credential sharingRepeated failed logins from multiple IPs, then successful logon — shared passwordMedium
Phishing susceptibilityMultiple phishing simulation failures; reported malicious emails without clickingMedium
Shadow IT usageWeb proxy logs — unsanctioned cloud services, personal file sharingMedium
Policy violationHR records — previous warnings about data handling or equipment useContextual

Compromised Insider Indicators

IndicatorWhat to CheckConfidence
Impossible travelAuthentication logs — logon from US and Asia within 30 minutesHigh
Anomalous locationAuthentication logs — logon from a country the user has never visitedHigh
New device registrationMFA logs — new device or new browser registeredMedium
Anomalous behaviorUser behavior analytics (UBA) — sudden change in access patternMedium

If impossible travel or anomalous authentication is present, this is a compromised insider — escalate to credential theft response.


Phase 1: Immediate Containment (15-30 minutes)

Critical Actions — Do These First

For malicious insider:

  • Do NOT alert the user — notifying the user may trigger data destruction, evidence deletion, or escalation. Work quietly with legal and HR.
  • Disable network access — block the user’s workstation at the switch level or via NAC
  • Revoke VPN access — prevent remote access
  • Disable the user accountDisable-ADAccount -Identity "UserName" — but only after confirming HR or legal approval
  • Block external data transfers — enable restrictive DLP policies for all data from that user’s systems
  • Disable USB ports — if the user is still onsite, disable removable media access via Group Policy

For negligent insider:

  • Notify the user’s manager — negligent insiders require education, not containment
  • Revoke temporary access — if the user shared credentials, reset passwords and require MFA re-enrollment
  • Reschedule phishing training — if the user fell for a phishing simulation, assign remediation training

For compromised insider:

  • Reset the user’s passwordSet-ADAccountPassword -Identity "UserName" -Reset
  • Revoke all session tokens — sign out of all active sessions (Azure AD, O365, VPN)
  • Disable MFA tokens — de-register all MFA devices and require re-registration
  • Isolate the user’s workstation — disconnect from the network for forensic imaging

What NOT to Do

ActionWhy It’s Dangerous
Confront the user immediately (malicious)May trigger data destruction or escalation. Legal and HR must be involved first.
Assume every insider threat is maliciousNegligent and compromised insiders need different responses.
Fire the user before forensic preservationTermination without evidence preservation destroys the case.
Notify the user’s teamWord spreads quickly, potentially alerting the user or destroying the investigation.
Restore from backup without investigationDestroys evidence of the compromise timeline.

Phase 2: Evidence Preservation (30-60 minutes)

Evidence Collection by Type

EvidenceMalicious InsiderNegligent InsiderCompromised Insider
User workstation memory✅ Critical — contains active sessions, encryption keys❌ Not needed✅ Critical
File server access logs✅ Critical — shows data accessed✅ Helpful✅ Critical
Email and collaboration logs✅ Shows data exfiltration attempts✅ Shows policy violations✅ Shows attacker communication
Web proxy logs✅ Shows data upload destinations✅ Shows shadow IT✅ Shows C2 or data exfiltration
VPN and remote access logs✅ Helps determine scope❌ Not needed✅ Critical
Badge access logs✅ Correlates physical presence with digital activity❌ Not needed❌ Not needed
HR records✅ Performance, complaints, resignation notice✅ Policy violation history❌ Not needed
DLP alerts✅ Shows data exfiltration paths❌ Usually not applicable✅ Shows data exfiltration

Forensic Acquisition Priority for Malicious Insider

  1. Memory capture (most volatile) — dumpit.exe or winpmem
  2. Process and network statenetstat -ano, tasklist /v
  3. Disk image — forensic image, not a file copy. Use dd or FTK Imager
  4. Cloud data — preserve the user’s OneDrive, SharePoint, and email via legal hold

Phase 3: Investigation (1-4 hours)

Questions to Answer

QuestionEvidence SourceHow to Determine
What data was accessed?File server logs, DLP alerts, web proxyList every file accessed, downloaded, or uploaded during the suspicious window
Who else was involved?Communication logs, badge access, emailWere there colluders? Did the user communicate with anyone else about the data?
Where was the data sent?Web proxy, email logs, USB logs, cloud storage logsExternal destination IPs, cloud providers, email recipients
Was data deleted?File audit logs, volume shadow copy, backup logsCheck deletion events, shadow copy deletion, backup integrity
When did the behavior start?All logsBuild a timeline — one week of data staging looks different from one day
Is the data recoverable?Backup logs, DLP quarantineCan the exfiltrated data be recovered via backup, DLP quarantine, or legal action?

Timeline Reconstruction

SPL query — build activity timeline for a specific user:

index=* UserName="target_user"
| eval EventType = case(
    EventCode==4624, "Logon",
    EventCode==4648, "Logon with explicit creds",
    EventCode==4663, "File access",
    EventCode==5140, "Share access",
    match(source, "DLP"), "DLP alert",
    1=1, "Other"
)
| table _time, EventType, ComputerName, ObjectName, AccessMask
| sort _time

Phase 4: Response Actions (4-8 hours)

Malicious Insider — Response

ActionDetailOwner
HR notificationInform HR — they guide the disciplinary processSOC lead → HR
Legal notificationLegal handles evidence preservation, law enforcement contact, and civil actionHR → Legal
Account disablementDisable the user’s AD account, revoke all accessSOC
Data recoveryRecover exfiltrated data from DLP quarantine or backupIR team
Impact assessmentIdentify all systems and data the user accessedIR team
Access reviewReview and revoke any privileges the user granted to othersSOC
Policy reviewIdentify controls that failed to prevent the incidentSecurity team

Negligent Insider — Response

ActionDetailOwner
Manager notificationInform manager — they handle the coaching/disciplineSOC → HR → Manager
Password resetRequire password change and MFA re-enrollmentSOC
RetrainingAssign targeted security trainingHR / Security awareness
Access restrictionsRestrict access to sensitive data until training is completeSOC
Policy reviewIdentify if unclear policies contributed to the negligenceSecurity team

Compromised Insider — Follow Credential Theft Response

If the insider was compromised (credentials stolen), follow the credential theft incident response playbook. The user is a victim, not the attacker.


Phase 5: Hardening and Prevention

ControlWhat It PreventsImplementation
User and Entity Behavior Analytics (UEBA)Early detection of anomalous behaviorSIEM-based UEBA module (Sentinel, Splunk UBA)
DLP with user monitoringData exfiltration detectionEndpoint DLP + network DLP + cloud DLP
Least privilegeReduces malicious insider blast radiusRegular access reviews, JIT (Just-In-Time) access
Separation of dutiesPrevents one person from controlling sensitive functionsDual-approval for data access, admin actions
Data classificationIdentifies which data to protectMicrosoft Purview, Boldon James, Titus
Watermarking/screen captureDeters data theft via screenshotsEndpoint DLP with screen capture detection
Insider risk programStructured program for insider threat lifecycleDedicated team or cross-functional working group

Sources