I really like network penetration testing. Some might even say that it’s one of my favorite things! Whether I’m looking to break into an internal network from the Internet, or I’m slinking my way through internal SMB shares, databases, and domain controllers, you can bet that I’ve got a smile on my face while doing it. When I first got into network penetration testing, I really didn’t know where to start. I was fortunate enough to have the opportunity to watch people more talented than I do their work, which is where I got my initial bit of momentum. Since then I’ve relied on curiosity, trial and error, and the knowledge that our awesome community members freely share to continue bulking up my skillset.
I always wished that there was a resource somewhere with information about attacking and defending networks on a per-port basis. I found myself constantly hopping between a handful of blogs and various articles of documentation to form a full opinion of how to attack and defend a single network service.
And so, with all of that being said, I’d like to introduce my series entitled “Pwnage Per Port,” where every post will focus on a single TCP or UDP port and will cover the following topics:
- What is typically on the port
- A brief history of the service
- Security concerns around the service
- Tools and techniques for attacking the service
- Tools and techniques for defending the service
I’ll be running through the more common ports first (and no, I won’t be doing TCP 80 or 443 – check out my good friends Shubs and Mandatory for that stuff), and would love feedback about what ports I should do next and any tricks or techniques that I may have missed.
I hope you all enjoy, and as always hit me up at @_lavalamp with questions, comments, and feedback!