| ▲ | simoncion 2 hours ago | ||||||||||||||||||||||||||||||||||
> At some point you're going to have to find a way to argue that the Cisco PIX was not a security device... What? It's a firewall that can do NAT. The PIX is clearly a security device. NAT is clearly an address-depletion-mitigation technique. > Since there's no way for anyone on the Internet to know which machine on the corporate network is using a Class C address at any given time, it's impossible to establish a telnet or FTP session with any particular device. Right. And you can achieve the exact same effect with a firewall on an edge router or on a host. I get that firewalls might have been much less common thirty-ish years ago and that doing packet filtering might have been pretty novel for many, leading folks to get confused when they encountered a combination firewall+NAT device. | |||||||||||||||||||||||||||||||||||
| ▲ | tptacek 2 hours ago | parent [-] | ||||||||||||||||||||||||||||||||||
I'm not sure I can be any clearer about the fact that NAT is both a security feature and an address management feature. I feel like people who weren't practitioners are the time are trying to reason axiomatically that every feature fits into precisely one bucket, or that a security feature isn't a true security feature if it can be replaced by one or more other "cleaner" security features. None of that is true. Practitioners at the time were not confused. "You can achieve the same effect" doesn't mean anything in this discussion. If that's your argument, you've conceded the debate. | |||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||