Detection rules › Kusto
Netskope - High Severity Alert
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.
MITRE ATT&CK coverage
| Tactic | Techniques |
|---|---|
| Initial Access | |
| Exfiltration |
Rule body
id: a1f6c2d4-8b35-4e19-9c7a-2d4e6f8a1b30
name: Netskope - High Severity Alert
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.
severity: High
status: Available
requiredDataConnectors:
- connectorId: NetskopeAlertEventsConnector
dataTypes:
- NetskopeAlertEvents_CL
queryFrequency: 1h
queryPeriod: 1h
triggerOperator: gt
triggerThreshold: 0
tactics:
- InitialAccess
- Exfiltration
relevantTechniques:
- T1078
- T1567
query: |
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
entityMappings:
- entityType: Account
fieldMappings:
- identifier: Name
columnName: User
- entityType: IP
fieldMappings:
- identifier: Address
columnName: Userip
- entityType: Host
fieldMappings:
- identifier: HostName
columnName: Hostname
version: 1.0.0
kind: Scheduled
Stages and Predicates
Stage 1: source
NetskopeAlertEvents_CL
Stage 2: where
| where TimeGenerated > ago(1h)
Stage 3: where
| where Alert =~ "yes"
Stage 4: where
| where Severity in~ ("high", "critical")
Stage 5: extend
| extend NormalizedSeverity = tolower(Severity)
Stage 6: summarize
| 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
Stage 7: sort
| order by AlertCount desc
Stage 8: project
| project
LastSeen,
AlertName,
AlertType,
Severity = NormalizedSeverity,
User,
Userip,
Hostname,
SrcCountry,
AlertCount,
Applications,
Activities,
Policies,
Actions,
FirstSeen
Indicators
These rows show field, operator, and value matches.
| Field | Kind | Values | Search |
|---|---|---|---|
Alert | eq |
| field:"Alert" kind:eq value:"yes" |
Severity | in |
| field:"Severity" kind:in |
Output fields
These fields are emitted when the rule matches.
| Field | Source |
|---|---|
Actions | project |
Activities | project |
AlertCount | project |
AlertName | project |
AlertType | project |
Applications | project |
FirstSeen | project |
Hostname | project |
LastSeen | project |
Policies | project |
Severity | project |
SrcCountry | project |
User | project |
Userip | project |