Google Cloud: Service Account Disabled or Deleted via IAM Audit Events

Identifies GCP IAM audit events where service accounts are disabled or deleted via serviceAccounts.disable/delete.

FreeReviewedSigma · Medium · v4
Product
gcp
Service
gcp.audit
Author
Austin Songer @austinsonger (SigmaHQ), DRL 1.1
Published
2021-08-14
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 Google Cloud IAM service account disablement or deletion actions by matching audit method names that end with .serviceAccounts.disable and .serviceAccounts.delete. Attackers may disable or remove service accounts to break access paths or to cover tracks after gaining control. The detection relies on GCP audit log telemetry that records the IAM method name for these account lifecycle changes.

Related detections9 linkedT1531 — drag to rearrange
Malicious Mass Device Wipe via Intune Remote Actions (via m365)
Suspicious Account Disable via net user active no (via process_creation)
AWS IAM SAML Provider Deletion via CloudTrail
Linux userdel Execution: User Account Deletion via userdel
Linux groupdel Executed to Delete a User Group
Windows Security Logoff Events (Event ID 4634/4647)
Windows PowerShell Script: Remove Account From Domain Admin Group via Remove-ADGroupMember
Okta User Account Lockout Triggered by Max Sign-In Attempts
Azure Kubernetes Service Service Account Modified or Deleted Activity Log Events
Google Cloud: Service Account Disabled or Deleted via IAM Audit Events
Pivot detection · T1531 · 9 related

Changelog

v4
  1. v4
    Candidate ingested via manual entry.2026-07-31
  2. v3
    Candidate ingested via manual entry.2026-07-31
  3. v2
    Candidate ingested via manual entry.2026-07-31
  4. 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.