detection.wiki

Detection rules › Kusto

Cisco Duo - Admin user created

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

'Detects when new admin user is created.'

MITRE ATT&CK coverage

TacticTechniques
PersistenceT1078 Valid Accounts
Privilege EscalationT1078 Valid Accounts

Rule body kusto

id: 0724cb01-4866-483d-a149-eb400fe1daa8
name: Cisco Duo - Admin user created
description: |
  'Detects when new admin user is created.'
severity: Medium
status: Available
requiredDataConnectors:
  - connectorId: CiscoDuoSecurity
    dataTypes:
      - CiscoDuo
queryFrequency: 1h
queryPeriod: 1h
triggerOperator: gt
triggerThreshold: 0
tactics:
  - Persistence
  - PrivilegeEscalation
relevantTechniques:
  - T1078
query: |
  CiscoDuo
  | where DvcAction =~ "admin_create"
  | extend AccountCustomEntity = DstUserName
entityMappings:
  - entityType: Account
    fieldMappings:
      - identifier: Name
        columnName: AccountCustomEntity
version: 1.0.0
kind: Scheduled

Stages and Predicates

Stage 1: source

CiscoDuo

Stage 2: where

| where DvcAction =~ "admin_create"

Stage 3: 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
DvcActioneq
  • admin_create

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
AccountCustomEntityextend