Description
Detects Netskope alerts raised with a high or critical severity. High severity alerts
typically indicate DLP violations, malware detections, compromised credentials, or
significant policy breaches that warrant immediate investigation.
- 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.
NetskopeAlertEvents_CL
| where TimeGenerated > ago(1h)
| where Alert =~ "yes"
| where Severity in~ ("high", "critical")
| extend NormalizedSeverity = tolower(Severity)
| summarize
AlertCount = count(),
Activities = make_set(Activity, 20),
Applications = make_set(App, 20),
Policies = make_set(Policy, 20),
Actions = make_set(Action, 10),
FirstSeen = min(TimeGenerated),
LastSeen = max(TimeGenerated)
by AlertName, AlertType, NormalizedSeverity, User, Userip, Hostname, SrcCountry
| order by AlertCount desc
| project
LastSeen,
AlertName,
AlertType,
Severity = NormalizedSeverity,
User,
Userip,
Hostname,
SrcCountry,
AlertCount,
Applications,
Activities,
Policies,
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
a1f6c2d4-8b35-4e19-9c7a-2d4e6f8a1b30
GSTEP / CATALOG TRACKING
Added to catalog : 16 Sept 2026 · 05:49 UTC
Last change observed : 16 Sept 2026 · 05:49 UTC