Security Basics mailing list archives
RE: NAT external/Public IP
From: "Grant Donald" <Grant.Donald () datacash co za>
Date: Mon, 29 Oct 2007 09:55:40 +0200
There's a real security benefit in using PAT for internet access from staff PC's. Any alternative is most definitely less secure. -Grant -----Original Message----- From: listbounce () securityfocus com [mailto:listbounce () securityfocus com] On Behalf Of Jason Alexander Sent: 26 October 2007 10:19 AM To: Eric Furman; Security Basics Subject: RE: NAT external/Public IP Looks like a requirement? <snip>1.5 Implement IP masquerading to prevent internal addresses from being translated and revealed on the Internet. Use technologies that implement RFC 1918 address space, such as port address translation (PAT) or network address translation (NAT).<snip> -----Original Message----- From: Eric Furman [mailto:ericfurman () fastmail net] Sent: 25 October 2007 18:13 To: Jason Alexander; Security Basics Subject: RE: NAT external/Public IP
-----Original Message----- From: listbounce () securityfocus com [mailto:listbounce () securityfocus com] On Behalf Of Ansgar -59cobalt- Wiechers Sent: 25 October 2007 15:49 To: security-basics () securityfocus com Subject: Re: NAT external/Public IP 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?
On Thu, 25 Oct 2007 16:28:13 +0100, "Jason Alexander" <jalexander () plus net> said:
If its not a security risk then why is it a PCI requirement?
If you are talking about Payment Card Industry (PCI) Data Security Standard, there isn't one for NAT. DISCLAIMER: This email and any files transmitted with it are confidential to DataCash Group plc and its group companies. It is intended only for the person to whom it is addressed. If you have received this email in error, please forward it to info () datacash com with the subject line "Received in Error". If you are not the intended recipient you must not use, disclose, copy, print, distribute or rely on this email or any of its transmitted files.
Current thread:
- NAT external/Public IP smarts_buy (Oct 24)
- Re: NAT external/Public IP crazy frog crazy frog (Oct 25)
- Re: NAT external/Public IP Ansgar -59cobalt- Wiechers (Oct 25)
- RE: NAT external/Public IP Jason Alexander (Oct 25)
- RE: NAT external/Public IP Eric Furman (Oct 25)
- RE: NAT external/Public IP Jason Alexander (Oct 26)
- RE: NAT external/Public IP Grant Donald (Oct 29)
- Re: NAT external/Public IP Ansgar -59cobalt- Wiechers (Oct 29)
- Re: NAT external/Public IP Michael Painter (Oct 30)
- RE: NAT external/Public IP Grant Donald (Oct 30)
- Re: NAT external/Public IP Ansgar -59cobalt- Wiechers (Oct 30)
- RE: NAT external/Public IP Security Incidents (Oct 30)
- Re: NAT external/Public IP crazy frog crazy frog (Oct 31)
- RE: NAT external/Public IP Dan Lynch (Oct 31)
- Re: NAT external/Public IP Ansgar -59cobalt- Wiechers (Oct 25)
- Re: NAT external/Public IP crazy frog crazy frog (Oct 25)
- Re: NAT external/Public IP Chris Barber (Oct 25)
- RE: NAT external/Public IP Nick Vaernhoej (Oct 25)
- Re: NAT external/Public IP Ansgar -59cobalt- Wiechers (Oct 25)