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

Summary


We are now done with the chapter, so let us recap. Since we completed all the penetration tests that were required for our engagement, we need to make sure that we clean up any mess we made, just like our mothers have taught us. It is important as professionals to make sure that we leave the environment the same as it was before we started and leave no tracks behind. To accomplish this, we talked about various items that we should be certain get done, basically, a cleaning-up list. To accomplish this, we talked about utilities to hide our tracks, for example, shred, dd, ClearLogs, and cleanev. They all have various specialties on where and when to use and all of them should be in the penetration tester's toolbox.

Next, since physical destruction may be necessary depending on the stakeholders' requirement and/or data sensitivity level, we talked about the various ways we can physically destroy our hardware. However, in some cases we may need to engage a third-party hardware destruction...