j2004
Posts: 3
Joined: 24.Oct.2004
Status: offline
|
quote: -------------------------------------------------------------------------------- Originally posted by <Wolfgang>: I know that for security reasons, the ISA server must be a Domain Member.
But, in my case, I have a slight different environment.
The users connect to my ISA server through a Cisco pix firewall into a DMZ (where the ISA server is). We haven't enabled the domain membership on the ISA Server because I understand that is a security issue to have a domain member in a DMZ.
In this particular scenario, what solutions I have to begin logging users? I have to use another ISA server? perhaps making an Array?
Thanks for your time! --------------------------------------------------------------------------------
Hi Wolfgang, That's a very interesting deployment, a back to back firewall config with the ISA firewall in front. While its a valid config, you should bring the more secure firewall, the ISA firewall, closest to the core assets, and let the PIX packet filter just use its packet filter features to filter out the "junk" traffic.
Thanks! Tom
-
Tom, Have you considered that if this person is using isa in cache mode only etc. and doesn't need the other isa features (when used as firewall, publising box) hence doesn't care less for having it a domain memeber ? there is nothing wrong with having caching proxy server in a DMZ Tom, 1. In fact its excellent practice if it is to serve other networks aswell and doesn't need to be a member of the internal domain. 2. it can be well hardened aswell by disbling uneeded services, and hence also knows very little stuff about inside networks for any potential compromise to extract. I have deployed many Squid Box's in a DMZ in this scenario, now that ISA2004 can do radius auth for this type of proxy deployment many admins may migration from Squid to ISA2004. Its actually a very common scenario.
The guy just asked if the logging is still as good when setup this way, a good question. I suggest you just anwser the question instead of telling the poster how to design their network.
Sorry if this sounds like flaming, remember not everyone's environment is how MS or you want it to be. Example, many organisatiosn don't publish anything, and never will as they have no need, accept perhaps for smtp, in this case the PIX has a proven application smtp filter that can be attached to another external registered ip address/dns mx for publising to the inside box, and often a proxy server is placed in the dmz, so it can serve more than just a MS network behind the pix, with ISA2004 being able to authenticate using radius and perhaps better logging facility because of this feature, this is an attractive scenario for many organisations as this ins't t as easy to do on on standalone proxy servers.
regards
julian [ July 10, 2005, 09:58 PM: Message edited by: j2004 ]
|