Detection rules › Kusto
PaloAlto - Forbidden countries
'Detects suspicious connections from forbidden countries.'
MITRE ATT&CK coverage
| Tactic | Techniques |
|---|---|
| Initial Access | T1133 External Remote Services, T1190 Exploit Public-Facing Application |
Rule body kusto
id: 9fcc7734-4d1b-11ec-81d3-0242ac130003
name: PaloAlto - Forbidden countries
description: |
'Detects suspicious connections from forbidden countries.'
severity: Medium
status: Available
requiredDataConnectors:
- connectorId: CefAma
dataTypes:
- CommonSecurityLog
queryFrequency: 1h
queryPeriod: 1h
triggerOperator: gt
triggerThreshold: 0
tactics:
- InitialAccess
relevantTechniques:
- T1190
- T1133
query: |
let bl_countries = dynamic(['CH', 'RU']);
PaloAltoCDLEvent
| where EventResourceId =~ 'TRAFFIC'
| where MaliciousIPCountry in (bl_countries)
| summarize count() by DstUsername, SrcIpAddr
| extend IPCustomEntity = SrcIpAddr, AccountCustomEntity = DstUsername
entityMappings:
- entityType: Account
fieldMappings:
- identifier: Name
columnName: AccountCustomEntity
- entityType: IP
fieldMappings:
- identifier: Address
columnName: IPCustomEntity
version: 1.0.4
kind: Scheduled
Stages and Predicates
Parameters
let bl_countries = dynamic(['CH', 'RU']);
Stage 1: source
PaloAltoCDLEvent
Stage 2: where
| where EventResourceId =~ 'TRAFFIC'
Stage 3: where
| where MaliciousIPCountry in (bl_countries)
Stage 4: summarize
| summarize count() by DstUsername, SrcIpAddr
Stage 5: extend
| extend IPCustomEntity = SrcIpAddr, AccountCustomEntity = DstUsername
Indicators
Each row is a field, operator, and value that the rule matches. The corpus column counts how many other rules in the catalog look for the same combination: high numbers point to widely-used, community-vetted indicators. Blank or 1 shows that the indicator is specific to this rule.
| Field | Kind | Values |
|---|---|---|
EventResourceId | eq |
|
MaliciousIPCountry | in |
|
Output fields
Fields the rule emits when it matches. Chronicle authors list these in the outcome block; they appear on the detection and $risk_score drives alerting. Sentinel / Defender XDR rules build them up through project / summarize / extend stages. Sentinel maps these into alert fields via entityMappings and customDetails; Defender XDR custom detections surface them as alert fields directly.
| Field | Source |
|---|---|
DstUsername | summarize |
SrcIpAddr | summarize |
AccountCustomEntity | extend |
IPCustomEntity | extend |