Book Image

Kali Linux 2018: Windows Penetration Testing - Second Edition

By : Wolf Halton, Bo Weaver
Book Image

Kali Linux 2018: Windows Penetration Testing - Second Edition

By: Wolf Halton, Bo Weaver

Overview of this book

Microsoft Windows is one of the two most common OSes, and managing its security has spawned the discipline of IT security. Kali Linux is the premier platform for testing and maintaining Windows security. Kali is built on the Debian distribution of Linux and shares the legendary stability of that OS. This lets you focus on using the network penetration, password cracking, and forensics tools, and not the OS. This book has the most advanced tools and techniques to reproduce the methods used by sophisticated hackers to make you an expert in Kali Linux penetration testing. You will start by learning about the various desktop environments that now come with Kali. The book covers network sniffers and analysis tools to uncover the Windows protocols in use on the network. You will see several tools designed to improve your average in password acquisition, from hash cracking, online attacks, offline attacks, and rainbow tables to social engineering. It also demonstrates several use cases for Kali Linux tools like Social Engineering Toolkit, and Metasploit, to exploit Windows vulnerabilities. Finally, you will learn how to gain full system-level access to your compromised system and then maintain that access. By the end of this book, you will be able to quickly pen test your system and network using easy-to-follow instructions and support images.
Table of Contents (12 chapters)

NetBIOS name service and NTLM

Back in the early days of networking, just after the birth of the PC, people wanted the ability to share files from one system to another. In business applications, systems already had the ability to network themselves using proprietary networking protocols such as IPX (Internetwork Packet Exchange), Tolkien Ring, and coaxial bus networks. One big problem with all these proprietary protocols is that none of them could cross-communicate between themselves. This became known as vendor lock-in, and we still have some of this even today with proprietary systems and protocols. (Yes, I am pointing the finger at you, Microsoft.) Using these protocols meant paying a license fee for each system on the network-not just a cost for the OS, but an extra cost to network each system, then an extra fee on top of that for each workstation connecting to a server across...