John,
> Does it make sense to split the work between traditional departments
> (IE. midrange, security, and teleco)?...
I will say no. If the work is split amongst several departments, there may
be conflicts as to who has authority to make changes. Modifications may not
be well coordinated and may take longer to implement. This may spell trouble
for the company. There may be other non-technical (political) issues that
may not bode well with sharing of responsibilities.
My advice would be to have one group be responsible for the firewall. If you
must share responsibilities you could have one group do the design while a
second do the implementation based on the design. This way you spread the
knowledge, which may cause job satisfaction, and improve productivity.
My two cents.
Regards,
--------------------------------------------------------------------------
Sunny Azah - sazah @
ibu .
sj .
nec .
com
Internet Business Unit, Home of the PrivateNet
NEC Technologies, Inc.
110 Rio Robles San Jose, CA 95134
Tel:(408) 433-2161 FAX:(408) 433-1230
http://www.privatenet.nec.com
--------------------------------------------------------------------------
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Date: 13 Nov 96 21:41:22 EST
From: John Madincea <71333 .
2026 @
CompuServe .
COM>
Sender: firewalls-owner @
GreatCircle .
COM
Precedence: bulk
I am looking for input (PROS's and CON's) regarding how firewalls are currently
being supported
within large organizations. Does it make sense to split the work between
traditional departments (IE. midrange, security, and telecom) or is the worked
better served from within one department ? I know that
a lot of this would depend on the skill level of those involved. However, Im
not looking for replies like
that. Im trying to get views on how this has worked (or hasn't worked) and what
you would suggest
if you had the luxury of starting from scratch. Any detailed information on why
you recommend one method
over another would be greatly appreciated.
Thanks in advance,
John Madincea
71333 .
2026 @
compuserve .
com
References:
|
|
