Automation Accounts

Abusing Azure Automation Accounts: runbooks and the RunAs account for code execution as a privileged identity, plus hybrid worker reach.

1 мин четенеобновено на 7.10.2026 г.florianamette1 сътрудник
Попитайте асистента си (MCP)Редактиране в GitHub

An Automation Account runs runbooks (PowerShell or Python) under its own identity, holds credential, variable, and connection assets that are often cleartext, and can reach on-prem or VM hosts through Hybrid Runbook Workers. It is one of the highest-value targets on the Azure resource plane: a runbook is arbitrary code as a privileged identity, and the account's assets routinely store service-principal secrets.

What folds in here#

The account's stored credential assets are harvested as credentials.

References#