Heather
Take a look at the report referenced on this page. (7 firewalls fit for your
enterprise). Alternatively go to network computing and search the features
archive. It depends on what you want but we are planning to use the Raptor
Firewall and not the PIX.
We already use the PIX for an internal firewall but its just too darn
tricky to write rules. And when you do write them you have to maintain the
order, and no-one else can easily understand them. Also when you want to
modify a rule you have to delete it, modify it and re-insert it. The PIX may
be fast but its darn hard to manage.
We currently use Raptor for the internet access and its straightforward to
write rules based on interfaces, subnets, groups of users, individual
machines. Furthermore you can modify a rule, or add a rule, look at it,
check it and then commit it. You can't do this on the PIX.
The only thing that concerns me at the moment is how fast Raptor will be
handling VPNs.
http://www.axent.com/product/rsbu/firewall/default.htm
Ray
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]
Sent: Friday, May 14, 1999 1:06 PM
To: [EMAIL PROTECTED]
Subject: Cisco PIX Implementation
Firewall gurus,
Need some advice. We're getting ready to move from an Eagle Raptor
firewall to a Cisco Pix firewall solution. As part of this process, we'll
be installing the NetRanger detection product.
Any tips or tricks you all can give me on the new products? Strengths,
weaknesses, etc.?
Thanks in advance,
Heather White
Sr. Security Risk Analyst
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]