What the demonstration did
Research demonstration / Orca Security
- 1
Sandbox identity isolation
December 2021Orca observes another tenant’s managed identity token from an Azure Automation sandbox.
- 2
Identity authorization
December 2021In its own account, Orca verifies that a managed identity without a suitable role cannot read the test resources.
Impact
Orca obtained tokens associated with other tenants. Their possible reach depended on each managed identity’s assigned permissions. The research does not establish access to another tenant’s data.
Would the controls have stopped it?
The sandbox must issue each job only its own identity
Microsoft corrected token isolation in Azure Automation. Owners can limit each automation identity to the resources its jobs need, reducing what a disclosed token could authorize.
Incident control assessments
- 0
- Prevented
- 0
- Contained
- 2
- Not covered
How it could have been prevented
The same replay with the controls in place. Green marks where a step is refused, blue where it is bounded, and red where no control reaches it. Open a row to read the control, why it acts, and its caveat.
Research demonstration / Orca Security
1 · Sandbox identity isolation
1 Not covered2 · Identity authorization
1 Not coveredKey facts
- Orca reported the Azure Automation sandbox isolation issue on December 6, 2021.
- The researchers observed managed identity tokens associated with multiple tenants.
- Orca tested the effect of role assignments using its own identity and did not need to access other tenants’ data.
- Microsoft fixed the service on December 10, 2021.
- Orca published the results on March 7, 2022 after Microsoft concluded its investigation.
- Microsoft detected no evidence of token misuse. Managed identities on Azure Sandbox jobs were exposed. Hybrid Worker execution and Run As accounts were outside the reported scope.
Sources
Every fact in this breakdown comes from the public reporting below. The replay is a model of that reporting, not a reconstruction of the environment it describes.
- 1.AutoWarp: Azure Automation VulnerabilityOrca Security · Mar 7, 2022 · ResearchOrca obtained tokens associated with other tenants. Their possible reach depended on each managed identity’s assigned permissions. The research does not establish access to another tenant’s data.
- 2.Security best practices in Azure AutomationMicrosoft · undated · Vendor reportMicrosoft’s Automation guidance covers managed identities and restricting the permissions granted to automation accounts.
- 3.Disclosure of Vulnerability in Azure Automation Managed Identity TokensMicrosoft Security Response Center · Mar 7, 2022 · AdvisoryMicrosoft detected no evidence of token misuse. Managed identities on Azure Sandbox jobs were exposed. Hybrid Worker execution and Run As accounts were outside the reported scope.
The estate in the replay follows the researchers' description of their own test environment. Verdicts describe what a control does when it is in place before the run. They are not an assessment of any company's security program.