Azure Kubernetes Service Service Account Modified or Deleted Activity Log Events

Alerts on Azure Activity Log events where a Kubernetes service account is written, deleted, or impersonated.

FreeReviewedSigma · Medium · 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 identifies Azure activity log events where a Kubernetes connected cluster service account is written, deleted, or impersonated. Such changes matter because attackers with sufficient permissions can alter service account privileges, remove access, or perform actions via impersonation. The detection relies on Azure Activity Logs fields that record the Kubernetes service account operation names for write, delete, and impersonate actions.

Related detections9 linkedT1485 — drag to rearrange
Azure Activity Logs: Kubernetes Network Policy Write/Delete Changes
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: Container Registry Created or Deleted
Azure Activity Logs: Azure Kubernetes Connected Cluster Created or Deleted
Malicious Mass Device Wipe via Intune Remote Actions (via m365)
Malicious Cryptocurrency Miner Execution via XMRig and c3pool (via process_creation)
Suspicious Self-Deleting Batch Script Execution Consistent with Agonizing Serpens Wiper Cleanup
Azure Kubernetes Service Service Account Modified or Deleted Activity Log Events
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.