|
|
|
|
|
|
|
|
 |
 |
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [FW1] Firewall names
Hello Brian: Well, it all depends. If it is just the hostname, it is probably no big deal. If it is associated with an IP address that is advertised to the world via DNS, then it would be just asking for trouble. There is no reason to draw attention to your firewalls. IMHO a firewall should be a black hole to the outside world. If your customer wants to associate the name with an IP address on the secure network that is not advertised to the world, that would not be the end of the world, but keep in mind that most security incidents originate from within the organization. Regards. Bob Webber AT&T Global Network Services Tel:Fax:Notes: Bob Webber/Markham/IBM@IBMCA Internet: [email protected] "Logic merely enables one to be wrong with authority" - Doctor Who "Brian Mulford" <[email protected]>@lists.us.checkpoint.com on 02/28/2001 01:14:14 PM Please respond to "Brian Mulford" <[email protected]> Sent by: [email protected] To: "Check Point FW List (E-mail)" <[email protected]> cc: Subject: [FW1] Firewall names Everyone, I have a client that insists on naming firewalls FW1 and FW2 or Firewall1 and Firewall2(NT machines). I advised that its not good practice to name firewalls anything that could indicate to the outside world that this is indeed a firewall. Am I off the wall think that? Brian ================================================================================ To unsubscribe from this mailing list, please see the instructions at http://www.checkpoint.com/services/mailing.html ================================================================================ ================================================================================ To unsubscribe from this mailing list, please see the instructions at http://www.checkpoint.com/services/mailing.html ================================================================================
|
||||||||||
 |
 |
 |
 |
 |
 |
 |
 |
 |
|
