Re: Outbound ports

From: David (davidwnh_at_adelphia.net)
Date: 10/22/03 

Date: Wed, 22 Oct 2003 19:06:00 GMT

You set up filters that allow inbound from the high ports to the
specific service ports and that allow outbound from the specific service
ports to the high ports.
>
>
> How are people going to use it, then? Destination Port 80 outbound
> means that you allow people ON your webserver to surf to other
> webservers ;-)
>
>

It applies to any firewall that allows for this type of filtering. Many
personal firewalls allow for this type of filtering.
>>If you block outbound ports, except the ones you actually need, you
>>limit what things your computers can do should they become
>>compromised.
>
>
> Caveat: This only applies for real firewalls, not "Desktop Firewalls".
>
>
>>For instance, if you don't allow 135~139, 445, and 8 outbound you
>>don't have to worry about people making standard windows share
>>connections to machines on the internet and you don't have to worry
>>about your machines pinging them either.
>

You could always change the setting for the small amount of time that
you might spend troubleshooting a connection.
> Not to mention that it would be rather stupid to prevent your own
> machine from pinging others - how do you troubleshoot connections
> without ping?
>

Relevant Pages

  • Re: Netscreen 5GT for home network?
    ... > the limited outbound control available on the Linksys, ... > like to have some content filtering available. ... > DHCP ... > puts all 4 ports into one security zone called Trust. ...
    (comp.security.firewalls)
  • Re: UDP Scanning - how nmap really works
    ... > Seen as this method cannot be used, it does not seem feasible for nmap to generate any meaningful information in this ... > situation yet somehow it is differentiating between filtered and open udp ports. ... So how does it match PORT_FIREWALLED in UDP scanning? ... and still is marginally useful in internal networks with no filtering going on. ...
    (Pen-Test)
  • Re: How block socket ports
    ... I would advise against the IPsec filtering that comes with Windows 2000 as ... install all microsoft security patches, sign up for the microsoft newsletter ... on ports basis. ...
    (microsoft.public.win2000.security)
  • Re: IPSec: Network sooo slooooow
    ... > to use ipsec filtering to secure domain controllers. ... > to the Windows 2003 Security Guide. ... > that are not in the same forest, all of the preceding ports for Windows NT ...
    (microsoft.public.windows.server.networking)
  • Firewall Identification via nmap SYN, Stealth FIN, Xmas Tree, and Null scans
    ... me) is filtering traffic on the target network. ... I was wondering if there were any ways of identifying the firewall ... Here's the data set I'm working with (6 common TCP ports), ... 80/tcp filtered http ...
    (comp.security.misc)