Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Security-Basics
[Top] [All Lists]

Re: NAT external/Public IP

Subject: Re: NAT external/Public IP
Date: Thu, 25 Oct 2007 19:23:13 +0200
On 2007-10-25 Jason Alexander wrote:
On 25 October 2007 15:49 Ansgar -59cobalt- Wiechers wrote:
On 2007-10-25 crazy frog crazy frog wrote:
On 24 Oct 2007 15:46:21 -0000, smarts_buy@yahoo.com wrote:
Would like know is ther any security concern to bring in 
external/public IP with out NAT to inside of the enterprise network.
Is it any way more secure if we use NAT?
[...]
2)If you allow lots of machine to direct access the internet with 
external ip they may pose a security risk.

How would that pose a risk that would not exist with NAT'ed machines?

If its not a security risk then why is it a PCI requirement?

Aside from the fact that this is no answer to my question: apparently
because the people specifying this failed to understand that obfuscation
of IP addresses doesn't add to a system's security. Either the system is
secure, then it doesn't matter whether someone knows its address, or it
isn't, in which case you're just relying on luck, hoping that the Bad
Guys(tm) won't find you. Which you shouldn't.

Regards
Ansgar Wiechers
-- 
"All vulnerabilities deserve a public fear period prior to patches
becoming available."
--Jason Coombs on Bugtraq

<Prev in Thread] Current Thread [Next in Thread>