Detection rules › Kusto
Ping Federate - OAuth old version
'Detects requests using not the latest version of OAuth protocol.'
MITRE ATT&CK coverage
| Tactic | Techniques |
|---|---|
| Initial Access | T1190 Exploit Public-Facing Application |
Rule body kusto
id: 85f70197-4865-4635-a4b2-a9c57e8fea1b
name: Ping Federate - OAuth old version
description: |
'Detects requests using not the latest version of OAuth protocol.'
severity: Medium
status: Available
requiredDataConnectors:
- connectorId: CefAma
dataTypes:
- CommonSecurityLog
queryFrequency: 1d
queryPeriod: 1d
triggerOperator: gt
triggerThreshold: 0
tactics:
- InitialAccess
relevantTechniques:
- T1190
query: |
PingFederateEvent
| where isnotempty(DeviceCustomString3)
| extend proto = extract(@'(OAuth)', 1, DeviceCustomString3)
| extend ver = extract(@'(\d+)', 1, DeviceCustomString3)
| where proto =~ 'OAuth'
| where ver !~ '20'
| 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
Stage 1: source
PingFederateEvent
Stage 2: where
| where isnotempty(DeviceCustomString3)
Stage 3: extend
| extend proto = extract(@'(OAuth)', 1, DeviceCustomString3)
Stage 4: extend
| extend ver = extract(@'(\d+)', 1, DeviceCustomString3)
Stage 5: where
| where proto =~ 'OAuth'
Stage 6: where
| where ver !~ '20'
Stage 7: extend
| extend AccountCustomEntity = DstUserName
Stage 8: 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 |
|---|---|---|
DeviceCustomString3 | is_not_null | |
proto | eq |
|
ver | ne |
|
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 |
|---|---|
proto | extend |
ver | extend |
AccountCustomEntity | extend |
IpCustomEntity | extend |