A collection of Python scripts for AWS penetration testing, reconnaissance, exploitation, and persistence.
AWS pwn is a collection of Python scripts designed for AWS penetration testing and security assessment. It helps security professionals identify misconfigurations, escalate privileges, maintain persistence, and exfiltrate data from AWS environments. The toolkit covers reconnaissance, exploitation, stealth, and post-compromise activities across various AWS services.
Security researchers, penetration testers, and red teamers who need to assess the security of AWS infrastructure. It's also useful for blue teams and defenders looking to understand attack techniques.
It provides a focused, script-based approach to AWS security testing without the overhead of larger frameworks. The tools are purpose-built for real-world scenarios, though they may require updates as AWS changes.
A collection of AWS penetration testing junk
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Includes scripts like validate_iam_access_keys.py and validate_s3_buckets.py for checking access keys, buckets, principals, and accounts, enabling detailed pre-compromise intelligence gathering.
Provides practical tools such as assume_roles.py for role assumption and add_iam_policy.py for privilege escalation, tailored for hands-on AWS penetration testing scenarios.
Offers mechanisms like disrupt_cloudtrail.py to evade detection and Lambda backdoor scripts for maintaining access, addressing post-compromise activities in engagements.
Acknowledges contributions from others like Mike Fuller and encourages updates, helping adapt tools as AWS evolves, though reliance on community upkeep is a trade-off.
The README admits scripts are 'horribly written' and may break due to AWS API changes, requiring frequent manual fixes and updates, which adds maintenance overhead.
Some scripts, like backdoor_all_roles.py, require editing constants within the file instead of using arguments, increasing setup complexity and risk of errors.
The 'To do' list highlights missing functionalities such as stack resource dumping, and tools like dump_account_data.sh are 'very noisy,' potentially alerting defenders during testing.