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
Credits
About the Author
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface

Cleaning up any trails left behind


One of the most important things we can do, as penetration testers, is to leave the environment in the same shape it was prior to the engagement. This means we need to make sure anything we had on the systems has been removed. This list is just some of the things that we need to do as responsible penetration testers:

  • Remove any user or system accounts that were created for any tests or procedures. We don't want to leave any unmonitored accounts.
  • Remove any exploits, backdoors, rootkits, or malware that we may have left behind as part of our testing.
  • Remove any test evidence that was left on the servers during our tests. We should have transferred these to our C&C server for safekeeping, but there may have been times when this wasn't possible. So, we want to make sure none of this is left behind.
  • Remove any tools or scripts that were used during any of the tests. We don't want anyone else to use our tools against the company after the fact.
  • Make sure any...