8 replies
by alpha-male
It all boils down to this:
Public IP addresses may be accessed across the Internet while private addresses may not. This is important if you intend to have a machine that needs to be accessed by other devices on the Internet. A Public IP address should be used if you are running a web server, an FTP server, a public e-mail server, VPN, etc.
The advantage is others can access the machine via the net. The drawback is...others can access the machine via the net. The threat level really doesn't really depend on what data you have. The hackers are out there and if you're vulnerable they'll find you. The more "high profile" you are, the more likely you'll draw attention...but believe me, they watch for new servers and sites coming online.You are all but certain to get scanned...or worse. As you have stated, the defense is a firewall. Have a intrusion detection and counter-measures policy and definitely a disaster policy. If your security is good, and the firewall well configured you*may* not need it...but bear in mind new exploits are revealed constantly. Be on guard.
Private IP addresses may be used to eliminate many security threats. A Private IP cannot be accessed by other devices on the Internet (they only see the Public IP). Network Address Translation (NAT) or IP Masquerading allows you to use the internet and access sites without them having access to the individual workstation. No information that was not previously requested from behind the NAT will be allowedto pass. Bear in mind though, your router or server (the device providing the NAT functionality) DOES still need to be protected/secured. It has a public IP and is vulnerable...so you *still* need to take security measures.
by alpha-male
by lmuran
by ann777
Public ip addresses are accessible from anywhere. Private ip addresses cannot be accessed outside the network unless there's NAT (network address translation) devices within the internal network. Firewalls can use NAT or they can use other more intensive security methods with multiple external/routable ip addresses.
A company with public ip addresses and a firewall may not be any more secure than a company with public ip addresses and NO firewall.
Everything depends on how the firewallis setup. When you have a firewall, you have to open ports to do certain things on the web; any open port can be exploited.
The safest alternative is private ip addresses, but it is also the most restrictive. Your company must decide on what itneeds to do to remain competitive in today's environment.
by lmuran
by mckaytech
The above answers are largely correct in regards to security but I just wanted to add the thought that using RFC1918 (private) addresses inside your firewall also gives you a lot more flexibility as far as your LAN design.
However, one other security point to be added is that any server accessible from the Internet should be in a DMZ and not on your internal network, regardless of whether its actual address is public or private. That way, if it does get compromised, it doesn't put your internal network in harm's way. Defense in depth.
regards!
paul
by lmuran
by lmuran
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending