Detection rules › Kusto

Illumio Firewall Tampering Analytic Rule

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

'Create Microsoft Sentinel Incident When Firewall Is Tampered With'

MITRE ATT&CK coverage

TacticTechniques
StealthT1562 Impair Defenses

Rule body kusto

id: e9e4e466-3970-4165-bc8d-7721c6ef34a6
name: Illumio Firewall Tampering Analytic Rule
description: |
  'Create Microsoft Sentinel Incident When Firewall Is Tampered With'
severity: Medium
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 'tampering'
  | extend ipaddress = action.src_ip,
            hostname = created_by.agent.hostname,
            ven_href = created_by.ven.href
  | project-away resource_changes, action, version
eventGroupingSettings:
  aggregationKind: SingleAlert
entityMappings:
  - entityType: Host
    fieldMappings:
      - identifier: HostName
        columnName: hostname
  - entityType: IP
    fieldMappings:
      - identifier: Address
        columnName: ipaddress          
alertDetailsOverride:
  alertDisplayNameFormat: | 
    Illumio Firewall Tamper Incident for {{hostname}}
  alertDescriptionFormat: | 
    Illumio Firewall Tamper Incident for {{hostname}} generated at {{TimeGenerated}}
version: 1.0.7
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 'tampering'

Stage 5: extend

| extend ipaddress = action.src_ip,
           hostname = created_by.agent.hostname,
           ven_href = created_by.ven.href

Stage 6: project-away

| project-away resource_changes, action, version

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
event_typematch
  • tampering transforms: term

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
hostnameextend
ipaddressextend
ven_hrefextend