charlie66 -> RE: TrendMicro gateway products. . . (14.Dec.2004 12:14:00 AM)
|
My configuration is as you assume:
CLIENT (HTTP request) > IWSS > ISA server > WEB SERVER.
I use web proxy, and clients are pointed to IWSS in their proxy settings.
The following is copied from the install and config guide (p. 41):
"If you are using the HTTP proxy, you can configure it to function in stand-alone mode (no upstream proxy) or in dependent mode (with upstream proxy)."
Actually, I tested your configuration also a while ago - it's more intelligent since you scan content once and serve it to many users. The downside is that in order to have max. security, you need to clear the ISA cache whenever the pattern files are updated (several times a week, sometimes several times a day). Trend does offer the ICAP mode for this scenario (but ISA 2004 is not ICAP compliant).
I didn't see any issues with this config though, but again using web proxy only, and having the client proxy point to ISA 2004 (or using wpad entry).
Authentication and logging would have to take place on the IWSS (we don't use authentication and logging is done only on the IP address). Logging on ISA 2004 would have all requests to come from the IWSS server (but still usable for performance, cache hit ratio etc.).
But you should be able to use e.g. LDAP for authentication on the IWSS. I think the KB article deals with v. 1.0.1 where this feature was not available (but I haven't tested it). And IWSS does have some very nice and extensive logging and reporting facilities.
And I too would assume the IWSS box would have to be on your secured network, mine certainly is. [ December 14, 2004, 12:15 AM: Message edited by: soren ]
|
|
|
|