Suspicious Azure Key Vault Access Policy Modification

PremiumReviewedSigma · Medium · v1
Product
azure
Service
activitylogs
Author
HuntRule
Published
2026-09-14
Updated
2026-09-14

ATT&CK techniques

Persistence → Cred Access
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Defense Evasion

  6. Discovery

  7. Lateral Movement

  8. Collection

  9. C2

  10. Exfiltration

  11. Impact

What it detects

This rule detects an Azure Activity Log write operation against a Key Vault which a principal holding the Microsoft.KeyVault vaults write permission can abuse to grant itself secret key and certificate data access for privilege escalation and credential theft.

Related detections9 linkedT1552.001 — drag to rearrange
Malicious Marimo Notebook Credential File Access via Shell (via process_creation)
Malicious Keyhunter Worker Persistence via Systemd Service
Suspicious Route53 Domain Transfer Lock Disabled via Scattered Spider Technique
Suspicious Domain Admin Account Creation via net (via process_creation)
Suspicious Guest Account Privilege Escalation (via process_creation)
Suspicious TruffleHog Execution Spawned by Bun Runtime via Process Creation
Malicious AWS Credential Exfiltration via Curl or Wget in Process Creation
Suspicious Login Shell Assigned to Service Account games on Linux
Suspicious sqlite3 Access to gcloud Cached Access Token Database (via process_creation)
Suspicious Azure Key Vault Access Policy Modification
Pivot detection · T1552.001 · 9 related

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