Detection rules › Kusto
Ping Federate - Forbidden country
'Detects requests from forbidden countries.'
MITRE ATT&CK coverage
| Tactic | Techniques |
|---|---|
| Initial Access | T1078 Valid Accounts |
Rule body kusto
id: 14042f74-e50b-4c21-8a01-0faf4915ada4
name: Ping Federate - Forbidden country
description: |
'Detects requests from forbidden countries.'
severity: High
status: Available
requiredDataConnectors:
- connectorId: CefAma
dataTypes:
- CommonSecurityLog
queryFrequency: 1h
queryPeriod: 1h
triggerOperator: gt
triggerThreshold: 0
tactics:
- InitialAccess
relevantTechniques:
- T1078
query: |
let forbidden_geo = dynamic(['CH']);
PingFederateEvent
| where isnotempty(DstGeoCountry)
| where tostring(DstGeoCountry) in~ (forbidden_geo)
| extend AccountCustomEntity = DstUserName
| extend IpCustomEntity = SrcIpAddr
entityMappings:
- entityType: Account
fieldMappings:
- identifier: Name
columnName: AccountCustomEntity
- entityType: IP
fieldMappings:
- identifier: Address
columnName: IpCustomEntity
version: 1.0.3
kind: Scheduled
Stages and Predicates
Parameters
let forbidden_geo = dynamic(['CH']);
Stage 1: source
PingFederateEvent
Stage 2: where
| where isnotempty(DstGeoCountry)
Stage 3: where
| where tostring(DstGeoCountry) in~ (forbidden_geo)
Stage 4: extend
| extend AccountCustomEntity = DstUserName
Stage 5: extend
| extend IpCustomEntity = SrcIpAddr
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 |
|---|---|---|
DstGeoCountry | in |
|
DstGeoCountry | is_not_null |
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 |
|---|---|
AccountCustomEntity | extend |
IpCustomEntity | extend |