Detection rules › Kusto

Ping Federate - Abnormal password reset attempts

Status
available
Severity
high
Time window
30m
Group by
DstUserName
Source
github.com/Azure/Azure-Sentinel

'Detects abnormal password reset attempts for user in short period of time.'

MITRE ATT&CK coverage

TacticTechniques
Credential AccessT1110 Brute Force

Rule body kusto

id: e45a7334-2cb4-4690-8156-f02cac73d584
name: Ping Federate - Abnormal password reset attempts
description: |
  'Detects abnormal password reset attempts for user in short period of time.'
severity: High
status: Available
requiredDataConnectors:
  - connectorId: CefAma
    dataTypes:
      - CommonSecurityLog
queryFrequency: 1d
queryPeriod: 1d
triggerOperator: gt
triggerThreshold: 0
tactics:
  - CredentialAccess
relevantTechniques:
  - T1110
query: |
  let threshold = 10;
  PingFederateEvent
  | where EventType =~ 'PWD_RESET_REQUEST'
  | summarize count() by DstUserName, bin(TimeGenerated, 30m)
  | where count_ > threshold
  | extend AccountCustomEntity = DstUserName
entityMappings:
  - entityType: Account
    fieldMappings:
      - identifier: Name
        columnName: AccountCustomEntity
version: 1.0.3
kind: Scheduled

Stages and Predicates

Parameters

let threshold = 10;

Stage 1: source

PingFederateEvent

Stage 2: where

| where EventType =~ 'PWD_RESET_REQUEST'

Stage 3: summarize

| summarize count() by DstUserName, bin(TimeGenerated, 30m)

Stage 4: where

| where count_ > threshold

Stage 5: extend

| extend 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.

FieldKindValues
EventTypeeq
  • PWD_RESET_REQUEST
count_gt
  • 10 transforms: cased

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.

FieldSource
DstUserNamesummarize
AccountCustomEntityextend