TO UNSUBSCRIBE: email "unsubscribe issforum" in the body of your message to
[EMAIL PROTECTED] Contact [EMAIL PROTECTED] for help with any problems!
----------------------------------------------------------------------------
>I disagree; it's common practice to use the RFC-suggested non-routable
>IP blocks 10.0.0.x and 192.168.1.x for internal addresses. Surely if
> >these were not protected by a firewall and a dmz config of some sort, >it
>would be a problem. Otherwise, bleeding your internal IP addresses >is
>notreally a security risk.
Well, I challenge you to recommend to your management that posting your
company's entire network infrastructure on the Internet is a good idea
since you're protected by a firewall.
I do see your point. However, I sleep better at night with Andy Grove's
mantra: only the paranoid survive [stay employed, don't get owned].
Why give out any infomation to the entire world about your internal
network infrastructure if you don't have to? I would wager that at
least 75% of the RFC1918 addresses you see in e-mail headers aren't
there because someone said "let's just leave them in there, we're
protected by a firewall". It's something that is easily, but not very
often, overlooked.
If you're going to sit down and actually secure an enterprise network
why not do it thoroughly? Why not plug every hole you can possibly find?
Why would you want to give any potential cracker any information about
your network?
-chris
_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
Share information about yourself, create your own public profile at
http://profiles.msn.com.
