Detection rules › Kusto

Cisco Duo - AD sync failed

Status
available
Severity
medium
Time window
1h
Source
github.com/Azure/Azure-Sentinel

'Detects when AD syncronization failed.'

MITRE ATT&CK coverage

TacticTechniques
ImpactT1489 Service Stop

Rule body kusto

id: 398dd1cd-3251-49d8-b927-5b93bae4a094
name: Cisco Duo - AD sync failed
description: |
  'Detects when AD syncronization failed.'
severity: Medium
status: Available
requiredDataConnectors:
  - connectorId: CiscoDuoSecurity
    dataTypes:
      - CiscoDuo
queryFrequency: 1h
queryPeriod: 1h
triggerOperator: gt
triggerThreshold: 0
tactics:
  - Impact
relevantTechniques:
  - T1489
query: |
  CiscoDuo
  | where DvcAction =~ "ad_sync_failed"
  | extend IPCustomEntity = SrcIpAddr
entityMappings:
  - entityType: IP
    fieldMappings:
      - identifier: Address
        columnName: IPCustomEntity
version: 1.0.0
kind: Scheduled

Stages and Predicates

Stage 1: source

CiscoDuo

Stage 2: where

| where DvcAction =~ "ad_sync_failed"

Stage 3: 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.

FieldKindValues
DvcActioneq
  • ad_sync_failed

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
IPCustomEntityextend