Book Image

Penetration Testing Bootcamp

By : Jason Beltrame
Book Image

Penetration Testing Bootcamp

By: Jason Beltrame

Overview of this book

Penetration Testing Bootcamp delivers practical, learning modules in manageable chunks. Each chapter is delivered in a day, and each day builds your competency in Penetration Testing. This book will begin by taking you through the basics and show you how to set up and maintain the C&C Server. You will also understand how to scan for vulnerabilities and Metasploit, learn how to setup connectivity to a C&C server and maintain that connectivity for your intelligence gathering as well as offsite processing. Using TCPDump filters, you will gain understanding of the sniffing and spoofing traffic. This book will also teach you the importance of clearing up the tracks you leave behind after the penetration test and will show you how to build a report from all the data obtained from the penetration test. In totality, this book will equip you with instructions through rigorous tasks, practical callouts, and assignments to reinforce your understanding of penetration testing.
Table of Contents (17 chapters)
Title Page
About the Author
About the Reviewer
Customer Feedback

Automating evidence collection

The last thing you want to do in a penetration test is make it difficult to transfer the data over that newly formed stunnel tunnel. Because of this, having a tool you can run that will just copy the files over your request is key. In my case, I tend to use a script that will send the files over to the correct directory on my C&C server. We can run this script whenever we have evidence to move over.

My default setup on the Raspberry Pi and C&C server is as follows. Feel free to change the directories to whatever works best for you:

  1. On the internal server (Raspberry Pi), create the evidence folder in /var and, within this directory, create a file called LOG. Make sure that the log file is writable:
  1. Now that the evidence directory is all set, we just need to create the script. I placed the script in /root/scripts on the Raspberry Pi. After creating the script, make sure you make it executable:
  1. The internal server (Raspberry Pi) is all set at this point. I...