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

Product type Paperback

Published in Oct 2023

Publisher Packt

ISBN-13 9781837632398

Length 562 pages

Edition 1st Edition

Tools

AWS

Concepts

Cloud Security

Author (1):

Joshua Arvin Lat

View More author details

Table of Contents (15) Chapters

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

Why subscribe?

14. Other Books You May Enjoy

Cleaning up

Cleaning up the cloud resources we created or deployed is a crucial step when working with vulnerable cloud applications and environments. If we don’t clean up and delete the resources we created right away, we might end up paying for unused cloud resources. In addition to this, these cloud resources may end up being attacked by malicious users as well. At a minimum, we will pay for the time the following resources are running:

1 x ml.t3.medium SageMaker notebook instance
1 x t2.micro EC2 instance of the Cloud9 environment
1 x QLDB ledger database

Note that there are other costs we should consider as well—including data transfer fees, storage costs for any persistent data used by the instances, potential charges for additional AWS services utilized in the lab environment (for example, monitoring logs), and any applicable taxes or fees associated with the AWS usage.

Important note

It is important to note that this lab allows for...