3 ms·
NAT (standard one to many SNAT) is absolutely a firewall. You can't connect to the machines behind it from outside, which serves the exact same purpose as a de
by sneak 5y ago
NAT (standard one to many SNAT) is absolutely a firewall. You can't connect to the machines behind it from outside, which serves the exact same purpose as a default deny inbound firewall.
This is a false meme right up there with "docker is not a security boundary".
- zajio1am 5y agoThat is not true. It is problematic in general but in some limited cases it is possible. For example, neighbors on WAN network could just send packets with dst address from your private LAN range directly to the WAN port of your router. If the router is configured as both NAT (SNAT) and firewall, it will drop such packet as not associated with any existing flow, but if it is just configured as SNAT, then such packet would be just forwarded inside unmodified.
- sneak 5y agoA router that accepts inbound packets with 1918 dsts on the wan port is a broken router.
- icedchai 5y agoNot necessarily. Routers can be used internally. Even consumer level routers are used in weird dual NAT situations. (Also there is no requirement that you use RFC-1918 addresses behind NAT.)
- jeroenhd 5y agoYou can't easily connect to devices behind NAT but that's more of a restriction than a security measure. Once you can trick a device into making an outgoing connection, you can bypass a lot of security in most NAT implementations [0], allowing an attacker access to any port of the victim computer. A variant was also discovered and later hot-patched [1] that could even expose other devices in the internal network. NAT was never designed to be a security boundary and should not be considered one. It's only a matter of time until the next NAT slipstreaming attack is discovered. That doesn't mean your computer is in some kind of immediate danger or that you should cut your internet cable right now, of course. It's just good to know what does and what doesn't work when it comes to your network security and why IPv6 changes very little. In fact, I'd argue that most IPv6 routers are actually more secure than IPv4 NAT because incoming traffic will never be translated as if it came from your router like some NAT implementations do, and incoming traffic is usually always blocked. The lack of a need for parsing and interpreting network packets makes your firewall a lot easier to reason about. Docker is not designed as a security boundary, but it does provide some security functionality if used correctly that would otherwise be a pain. Sticking something in a docker container and just running it as root is dangerous, but Docker makes it easy to apply strict, complex security measures, which its security bonus comes from. NAT is the opposite, it's supposed to work like magic. That's why network protocols like UPnP were invented, not to automate firewall management, but to make application use transparent to the user. [0]: https://samy.pl/slipstream/ https://samy.pl/slipstream/ [1]: https://www.armis.com/research/nat-slipstreaming-v20/ https://www.armis.com/research/nat-slipstreaming-v20/