Apr 20, 2018
updated at: Jun 10, 2018
I'm very interested in security, moreover penetration testing. I started to read some books and here is my top 5!
By Jon Erickson.
This book is 10 years old, but boy I learned a lot. If you want to get started in the hacker field and you want to go balls deep directly this is the book to go with. The goal of this book is not to learn how to hack but how things really work. The book first explains what assembly is and how code gets read by the computer, next you get an introduction to C and after that the fun starts. You learn about creating reverse shells, how to capture and modify packets, encryption, buffer overflows and shellcode. What I really liked was the shellcode part and debugging memory, the sad part is that the book only covers 32 bit architecture so almost nothing works when copying code (but you are a hacker so you should find out how it works on your architecture!). I really hope one day there will be a 3rd edition.
By Peter Kim.
On a penetration test when you are out of ideas for exploiting for example, open this book at the correct chapters and continue your pentest. This is what the book is intended for, it is something you bring with you, open at a specific chapter and get that shell.
NOTE: The Hacker Playbook 3 got recently released and is more focussed on red teaming.
By Justin Seitz.
Very good coverage of what you can do with Python. It starts with building little tools like tcp_server, netcat, tcp_proxy all in python step by step guide. And ends with Windows privilege escalation and automating forensic tools.
By Ben Clark.
This is not a real book, it's a book full of cheatsheets for various stuff like reverse shells in different languages, firewall ports, Windows NT version explanation and so on.
By Wil Allsopp.
This book is not like the others; a tutorial. It wants to show you how things are really done in the real world, it explains what an advanced persistent threat (APT) is and how to model it in the real world. One of the scenario's was connecting to your C2 server via DNS or via TOR, which was very interesting.