Az - Enumeration Tools
Tip
Učite i vežbajte AWS Hacking:
HackTricks Training AWS Red Team Expert (ARTE)
Učite i vežbajte GCP Hacking:HackTricks Training GCP Red Team Expert (GRTE)
Učite i vežbajte Azure Hacking:
HackTricks Training Azure Red Team Expert (AzRTE)
Podržite HackTricks
- Proverite planove pretplate!
- Pridružite se 💬 Discord grupi ili telegram grupi ili pratite nas na Twitteru 🐦 @hacktricks_live.
- Podelite hakerske trikove slanjem PR-ova na HackTricks i HackTricks Cloud github repozitorijume.
Instalirajte PowerShell na Linuxu
Tip
Na Linuxu ćete morati instalirati PowerShell Core:
sudo apt-get update
sudo apt-get install -y wget apt-transport-https software-properties-common
# Ubuntu 20.04
wget -q https://packages.microsoft.com/config/ubuntu/20.04/packages-microsoft-prod.deb
# Update repos
sudo apt-get update
sudo add-apt-repository universe
# Install & start powershell
sudo apt-get install -y powershell
pwsh
# Az cli
curl -sL https://aka.ms/InstallAzureCLIDeb | sudo bash
Install PowerShell in MacOS
Uputstva iz documentation:
- Instalirajte
brewako još nije instaliran:
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
- Instalirajte najnoviju stabilnu verziju PowerShell:
brew install powershell/tap/powershell
- Pokrenite PowerShell:
pwsh
- Ažuriranje:
brew update
brew upgrade powershell
Glavni alati za enumeraciju
az cli
Azure Command-Line Interface (CLI) je cross-platform alat napisan u Pythonu za upravljanje i administraciju (većine) Azure i Entra ID resursa. Povezuje se sa Azure i izvršava administrativne komande putem komandne linije ili skripti.
Pratite ovaj link za installation instructions¡.
Komande u Azure CLI su strukturisane koristeći obrazac: az <service> <action> <parameters>
Debug | MitM az cli
Korišćenjem parametra --debug moguće je videti sve zahteve koje alat az šalje:
az account management-group list --output table --debug
Da biste uradili MitM nad alatom i ručno proverili sve zahteve koje šalje, možete:
export ADAL_PYTHON_SSL_NO_VERIFY=1
export AZURE_CLI_DISABLE_CONNECTION_VERIFICATION=1
export HTTPS_PROXY="http://127.0.0.1:8080"
export HTTP_PROXY="http://127.0.0.1:8080"
# If this is not enough
# Download the certificate from Burp and convert it into .pem format
# And export the following env variable
openssl x509 -in ~/Downloads/cacert.der -inform DER -out ~/Downloads/cacert.pem -outform PEM
export REQUESTS_CA_BUNDLE=/Users/user/Downloads/cacert.pem
Ispravljanje “CA cert does not include key usage extension”
Zašto se greška javlja
Kada se Azure CLI autentifikuje, pravi HTTPS zahteve (putem MSAL → Requests → OpenSSL). Ako presrećete TLS sa Burp-om, Burp generiše “on the fly” sertifikate za sajtove kao što je login.microsoftonline.com i potpisuje ih sa Burp-ovim CA.
Na novijim stack-ovima (Python 3.13 + OpenSSL 3), validacija CA je stroža:
- A CA certificate must include Basic Constraints:
CA:TRUEand a Key Usage extension permitting certificate signing (keyCertSign, and typicallycRLSign).
Podrazumevani Burp CA (PortSwigger CA) je star i obično nema Key Usage ekstenziju, pa ga OpenSSL odbacuje čak i ako mu “verujete”.
To proizvodi greške kao što su:
CA cert does not include key usage extensionCERTIFICATE_VERIFY_FAILEDself-signed certificate in certificate chain
Dakle morate:
- Napraviti modernu CA (sa odgovarajućom Key Usage).
- Naterati Burp da je koristi za potpisivanje presretnutih sertifikata.
- Označiti tu CA kao pouzdanu u macOS-u.
- Usmeriti Azure CLI / Requests na taj CA bundle.
Korak po korak: radna konfiguracija
0) Preduslovi
- Burp pokrenut lokalno (proxy na
127.0.0.1:8080) - Azure CLI instaliran (Homebrew)
- Imate mogućnost da koristite
sudo(da biste obezbedili CA u sistemskom keychain-u)
1) Napravite Burp CA u skladu sa standardima (PEM + KEY)
Kreirajte OpenSSL konfiguracioni fajl koji eksplicitno postavlja CA ekstenzije:
mkdir -p ~/burp-ca && cd ~/burp-ca
cat > burp-ca.cnf <<'EOF'
[ req ]
default_bits = 2048
prompt = no
default_md = sha256
distinguished_name = dn
x509_extensions = v3_ca
[ dn ]
C = US
O = Burp Custom CA
CN = Burp Custom Root CA
[ v3_ca ]
basicConstraints = critical,CA:TRUE
keyUsage = critical,keyCertSign,cRLSign
subjectKeyIdentifier = hash
authorityKeyIdentifier = keyid:always,issuer
EOF
Generiši CA sertifikat + privatni ključ:
openssl req -x509 -new -nodes \
-days 3650 \
-keyout burp-ca.key \
-out burp-ca.pem \
-config burp-ca.cnf
Provera ispravnosti (MORA da se vidi Key Usage):
openssl x509 -in burp-ca.pem -noout -text | egrep -A3 "Basic Constraints|Key Usage"
Očekuje se da sadrži nešto poput:
CA:TRUEKey Usage: ... Certificate Sign, CRL Sign
2) Konvertuj u PKCS#12 (Burp import format)
Burp zahteva sertifikat + privatni ključ, najlakše kao PKCS#12:
openssl pkcs12 -export \
-out burp-ca.p12 \
-inkey burp-ca.key \
-in burp-ca.pem \
-name "Burp Custom Root CA"
Bićete upitani da unesete lozinku za izvoz (postavite neku; Burp će je zatražiti).
3) Importujte CA u Burp i restartujte Burp
U Burp-u:
- Proxy → Opcije
- Pronađite “Import / export CA certificate”
- Kliknite na “Import CA certificate”
- Odaberite PKCS#12
- Select
burp-ca.p12 - Unesite lozinku
- Restartujte Burp potpuno (važno)
Zašto restartovati? Burp može nastaviti da koristi staru CA dok se ne restartuje.
4) Označite novi CA kao pouzdan u macOS system keychain
Ovo omogućava sistemskim aplikacijama i mnogim TLS stack-ovima da prihvate ovaj CA.
sudo security add-trusted-cert \
-d -r trustRoot \
-k /Library/Keychains/System.keychain \
~/burp-ca/burp-ca.pem
(Ako više volite GUI: Keychain Access → System → Certificates → import → set “Always Trust”.)
5) Podesite promenljive okruženja za proxy
export HTTPS_PROXY="http://127.0.0.1:8080"
export HTTP_PROXY="http://127.0.0.1:8080"
6) Konfigurišite Requests/Azure CLI da veruju vašem Burp CA
Azure CLI koristi Python Requests interno; podesite oba ova:
export REQUESTS_CA_BUNDLE="$HOME/burp-ca/burp-ca.pem"
export SSL_CERT_FILE="$HOME/burp-ca/burp-ca.pem"
Napomene:
REQUESTS_CA_BUNDLEse koristi od strane Requests.SSL_CERT_FILEpomaže za druge TLS klijente i posebne slučajeve.- Obično vam nije potreban stari
ADAL_PYTHON_SSL_NO_VERIFY/AZURE_CLI_DISABLE_CONNECTION_VERIFICATIONnakon što je CA ispravna.
7) Proverite da li Burp zaista potpisuje sa vašim novim CA (kritična provera)
Ovo potvrđuje da je vaš lanac presretanja ispravan:
openssl s_client -connect login.microsoftonline.com:443 \
-proxy 127.0.0.1:8080 </dev/null 2>/dev/null \
| openssl x509 -noout -issuer
Očekivani issuer sadrži ime vaše CA, npr.:
O=Burp Custom CA, CN=Burp Custom Root CA
Ako i dalje vidite PortSwigger CA, Burp ne koristi vašu uvezenu CA → ponovo proverite uvoz i restartujte.
8) Proverite da li Python Requests radi kroz Burp
python3 - <<'EOF'
import requests
requests.get("https://login.microsoftonline.com")
print("OK")
EOF
Očekivano: OK
9) Azure CLI test
az account get-access-token --resource=https://management.azure.com/
Ako ste već prijavljeni, trebalo bi da vrati JSON sa accessToken.
Az PowerShell
Azure PowerShell je modul koji sadrži cmdlets za upravljanje Azure resursima direktno iz PowerShell komandne linije.
Follow this link for the installation instructions.
Commands in Azure PowerShell AZ Module are structured like: <Action>-Az<Service> <parameters>
Debug | MitM Az PowerShell
Korišćenjem parametra -Debug moguće je videti sve zahteve koje alat šalje:
Get-AzResourceGroup -Debug
Da biste izvršili MitM nad alatom i ručno proverili sve zahteve koje šalje, možete podesiti env promenljive HTTPS_PROXY i HTTP_PROXY u skladu sa docs.
Microsoft Graph PowerShell
Microsoft Graph PowerShell je višeplatformski SDK koji omogućava pristup svim Microsoft Graph API-ima, uključujući servise kao što su SharePoint, Exchange i Outlook, koristeći jedinstveni endpoint. Podržava PowerShell 7+, modernu autentifikaciju preko MSAL, spoljne identitete i napredne upite. Sa fokusom na pristup sa najmanje privilegija, obezbeđuje bezbedne operacije i redovno prima ažuriranja kako bi bio usklađen sa najnovijim funkcijama Microsoft Graph API-ja.
Follow this link for the installation instructions.
Commands in Microsoft Graph PowerShell are structured like: <Action>-Mg<Service> <parameters>
Debug Microsoft Graph PowerShell
Korišćenjem parametra -Debug moguće je videti sve zahteve koje alat šalje:
Get-MgUser -Debug
AzureAD Powershell
Azure Active Directory (AD) module, sada zastareo, je deo Azure PowerShell-a za upravljanje Azure AD resursima. On obezbeđuje cmdlets za zadatke kao što su upravljanje korisnicima, grupama i registracijama aplikacija u Entra ID.
Tip
Ovo je zamenjeno Microsoft Graph PowerShell-om
Pratite ovaj link za uputstva za instalaciju.
Automatizovani Recon i alati za usklađenost
turbot azure plugins
Turbot sa steampipe i powerpipe omogućava prikupljanje informacija iz Azure i Entra ID, izvođenje provera usklađenosti i pronalaženje pogrešnih konfiguracija. Trenutno najpreporučljiviji Azure moduli za pokretanje su:
- https://github.com/turbot/steampipe-mod-azure-compliance
- https://github.com/turbot/steampipe-mod-azure-insights
- https://github.com/turbot/steampipe-mod-azuread-insights
# Install
brew install turbot/tap/powerpipe
brew install turbot/tap/steampipe
steampipe plugin install azure
steampipe plugin install azuread
# Config creds via env vars or az cli default creds will be used
export AZURE_ENVIRONMENT="AZUREPUBLICCLOUD"
export AZURE_TENANT_ID="<tenant-id>"
export AZURE_SUBSCRIPTION_ID="<subscription-id>"
export AZURE_CLIENT_ID="<client-id>"
export AZURE_CLIENT_SECRET="<secret>"
# Run steampipe-mod-azure-insights
cd /tmp
mkdir dashboards
cd dashboards
powerpipe mod init
powerpipe mod install github.com/turbot/steampipe-mod-azure-insights
steampipe service start
powerpipe server
# Go to http://localhost:9033 in a browser
Prowler
Prowler je Open Source security tool za izvođenje AWS, Azure, Google Cloud i Kubernetes security best practices assessments, audits, incident response, continuous monitoring, hardening i forensics readiness.
U suštini nam omogućava da pokrenemo stotine provera protiv Azure okruženja kako bismo pronašli bezbednosne pogrešne konfiguracije i prikupili rezultate u json (i drugim tekstualnim formatima) ili ih pregledali na webu.
# Create a application with Reader role and set the tenant ID, client ID and secret in prowler so it access the app
# Launch web with docker-compose
export DOCKER_DEFAULT_PLATFORM=linux/amd64
curl -LO https://raw.githubusercontent.com/prowler-cloud/prowler/refs/heads/master/docker-compose.yml
curl -LO https://raw.githubusercontent.com/prowler-cloud/prowler/refs/heads/master/.env
## If using an old docker-compose version, change the "env_file" params to: env_file: ".env"
docker compose up -d
# Access the web and configure the access to run a scan from it
# Prowler cli
python3 -m pip install prowler --break-system-packages
docker run --rm toniblyx/prowler:v4-latest azure --list-checks
docker run --rm toniblyx/prowler:v4-latest azure --list-services
docker run --rm toniblyx/prowler:v4-latest azure --list-compliance
docker run --rm -e "AZURE_CLIENT_ID=<client-id>" -e "AZURE_TENANT_ID=<tenant-id>" -e "AZURE_CLIENT_SECRET=<secret>" toniblyx/prowler:v4-latest azure --sp-env-auth
## It also support other authentication types, check: prowler azure --help
Monkey365
Omogućava automatsko izvođenje revizija bezbednosnih konfiguracija Azure pretplata i Microsoft Entra ID-a.
HTML izveštaji se čuvaju u direktorijumu ./monkey-reports unutar foldera github repozitorijuma.
git clone https://github.com/silverhack/monkey365
Get-ChildItem -Recurse monkey365 | Unblock-File
cd monkey365
Import-Module ./monkey365
mkdir /tmp/monkey365-scan
cd /tmp/monkey365-scan
Get-Help Invoke-Monkey365
Get-Help Invoke-Monkey365 -Detailed
# Scan with user creds (browser will be run)
Invoke-Monkey365 -TenantId <tenant-id> -Instance Azure -Collect All -ExportTo HTML
# Scan with App creds
$SecureClientSecret = ConvertTo-SecureString "<secret>" -AsPlainText -Force
Invoke-Monkey365 -TenantId <tenant-id> -ClientId <client-id> -ClientSecret $SecureClientSecret -Instance Azure -Collect All -ExportTo HTML
ScoutSuite
Scout Suite prikuplja podatke o konfiguraciji za ručni pregled i ističe rizična područja. To je alat za sigurnosnu reviziju za multi-cloud okruženja koji omogućava procenu bezbednosnog stanja cloud okruženja.
virtualenv -p python3 venv
source venv/bin/activate
pip install scoutsuite
scout --help
# Use --cli flag to use az cli credentials
# Use --user-account to have scout prompt for user credentials
# Use --user-account-browser to launch a browser to login
# Use --service-principal to have scout prompt for app credentials
python scout.py azure --cli
Azure-MG-Sub-Governance-Reporting
To je PowerShell skripta koja vam pomaže da vizualizujete sve resurse i dozvole unutar Management Group i Entra ID tenant i pronađete bezbednosne greške u konfiguraciji.
Radi koristeći Az PowerShell module, dakle sve authentication metode koje alat podržava su dostupne.
import-module Az
.\AzGovVizParallel.ps1 -ManagementGroupId <management-group-id> [-SubscriptionIdWhitelist <subscription-id>]
Automatizovani Post-Exploitation alati
ROADRecon
The enumeration of ROADRecon pruža informacije o konfiguraciji Entra ID, kao što su korisnici, grupe, uloge i conditional access policies…
cd ROADTools
pipenv shell
# Login with user creds
roadrecon auth -u test@corp.onmicrosoft.com -p "Welcome2022!"
# Login with app creds
roadrecon auth --as-app --client "<client-id>" --password "<secret>" --tenant "<tenant-id>"
roadrecon gather
roadrecon gui
AzureHound
AzureHound je BloodHound collector za Microsoft Entra ID i Azure. To je jedan statički Go binarni fajl za Windows/Linux/macOS koji komunicira direktno sa:
- Microsoft Graph (Entra ID directory, M365) i
- Azure Resource Manager (ARM) control plane (subscriptions, resource groups, compute, storage, key vault, app services, AKS, etc.)
Ključne karakteristike
- Radi sa bilo kojeg mesta na javnom internetu prema tenant API-ima (nije potreban pristup internoj mreži)
- Generiše JSON za BloodHound CE ingestion radi vizualizacije puteva napada između identiteta i cloud resursa
- Podrazumevani User-Agent uočen: azurehound/v2.x.x
Opcije autentifikacije
- Korisničko ime + lozinka: -u
-p - Refresh token: –refresh-token
- JSON Web Token (access token): –jwt
- Service principal secret: -a
-s - Service principal certificate: -a
–cert <cert.pem> –key <key.pem> [–keypass ]
Primeri
# Full tenant collection to file using different auth flows
## User creds
azurehound list -u "<user>@<tenant>" -p "<pass>" -t "<tenant-id|domain>" -o ./output.json
## Use an access token (JWT) from az cli for Graph
JWT=$(az account get-access-token --resource https://graph.microsoft.com -o tsv --query accessToken)
azurehound list --jwt "$JWT" -t "<tenant-id>" -o ./output.json
## Use a refresh token (e.g., from device code flow)
azurehound list --refresh-token "<refresh_token>" -t "<tenant-id>" -o ./output.json
## Service principal secret
azurehound list -a "<client-id>" -s "<secret>" -t "<tenant-id>" -o ./output.json
## Service principal certificate
azurehound list -a "<client-id>" --cert "/path/cert.pem" --key "/path/key.pem" -t "<tenant-id>" -o ./output.json
# Targeted discovery
azurehound list users -t "<tenant-id>" -o users.json
azurehound list groups -t "<tenant-id>" -o groups.json
azurehound list roles -t "<tenant-id>" -o roles.json
azurehound list role-assignments -t "<tenant-id>" -o role-assignments.json
# Azure resources via ARM
azurehound list subscriptions -t "<tenant-id>" -o subs.json
azurehound list resource-groups -t "<tenant-id>" -o rgs.json
azurehound list virtual-machines -t "<tenant-id>" -o vms.json
azurehound list key-vaults -t "<tenant-id>" -o kv.json
azurehound list storage-accounts -t "<tenant-id>" -o sa.json
azurehound list storage-containers -t "<tenant-id>" -o containers.json
azurehound list web-apps -t "<tenant-id>" -o webapps.json
azurehound list function-apps -t "<tenant-id>" -o funcapps.json
What gets queried
- Graph endpoints (examples):
- /v1.0/organization, /v1.0/users, /v1.0/groups, /v1.0/roleManagement/directory/roleDefinitions, directoryRoles, owners/members
- ARM endpoints (examples):
- management.azure.com/subscriptions/…/providers/Microsoft.Storage/storageAccounts
- …/Microsoft.KeyVault/vaults, …/Microsoft.Compute/virtualMachines, …/Microsoft.Web/sites, …/Microsoft.ContainerService/managedClusters
Preflight behavior and endpoints
- Each azurehound list
- Platforma identiteta: login.microsoftonline.com
- Graph: GET https://graph.microsoft.com/v1.0/organization
- ARM: GET https://management.azure.com/subscriptions?api-version=…
- Cloud environment base URLs differ for Government/China/Germany. See constants/environments.go in the repo.
ARM-heavy objects (less visible in Activity/Resource logs)
- The following list targets predominantly use ARM control plane reads: automation-accounts, container-registries, function-apps, key-vaults, logic-apps, managed-clusters, management-groups, resource-groups, storage-accounts, storage-containers, virtual-machines, vm-scale-sets, web-apps.
- These GET/list operations are typically not written to Activity Logs; data-plane reads (e.g., *.blob.core.windows.net, *.vault.azure.net) are covered by Diagnostic Settings at the resource level.
OPSEC and logging notes
- Microsoft Graph Activity Logs are not enabled by default; enable and export to SIEM to gain visibility of Graph calls. Expect the Graph preflight GET /v1.0/organization with UA azurehound/v2.x.x.
- Entra ID non-interactive sign-in logs record the identity platform auth (login.microsoftonline.com) used by AzureHound.
- ARM control-plane read/list operations are not recorded in Activity Logs; many azurehound list operations against resources won’t appear there. Only data-plane logging (via Diagnostic Settings) will capture reads to service endpoints.
- Defender XDR GraphApiAuditEvents (preview) can expose Graph calls and token identifiers but may lack UserAgent and have limited retention.
Tip: When enumerating for privilege paths, dump users, groups, roles, and role assignments, then ingest in BloodHound and use prebuilt cypher queries to surface Global Administrator/Privileged Role Administrator and transitive escalation via nested groups and RBAC assignments.
Launch the BloodHound web with curl -L https://ghst.ly/getbhce | docker compose -f - up and import the output.json file. Then, in the EXPLORE tab, in the CYPHER section you can see a folder icon that contains pre-built queries.
MicroBurst
MicroBurst sadrži funkcije i skripte koje podržavaju otkrivanje Azure Services, proveru slabih konfiguracija i post exploitation akcije kao što su credential dumping. Namenjen je za upotrebu tokom penetration tests gde se koristi Azure.
Import-Module .\MicroBurst.psm1
Import-Module .\Get-AzureDomainInfo.ps1
Get-AzureDomainInfo -folder MicroBurst -Verbose
PowerZure
PowerZure je nastao iz potrebe za framework-om koji može i da izvrši reconnaissance i exploitation Azure, EntraID i pripadajućih resursa.
Koristi Az PowerShell modul, tako da su dostupne sve metode autentikacije koje Az PowerShell podržava.
# Login
Import-Module Az
Connect-AzAccount
# Clone and import PowerZure
git clone https://github.com/hausec/PowerZure
cd PowerZure
ipmo ./Powerzure.psd1
Invoke-Powerzure -h # Check all the options
# Info Gathering (read)
Get-AzureCurrentUser # Get current user
Get-AzureTarget # What can you access to
Get-AzureUser -All # Get all users
Get-AzureSQLDB -All # Get all SQL DBs
Get-AzureAppOwner # Owners of apps in Entra
Show-AzureStorageContent -All # List containers, shared and tables
Show-AzureKeyVaultContent -All # List all contents in key vaults
# Operational (write)
Set-AzureUserPassword -Password <password> -Username <username> # Change password
Set-AzureElevatedPrivileges # Get permissions from Global Administrator in EntraID to User Access Administrator in Azure RBAC.
New-AzureBackdoor -Username <username> -Password <password>
Invoke-AzureRunCommand -Command <command> -VMName <vmname>
[...]
GraphRunner
GraphRunner je post-exploitation toolset za interakciju sa Microsoft Graph API. Pruža razne alate za izvođenje reconnaissance, persistence i pillaging podataka iz Microsoft Entra ID (Azure AD) naloga.
#A good place to start is to authenticate with the Get-GraphTokens module. This module will launch a device-code login, allowing you to authenticate the session from a browser session. Access and refresh tokens will be written to the global $tokens variable. To use them with other GraphRunner modules use the Tokens flag (Example. Invoke-DumpApps -Tokens $tokens)
Import-Module .\GraphRunner.ps1
Get-GraphTokens
#This module gathers information about the tenant including the primary contact info, directory sync settings, and user settings such as if users have the ability to create apps, create groups, or consent to apps.
Invoke-GraphRecon -Tokens $tokens -PermissionEnum
#A module to dump conditional access policies from a tenant.
Invoke-GraphRecon -Tokens $tokens -PermissionEnum
#A module to dump conditional access policies from a tenant.
Invoke-DumpCAPS -Tokens $tokens -ResolveGuids
#This module helps identify malicious app registrations. It will dump a list of Azure app registrations from the tenant including permission scopes and users that have consented to the apps. Additionally, it will list external apps that are not owned by the current tenant or by Microsoft's main app tenant. This is a good way to find third-party external apps that users may have consented to.
Invoke-DumpApps -Tokens $tokens
#Gather the full list of users from the directory.
Get-AzureADUsers -Tokens $tokens -OutFile users.txt
#Create a list of security groups along with their members.
Get-SecurityGroups -AccessToken $tokens.access_token
#Gets groups that may be able to be modified by the current user
Get-UpdatableGroups -Tokens $tokens
#Finds dynamic groups and displays membership rules
Get-DynamicGroups -Tokens $tokens
#Gets a list of SharePoint site URLs visible to the current user
Get-SharePointSiteURLs -Tokens $tokens
#This module attempts to locate mailboxes in a tenant that have allowed other users to read them. By providing a userlist the module will attempt to access the inbox of each user and display if it was successful. The access token needs to be scoped to Mail.Read.Shared or Mail.ReadWrite.Shared for this to work.
Invoke-GraphOpenInboxFinder -Tokens $tokens -Userlist users.txt
#This module attempts to gather a tenant ID associated with a domain.
Get-TenantID -Domain
#Runs Invoke-GraphRecon, Get-AzureADUsers, Get-SecurityGroups, Invoke-DumpCAPS, Invoke-DumpApps, and then uses the default_detectors.json file to search with Invoke-SearchMailbox, Invoke-SearchSharePointAndOneDrive, and Invoke-SearchTeams.
Invoke-GraphRunner -Tokens $tokens
Stormspotter
Stormspotter kreira “attack graph” resursa u Azure subscription. Omogućava red teams i pentesters da vizualizuju attack surface i pivot opportunities unutar tenant-a, i znatno pomaže vašim defenders da se brzo orijentišu i prioritetizuju incident response zadatke.
Nažalost, izgleda neodržavano.
# Start Backend
cd stormspotter\backend\
pipenv shell
python ssbackend.pyz
# Start Front-end
cd stormspotter\frontend\dist\spa\
quasar.cmd serve -p 9091 --history
# Run Stormcollector
cd stormspotter\stormcollector\
pipenv shell
az login -u test@corp.onmicrosoft.com -p Welcome2022!
python stormspotter\stormcollector\sscollector.pyz cli
# This will generate a .zip file to upload in the frontend (127.0.0.1:9091)
Reference
- Cloud Discovery With AzureHound (Unit 42)
- AzureHound repository
- BloodHound repository
- AzureHound Community Edition Flags
- AzureHound constants/environments.go
- AzureHound client/storage_accounts.go
- AzureHound client/roles.go
Tip
Učite i vežbajte AWS Hacking:
HackTricks Training AWS Red Team Expert (ARTE)
Učite i vežbajte GCP Hacking:HackTricks Training GCP Red Team Expert (GRTE)
Učite i vežbajte Azure Hacking:
HackTricks Training Azure Red Team Expert (AzRTE)
Podržite HackTricks
- Proverite planove pretplate!
- Pridružite se 💬 Discord grupi ili telegram grupi ili pratite nas na Twitteru 🐦 @hacktricks_live.
- Podelite hakerske trikove slanjem PR-ova na HackTricks i HackTricks Cloud github repozitorijume.
HackTricks Cloud

