Azure Firewall Rule Collection Modified or Deleted via Activity Logs

Alerts on Azure Firewall rule collection write or delete operations for Application, NAT, or Network components.

FreeReviewedSigma · Medium · v5
Product
azure
Service
activitylogs
Author
Austin Songer @austinsonger (SigmaHQ), DRL 1.1
Published
2021-08-08
Updated
2026-07-31

ATT&CK techniques

  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. C2

  13. Exfiltration

  14. Impact

What it detects

This rule identifies Azure Firewall changes where rule collections are written to or deleted, covering Application, NAT, and Network rule collections. Such activity can directly alter traffic filtering behavior, enabling attackers or misconfigurations to redirect or disrupt network access. The detection relies on Azure Activity Log events that record operationName values for WRITE and DELETE actions on these specific rule collection resources.

Related detections7 linkedT1686.001 — drag to rearrange
AWS CloudTrail: S3 Block Public Access disabled via PutBucketPublicAccessBlock
Suspicious Azure Network Security Group Rule Opening Inbound Access to the Internet
Suspicious Security Group Ingress Rule Opened to the Internet via CloudTrail
AWS CloudTrail: CreateRoute Adds New Network Route to a Route Table
AWS CloudTrail: CreateNetworkAclEntry Adds Network ACL Rules
Azure Network Firewall Policy Modified or Deleted via Activity Logs
Azure Firewall Created, Modified, or Deleted via Activity Log
Azure Firewall Rule Collection Modified or Deleted via Activity Logs
Pivot detection · T1686.001 · 7 related

Changelog

v5
  1. v5
    Candidate ingested via manual entry.2026-07-31
  2. v4
    Candidate ingested via manual entry.2026-07-31
  3. v3
    Candidate ingested via manual entry.2026-07-31
  4. v2
    Candidate ingested via manual entry.2026-07-31
  5. v1
    No changelog recorded for this version.2026-07-30

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.