Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Kali Linux: Wireless Penetration Testing Beginner's Guide, Second Edition

You're reading from   Kali Linux: Wireless Penetration Testing Beginner's Guide, Second Edition Master wireless testing techniques to survey and attack wireless networks with Kali Linux

Arrow left icon
Product type Paperback
Published in Mar 2015
Publisher Packt
ISBN-13 9781783280414
Length 214 pages
Edition 2nd Edition
Arrow right icon
Authors (2):
Arrow left icon
Vivek Ramachandran Vivek Ramachandran
Author Profile Icon Vivek Ramachandran
Vivek Ramachandran
Cameron Buchanan Cameron Buchanan
Author Profile Icon Cameron Buchanan
Cameron Buchanan
Arrow right icon
View More author details
Toc

Table of Contents (13) Chapters Close

Preface 1. Wireless Lab Setup FREE CHAPTER 2. WLAN and its Inherent Insecurities 3. Bypassing WLAN Authentication 4. WLAN Encryption Flaws 5. Attacks on the WLAN Infrastructure 6. Attacking the Client 7. Advanced WLAN Attacks 8. Attacking WPA-Enterprise and RADIUS 9. WLAN Penetration Testing Methodology 10. WPS and Probes A. Pop Quiz Answers Index

Reporting


Finally, at the end of testing, it is necessary to report your findings to the client. It's important to ensure that the report matches the quality of your testing. As the client will only see the report, you have to give it as much love and attention as you do to your testing. The following is a guideline to the layout of the report:

  1. Management summary.

  2. Technical summary.

  3. Findings:

    • Vulnerability description

    • Severity

    • Affected devices

    • Vulnerability type—software/hardware/configuration

    • Remediation

  4. Appendices.

The management summary should be aimed at talking to a senior nontechnical audience with a focus on the effects and mitigations required at a high level. Avoid language that is too technical and ensure that the root causes are covered.

The technical summary should be a midpoint between the management summary and findings list. It should be aimed at a developer or a technical lead with a focus on how to fix the issues and broad solutions that could be implemented.

The findings list should...

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 €18.99/month. Cancel anytime