Re: Firewall definition
From: Matt Stevens (matt_at_zola.org.uk)
Date: 12/24/03
- Previous message: Tim Haynes: "Re: Port 135 Probes Continue"
- In reply to: Stuart Halliday: "Firewall definition"
- Next in thread: Lassi Hippeläinen : "Re: Firewall definition"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Wed, 24 Dec 2003 22:57:55 -0000
Yes, it is a byproduct of NAT's design and shouldn't be considered a
firewall nor used in place of one.
A firewall compares packets to a ruleset and drops (or allows) the ones it
matches, NAT does not provide such a mechanism. So outgoing traffic from an
internal network would be allowed (trojans, spyware etc.) with NAT, but not
with a well configured firewall.
Matt. Stevens
"Stuart Halliday" <stuarth@ecs-tech.com> wrote in message
news:3d57afa8.0312241417.2bdcbe59@posting.google.com...
> Is a NAT Router technically a Firewall?
>
> A lot of Router Manufacturers seem to list NAT as a Firewall feature
> when selling ADSL/Cable Routers.
>
> I say it's a byproduct of how NAT works rather than really a Firewall.
>
> I say to be a Firewall means its must actively probe packets, block
> suspicious ones and alert the user.
>
> A colleague says just a Router with NAT is a Firewall.
>
> Who's right? :-)
- Previous message: Tim Haynes: "Re: Port 135 Probes Continue"
- In reply to: Stuart Halliday: "Firewall definition"
- Next in thread: Lassi Hippeläinen : "Re: Firewall definition"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]