-
Notifications
You must be signed in to change notification settings - Fork 28
IAM Enumeration and Analysis Workflow
WebbinRoot edited this page May 9, 2026
·
6 revisions
This is the recommended path if your goal is permission mapping and escalation-path analysis.
modules run enum_all --iam
modules run enum_policy_bindings --ensure-treeenum_policy_bindings supports service scoping:
modules run enum_policy_bindings --resource-manager --storage --compute --secretsmodules run process_iam_bindingsOptional outputs:
modules run process_iam_bindings --csv --txt
modules run process_iam_bindings --silent --csv --txt
modules run process_iam_bindings --force-refresh-bindingsWhat this gives you:
- flattened member-to-role/resource summaries
- inheritance-aware organization/folder/project context
- per-member rows stored for downstream reporting
creds info
creds info --csv--csv is useful when terminal truncation hides long permission sets.
modules run enum_gcp_cloud_hound_data --expand-inherited --reset --out Bloodhound_Output.jsonThen import JSON into BloodHound CE.
analyze_vulns is currently a scaffold and returns:
[*] analyze_vulns is coming soon.
Use process_iam_bindings + OpenGraph for current operational analysis.
- Authentication Reference
- Workspace Instructions
- Google Workspace Enumeration
- CLI Module Reference
- Enumeration Module Reference
- Exploit Module Reference
- Downloads to Disk
- Logging & Verbosity
- Data View/Export
- IAM Enumeration and Analysis Workflow
- Troubleshooting and FAQ