Insider threats: malicious, negligent, and compromised insiders
Insider risk covers people who misuse access on purpose, make costly mistakes, or have their accounts taken over. The behavioral and technical indicators, the access controls that limit harm, and how to run an insider program fairly.
Diagram
Three kinds of insider risk
Step 1 of 4
Malicious
A departing engineer copies source code to personal storage.
DLP: 2.3 GB uploaded to personal cloud from ENG-LT-112 (user: lee) 2 days after resignation notice
The example on the open step is one illustration, or the fix you can paste into an application you own.
What this page is made of
3 pieces. Each one says what fails, who is affected, what you would notice, and what you change.
Departure window
- What fails
- Data theft often happens around resignation or termination.
- Who is affected
- The organization’s code and customer data.
- What you would notice
- Large downloads or uploads after a notice date.
- What you change
- Coordinate HR notices with security reviews of recent activity.
Access creep
- What fails
- People keep old access after changing roles.
- Who is affected
- Systems they no longer need.
- What you would notice
- Users with access from three previous roles.
- What you change
- Run access reviews and remove unused rights.
Fairness
- What fails
- Monitoring without clear policy damages trust and can break laws.
- Who is affected
- Employees.
- What you would notice
- Monitoring nobody was told about.
- What you change
- Publish the policy, involve legal and HR, and limit who sees results.
Indicators worth combining
No single signal proves intent. Programs look for combinations.
- Resignation or performance issues plus unusual downloads
- Access to systems outside the person’s role
- Disabling security tools or using unapproved storage
- Working at unusual hours combined with bulk data access
Further guidance
CISA’s Insider Threat Mitigation Guide and the CERT National Insider Threat Center publish program frameworks and case studies.
Check yourself
Recognition and the fix. Nothing here is a procedure.
An employee uploads 2 GB to personal cloud storage two days after resigning. What should happen?
Sibling techniques
Pages at the same depth, plus a lab and a glossary card for this one.