Azure Automation Runbook Deleted
Identifies when an Azure Automation runbook is deleted. An adversary may delete an Azure Automation runbook in order to disrupt their target's automated business operations or to remove a malicious runbook for…
Description
Identifies when an Azure Automation runbook is deleted. An adversary may delete an Azure Automation runbook in order to disrupt their target's automated business operations or to remove a malicious runbook for defense evasion.
Detection logic
Its licence does not clear it for publishing here
Sunturai publishes a detection's own text where the licence it arrived under has been reviewed and permits it, and Elastic License 2.0 has not. The query as its source wrote it, its canonical form and the hash that pins this revision are in the workspace record.
Detection requirements
- Platform
- ContainersESXiIaaSLinuxmacOSWindows
The rule states no platform. This is derived from the ATT&CK technique it maps to.
- Log source category
- event_index
MITRE ATT&CK mappings
0 exclusive techniques.This is coverage no other published rule has; it is not this rule's total technique count.
References
| Reference | Cited by |
|---|---|
| azure.microsoft.com/en-in/blog/azure-automation-runbook-management/ | 3 |
| github.com/hausec/PowerZure | 4 |
| posts.specterops.io/attacking-azure-azure-ad-and-introducing-powerzure-ca70b330511a | 6 |
| powerzure.readthedocs.io/en/latest/Functions/operational.html#create-backdoor | 4 |
From the source
- At source
- Open at source
- Upstream identifier
- 8ddab73b-3d15-4e5d-9413-47f05553c1d7
- Tagged by the source as
- Data Source: AzureData Source: Azure Activity LogsDomain: CloudNoise: LowPerformance: NormalPlatform: AzureResources: Investigation GuideRule Type: Custom Query (KQL)Tactic: Defense EvasionUse Case: Configuration Audit
Licence
- Published under
- Elastic License 2.0Read the licence
- Attribution
- Required
Authorship
- Written by
- Published
- Sep 20, 2026
- Version
- 3