detection.wiki

Detection rules › Kusto

vCenter - Root impersonation

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

'Detects when root impersonation occurs.'

MITRE ATT&CK coverage

TacticTechniques
Privilege EscalationT1078 Valid Accounts

Rule body kusto

id: f1fcb22c-b459-42f2-a7ee-7276b5f1309c
name: vCenter - Root impersonation
description: |
  'Detects when root impersonation occurs.'
severity: Medium
status: Available
requiredDataConnectors:
  - connectorId: CustomLogsAma
    dataTypes:
      - vcenter_CL
queryFrequency: 1h
queryPeriod: 1h
triggerOperator: gt
triggerThreshold: 0
tactics:
  - PrivilegeEscalation
relevantTechniques:
  - T1078
query: |
 vCenter
  | where Message has_all ('ImpersonateUser', 'VcIntegrity', 'root')
  | extend user = 'root'
entityMappings:
  - entityType: Account
    fieldMappings:
      - identifier: Name
        columnName: user
version: 1.0.2
kind: Scheduled

Stages and Predicates

Stage 1: source

vCenter

Stage 2: where

| where Message has_all ('ImpersonateUser', 'VcIntegrity', 'root')

Stage 3: extend

| extend user = 'root'

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
Messagematch
  • ImpersonateUser
  • VcIntegrity
  • root

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
userextend