Azure Automation Runbook Created or Modified
Identifies when an Azure Automation runbook is created or modified. An adversary may create or modify an Azure Automation runbook to execute malicious code and maintain persistence in their target's environment.
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
- ContainersESXiIaaSLinuxmacOSNetwork DevicesOffice SuiteSaaSWindows
The rule states no platform. This is derived from the 2 ATT&CK techniques 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
- 16280f1e-57e6-4242-aa21-bb4d16f13b2f
- Tagged by the source as
- Data Source: AzureData Source: Azure Activity LogsDomain: CloudNoise: HighPerformance: NormalPlatform: AzureProfile: AggressiveResources: Investigation GuideRule Type: Custom Query (KQL)Tactic: ExecutionUse Case: Configuration Audit
Licence
- Published under
- Elastic License 2.0Read the licence
- Attribution
- Required
Authorship
- Written by
- Published
- Sep 20, 2026
- Version
- 3