Azure enumeration
Enumerating Azure services
Common misconfigurations
Or, what Microsoft refers to as default.
Azure is by default open to every user in the organization. That means clients who for instance have Office 365 most likely haven't set up a conditional access policy to prevent users from logging in to portal.azure.com and retrieving every user, role and group. Odds are that if they haven't done that, they don't monitor what the users do there to closely either. So why ask the on-premise domain controller and get detected if you can get what you need right from Azure? Procedures for doing the magic with Powershell below.
Procedures and tools
Useful articles
Tools
https://github.com/mwrlabs/Azurite - Azurite was developed to assist penetration testers and auditors during the enumeration and reconnaisance activities within the Microsof Azure public Cloud environment.
https://github.com/nccgroup/azucar - Azucar automatically gathers a variety of configuration data and analyses all data relating to a particular subscription in order to determine security risks.
https://github.com/NetSPI/MicroBurst - MicroBurst includes functions and scripts that support Azure Services discovery, weak configuration auditing, and post exploitation actions such as credential dumping. It is intended to be used during penetration tests where Azure is in use.
https://github.com/chrismaddalena/SharpCloud - SharpCloud is a simple C# utility for checking for the existence of credential files related to Amazon Web Services, Microsoft Azure, and Google Compute.
Procedures
A little code block with some common procedures for enumerating Azure AD.
Last updated