Cloud
Pacu
AWS exploitation framework for authorized identity and service abuse proofs after config review.
What it is
Pacu is modular AWS post-ex: enum, privilege-path confirmation, and service abuse inside an account you already hold a role in. Most modules should stay on enum. Anything that creates users, opens buckets, or tampers with logging is a write and needs an explicit RoE line plus cleanup.
Reach for it when
Cloud assumed-role work when config scanners showed an identity path and you need to prove it without clicking around the console.
Watch-outs
Pacu can create resources that cost money and open the account. Snapshot logging first. Never run modules against production data planes with ePHI. Kill the session keys at close and delete any resource the framework created.
Typical invocation
pacu --session nw-landing --module-name iam__enum_users_roles_policies
Authorized assessments only. Stay inside the rules of engagement.
Pin to a kit
Open an engagement first.
Related
- Prowler
Cloud security configuration scanner for AWS, Azure, and GCP against CIS and similar benchmarks.
- ScoutSuite
Multi-cloud audit tool that collects configuration via APIs and highlights risky settings.
- Impacket
Python collection of Windows/AD protocol tools for authorized authentication and post-ex proof.