Re: Firewall RISKS

["Tim Kramer" <tkramer () irt net>]

You also might want to add:

8)  conducts business on the Internet and would like to limit employees access to specific resources (i.e., keep the 
employess conducting "official business" rather than looking at pornography or spending hours in a chat room)
9)  sends/receives e-mail or any sort of data to/from outside the company (possible virus infections).
10) is forced to trust the complete strangers that they hire.

-Tim Kramer -

MIKE SHAW wrote:

> These are security schemes and would be included in the word 'any'.  So let me define 'any situation' where a 
> firewall would be applicable:
>
> 1) uses a network LAN/WAN with TCP/IP anywhere in the architecture.
> 2) has machines present in the architecture with OS' that are difficult or impossible to completely lock down (which 
> is nearly all, especially with managers reading every day about how great NT is)
> 3) requires that a port or ports be open for functionality.
> 4) has actual services running on hosts/servers.
> 5) has end-users whose primary job does not involve network security (even if it is a secondary consideration).
> 6) has an interest in protecting information present in system(s) on that network or would be harmed by an abuse of 
> that network.
> 7) has a budget.