<p>We've all been there. You walk in to a network blind and the first thing you ask for is a network diagram. What gets handed to you has apparently fallen out of a bowl of ramen and on to the page. Overlapping lines, big arrows, and host names in print so small that only insects can read it. When you ask for someone to explain it, they just end up drawing something on a whiteboard rather than walk you through The Diagram (tm).</p>
<p>But really, what makes a good network diagram? It's easy to find examples of bad ones; making good ones is much harder. Having a useful network diagram can make vulnerability assessments go better, aid in incident response, and making planning the location of security devices much easier. Unfortunately creating a good network diagram is a dark art. This talk will shed some light on the situation and help you make better diagrams. I will examine the traits of a good network diagram including graphical elements, proper use of fonts and colors, and the overall intent of the map. I will go over examples of good and bad diagrams in a structured fashion and point out what works and what doesn't. Finally, I will provide concrete guidelines to help when you're creating your next network masterpiece.</p>