Comments on: QoTW #42: Would publishing a network diagram make the network less secure? http://security.blogoverflow.com/2013/01/qotw-42-would-publishing-a-network-diagram-make-the-network-less-secure/ The Security Stack Exchange Blog Sat, 06 Feb 2016 05:11:22 +0000 hourly 1 https://wordpress.org/?v=4.5.6 By: Shalin http://security.blogoverflow.com/2013/01/qotw-42-would-publishing-a-network-diagram-make-the-network-less-secure/#comment-278195 Wed, 05 Feb 2014 05:44:14 +0000 http://security.blogoverflow.com/?p=957#comment-278195 I draw these kinds of network diagrams and I know how important they are to understand network concepts. Its a great article done by you and i’m sharing this right away!

]]> By: Mike http://security.blogoverflow.com/2013/01/qotw-42-would-publishing-a-network-diagram-make-the-network-less-secure/#comment-25852 Wed, 06 Feb 2013 03:23:34 +0000 http://security.blogoverflow.com/?p=957#comment-25852 You do realize the architecture behind the diagram, correct? It is a virtual environment, so what information would be gained by DoS of the virtual host? If your goal is merely to be a nuisance by bringing down the entire environment, then more power to you. Wouldn’t it make more sense to target a guest VM that actually holds useful information such as the numerous exchange servers or loan domain controller?

]]> By: Richard http://security.blogoverflow.com/2013/01/qotw-42-would-publishing-a-network-diagram-make-the-network-less-secure/#comment-18224 Mon, 28 Jan 2013 13:56:11 +0000 http://security.blogoverflow.com/?p=957#comment-18224 would i look at your crappy diagram and use it to break your network?!… no, firstly you haven’t even begun to tell me the stuff I need, software running, firmware versions, os version, no i think me and most of the rest of the hacking community will stick to nmap,

I am more interested in the software running on your network

admittedly the target server to DOS, 142.42.0.56? this is a non-publicly facing back end server? So if I want to DOS you I can keep my resource usage to a minimum by targeting that IP, I think this is likely something we would have been able to determine.

]]>