Description
Detects a spike in Netskope DLP incidents within a short window. A sudden increase in
DLP violations for a single user or DLP profile can indicate active data exfiltration,
a misconfigured policy, or bulk handling of sensitive data. Triggers when a user
generates more DLP incidents in the last hour than a configurable threshold.
- Rule type
- Scheduled
- Version
- 1.0.0
- Declared status
- Available
- Query frequency
- 1h
- Query period
- 1h
- Trigger
- gt 0
Declared MITRE coverage
Declared sources
Metadata from the source file. No dependencies inferred from KQL.
Connectors
Data types
KQL query
Original query, unchanged.
let dlpIncidentThreshold = 10;
NetskopeAlertEvents_CL
| where TimeGenerated > ago(1h)
| where AlertType =~ "DLP" or isnotempty(DlpProfile) or isnotempty(DlpIncidentId)
| summarize
IncidentCount = count(),
DistinctIncidents = dcount(DlpIncidentId),
Profiles = make_set(DlpProfile, 20),
Rules = make_set(DlpRule, 20),
Applications = make_set(App, 20),
Files = make_set(DlpFile, 20),
Activities = make_set(Activity, 10),
Actions = make_set(Action, 10),
FirstSeen = min(TimeGenerated),
LastSeen = max(TimeGenerated)
by User, Userip, Hostname
| where IncidentCount > dlpIncidentThreshold
| order by IncidentCount desc
| project
LastSeen,
User,
Userip,
Hostname,
IncidentCount,
DistinctIncidents,
Profiles,
Rules,
Applications,
Files,
Activities,
Actions,
FirstSeen
Declared entities
Related content
Links established from declared identifiers and solution manifests.
Source provenance
GitHubDisplayed values come from files in Azure/Azure-Sentinel. They describe the published template, not your workspace configuration.
- Commit
9800e51↗- Source identifier
c3f8e4d6-0d57-4a3b-9e2c-4f6a8b0d3e52
GSTEP / CATALOG TRACKING
Added to catalog : 16 Sept 2026 · 05:49 UTC
Last change observed : 16 Sept 2026 · 05:49 UTC