Azure Activity Logs: Container Registry Created or Deleted

Flags Azure Activity Log events where an Azure Container Registry is created (write) or deleted.

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

ATT&CK techniques

Impact
  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

What it detects

This rule flags Azure Activity Log events where a Container Registry is created or deleted. Such changes can impact where container images are stored and retrieved, making them a relevant signal for persistence and disruption attempts. It relies on activity log records containing operationName values for Microsoft.ContainerRegistry/registries WRITE and DELETE.

Related detections9 linkedT1485 — drag to rearrange
Azure Activity Logs: Kubernetes Network Policy Write/Delete Changes
Azure Kubernetes Service Service Account Modified or Deleted Activity Log Events
Azure Kubernetes RBAC RoleBinding/ClusterRoleBinding Written or Deleted
Azure Kubernetes Activity Logs: Write/Delete of ConfigMaps or Secrets
Azure Activity Logs: Kubernetes ClusterRole/Role Write, Delete, Bind, or Escalate Changes
Azure Activity Logs: Azure Kubernetes Connected Cluster Created or Deleted
Malicious PathWiper Loader Script Execution from Windows Temp via WScript
Suspicious Free Space Wipe via cipher.exe
Suspicious sha256sum.exe Execution from Windows Temp Directory
Azure Activity Logs: Container Registry Created or Deleted
Pivot detection · T1485 · 9 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.