Well, from a firewall perspective, 1-65535 are all about equally
vulnerable.
A handful of ports may offer compelling business reasons why the
risk must be taken. Sometimes the risk can be mitigated by
restricting the addresses that may use the port.
IOf you don't know what a port is used for, it should be blocked.
If you know, you should probably still block it unless you know your
users *need* to be able to do that.
David Gillett
On 15 Jun 2001, at 10:04, Meghna Reddy wrote:
> Dear all,
>
> Does anyone have a comprehensive list of vulnerable
> ports which a firewall admin would never open in his
> f/w. Even a URL that holds this information would
> suffice.
>
>
> Regards.
>
> __________________________________________________
> Do You Yahoo!?
> Spot the hottest trends in music, movies, and more.
> http://buzz.yahoo.com/
> _______________________________________________
> Firewalls mailing list
> [EMAIL PROTECTED]
> http://lists.gnac.net/mailman/listinfo/firewalls
>
_______________________________________________
Firewalls mailing list
[EMAIL PROTECTED]
http://lists.gnac.net/mailman/listinfo/firewalls
