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
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Building and Automating Penetration Testing Labs in the Cloud

You're reading from   Building and Automating Penetration Testing Labs in the Cloud Set up cost-effective hacking environments for learning cloud security on AWS, Azure, and GCP

Arrow left icon
Product type Paperback
Published in Oct 2023
Publisher Packt
ISBN-13 9781837632398
Length 562 pages
Edition 1st Edition
Tools
Arrow right icon
Author (1):
Arrow left icon
Joshua Arvin Lat Joshua Arvin Lat
Author Profile Icon Joshua Arvin Lat
Joshua Arvin Lat
Arrow right icon
View More author details
Toc

Table of Contents (15) Chapters Close

Preface 1. Part 1: A Gentle Introduction to Vulnerable-by-Design Environments
2. Chapter 1: Getting Started with Penetration Testing Labs in the Cloud FREE CHAPTER 3. Chapter 2: Preparing Our First Vulnerable Cloud Lab Environment 4. Chapter 3: Succeeding with Infrastructure as Code Tools and Strategies 5. Part 2: Setting Up Isolated Penetration Testing Lab Environments in the Cloud
6. Chapter 4: Setting Up Isolated Penetration Testing Lab Environments on GCP 7. Chapter 5: Setting Up Isolated Penetration Testing Lab Environments on Azure 8. Chapter 6: Setting Up Isolated Penetration Testing Lab Environments on AWS 9. Part 3: Exploring Advanced Strategies and Best Practices in Lab Environment Design
10. Chapter 7: Setting Up an IAM Privilege Escalation Lab 11. Chapter 8: Designing and Building a Vulnerable Active Directory Lab 12. Chapter 9: Recommended Strategies and Best Practices 13. Index 14. Other Books You May Enjoy

Succeeding with Infrastructure as Code Tools and Strategies

In the previous chapter, we manually created our first vulnerable lab environment using the AWS Management Console. It probably took us about an hour and a half to set everything up. After completing the lab setup, it may have taken us an additional 30 minutes to test whether everything was (mis)configured as expected. What if we wanted to set up 10 lab environments similar to what we prepared in Chapter 2 for a security training course? Do we really need around 20 hours to set all of these up? In addition to this, remember that we only worked on a small component of an entire cloud penetration testing lab environment! Complete lab environments generally have about 5 to 10 times more resources compared to what we prepared in Chapter 2. Assuming the complete environment is at least five times larger than what we initially prepared, and taking into account the need to create and delete the entire environment every time to manage...

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
Banner background image