My TaoSecurity News page says I taught 41 classes lasting a day or more, from 2002 to 2014. All of these involved some aspect of network security monitoring (NSM). Many times students would ask me when I would create the “advanced” version of the class, usually in the course feedback. I could never answer them, so I decided to do so in this blog post.
The short answer is this: at some point, advanced NSM is no longer NSM. If you consider my collection – analysis – escalation – response model, NSM extensions from any of those phases quickly have little or nothing to do with the network.
Here are a few questions I have received concerned “advanced NSM,” paired with the answers I could have provided.
Q: “I used NSM to extract a binary from network traffic. What do I do with this binary?”
A: “Learn about reverse engineering and binary analysis.”
Q: “I used NSM to capture an exchange between a Windows client and a server. What does it mean?”
A: “Learn about Server Message Block (SMB) or Common Internet File System (CIFS).”
Q: “I used NSM to capture cryptographic material exchanged between a client and a server. How do I understand it?”
A: “Learn about cryptography.”
Q: “I used NSM to grab shell code passed with an exploit against an Internet-exposed service. How do I tell what it does?”
A: “Learn about programming in assembly.”
Q: “I want to design custom hardware for packet capture. How do I do that?”
A: “Learn about programming ASICs (application specific integrated circuits).”
The point is that eventually the NSM road takes you to other aspects of the cyber security landscape.
Are there *any* advanced area for NSM? One could argue that protocol analysis, as one finds in tools like Bro, Suricata, Snort, Wireshark, and so on constitute advanced NSM. However, you could just as easily argue that protocol analysis becomes more about understanding the programming and standards behind each of the protocols.
In brief, to learn advanced NSM, expand beyond NSM.