Detection rules › Kusto
Illumio VEN Clone Detection Rule
'Create Microsoft Sentinel Incident When A Cloned Ven Is Detected'
MITRE ATT&CK coverage
| Tactic | Techniques |
|---|---|
| Stealth | T1562 Impair Defenses |
Rule body kusto
id: b3c4b8f4-c12c-471e-9999-023c05852276
name: Illumio VEN Clone Detection Rule
description: |
'Create Microsoft Sentinel Incident When A Cloned Ven Is Detected'
severity: High
status: Available
requiredDataConnectors:
- connectorId: IllumioSaaSDataConnector
dataTypes:
- Illumio_Auditable_Events_CL
- connectorId: SyslogAma
datatypes:
- Syslog
queryFrequency: 60m
queryPeriod: 60m
triggerOperator: gt
triggerThreshold: 0
tactics:
- DefenseEvasion
relevantTechniques:
- T1562
query: |
Illumio_Auditable_Events_CL
| union IllumioSyslogAuditEvents
| where event_type has 'agent.clone_detected'
| extend hostname = created_by.agent.hostname,
ven_href = created_by.ven.href
eventGroupingSettings:
aggregationKind: SingleAlert
entityMappings:
- entityType: Host
fieldMappings:
- identifier: HostName
columnName: hostname
alertDetailsOverride:
alertDisplayNameFormat: |
Illumio VEN Clone Detection Incident for {{hostname}}
alertDescriptionFormat: |
Illumio VEN Clone Detection for {{hostname}} generated at {{TimeGenerated}}
version: 1.0.6
kind: Scheduled
Stages and Predicates
Stage 1: source
Illumio_Auditable_Events_CL
Stage 2: union
| union
Stage 3: source
IllumioSyslogAuditEvents
Stage 4: where
| where event_type has 'agent.clone_detected'
Stage 5: extend
| extend hostname = created_by.agent.hostname,
ven_href = created_by.ven.href
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 |
|---|---|---|
event_type | match |
|
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 |
|---|---|
hostname | extend |
ven_href | extend |