Law enforcement contact decision tree
Overview
When to call law enforcement depends on jurisdiction, sector, data types, and ransom dynamics—legal counsel approves contact framing.
Triggers to consider notification
- Critical infrastructure, regulated PHI/financial data, terrorism/nation-state attribution hints, physical threat, extortion with law enforcement interest.
- Insurance policy may require timely report to FBI/Cyber portal—verify wording.
Before dialing
- Preserve logs and timelines; avoid destroying evidence during panic rebuilds.
- Single narrative contact person—usually general counsel or outside counsel.
Process
- Local vs federal path varies; document case number received.
- Do not promise employees confidentiality that conflicts with legal duty to cooperate—HR + counsel wording.
International
GDPR or foreign data may restrict what you share—DPA review.
MSP role
Facilitate technical facts, attend bridged calls if contracted; do not make legal admissions on client’s behalf.
After
Update IR plan with lessons from agency interaction—some cases move slowly; manage executive expectations.
Related Articles
EDR deployment checklist for new workstations
## Overview Use this runbook when onboarding a new Windows workstation or re-imaging a device that...
Handling Defender for Business false positives
## Overview False positives waste analyst time and train users to ignore alerts. This article stand...
Application allowlisting with Windows Defender ASR rules
## Overview Attack Surface Reduction (ASR) rules reduce exploit surface by constraining Office macr...