Detection rules › Kusto
Hypervisor Host Deleted
Detects when a hypervisor host is deleted from Veeam Backup & Replication. This might indicate unauthorized changes to the virtualization environment.
Rule body kusto
id: 4e41c85f-d495-4a23-a218-41b938140dce
name: Hypervisor Host Deleted
description: Detects when a hypervisor host is deleted from Veeam Backup & Replication.
This might indicate unauthorized changes to the virtualization environment.
severity: Informational
status: Available
requiredDataConnectors:
- connectorId: Syslog
dataTypes:
- Syslog
- connectorId: SyslogAma
dataTypes:
- Syslog
queryFrequency: 1d
queryPeriod: 1d
triggerOperator: gt
triggerThreshold: 0
eventGroupingSettings:
aggregationKind: AlertPerResult
tactics: []
relevantTechniques: []
query: "Veeam_GetSecurityEvents\n| where instanceId == 24070 \n| project\n Date\
\ = format_datetime(TimeGenerated, 'dd.MM.yyyy HH:mm'),\n [\"DataSource\"] =\
\ original_host,\n EventId = instanceId,\n UserName = user,\n [\"MessageDetails\"\
] = Description,\n Severity = SeverityDescription"
entityMappings:
- entityType: Host
fieldMappings:
- identifier: FullName
columnName: DataSource
version: 1.0.1
kind: Scheduled
customDetails:
messageDetails: MessageDetails
Stages and Predicates
Stage 1: source
Veeam_GetSecurityEvents
Stage 2: where
| where instanceId == 24070
Stage 3: project
| project
Date = format_datetime(TimeGenerated, 'dd.MM.yyyy HH:mm'),
["DataSource"] = original_host,
EventId = instanceId,
UserName = user,
["MessageDetails"] = Description,
Severity = SeverityDescription
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 |
|---|---|---|
instanceId | eq |
|
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 |
|---|---|
DataSource | project |
Date | project |
EventId | project |
MessageDetails | project |
Severity | project |
UserName | project |