Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
AWS Penetration Testing

You're reading from   AWS Penetration Testing Beginner's guide to hacking AWS with tools such as Kali Linux, Metasploit, and Nmap

Arrow left icon
Product type Paperback
Published in Dec 2020
Publisher Packt
ISBN-13 9781839216923
Length 330 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
Jonathan Helmus Jonathan Helmus
Author Profile Icon Jonathan Helmus
Jonathan Helmus
Arrow right icon
View More author details
Toc

Table of Contents (17) Chapters Close

Preface 1. Section 1: Setting Up AWS and Pentesting Environments
2. Chapter 1: Building Your AWS Environment FREE CHAPTER 3. Chapter 2: Pentesting and Ethical Hacking 4. Section 2: Pentesting the Cloud – Exploiting AWS
5. Chapter 3: Exploring Pentesting and AWS 6. Chapter 4: Exploiting S3 Buckets 7. Chapter 5: Understanding Vulnerable RDS Services 8. Chapter 6: Setting Up and Pentesting AWS Aurora RDS 9. Chapter 7: Assessing and Pentesting Lambda Services 10. Chapter 8: Assessing AWS API Gateway 11. Chapter 9: Real-Life Pentesting with Metasploit and More! 12. Section 3: Lessons Learned – Report Writing, Staying within Scope, and Continued Learning
13. Chapter 10: Pentesting Best Practices 14. Chapter 11: Staying Out of Trouble 15. Chapter 12: Other Projects with AWS 16. Other Books You May Enjoy

Goal-based pentesting scenarios

Now let's start to move forward and look at some real scenarios that are relatively common when pentesting S3 in a real-life environment. While it may not seem like typical "pentesting," because AWS pentesting does not use a typical pentesting methodology, it does still serve the mission of finding issues and leveraging them to your advantage. Goal-based pentesting entails testing a target with a "goal" in mind. In this case, we are looking for issues and mishaps that may be in an S3 bucket. Oftentimes, organizations will want to know how vulnerable a specific resource is, and how the path that leads to the vulnerability could be exploited.

For this example, we will look at how an unsecured bucket leads us to delete an important document and then upload a document with the same name. We will be using an "assumed model," meaning that we already have some type of access to the system. Before we walk through the exercise...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime