I have two access rules to enable certain applications to access certain domains to access datastreams. These rules are configured to allow access for all users to specific domains defined in domain name sets. Only http protocol is allowed. I am testing an IronKey(TM) for potential rollout as a corporate standard. This device is a USBKey with hardware encryption and inbuilt Firefox browser to allow secure (and private/anonymous) web browsing. In my tests, have noted in the ISA logs that there are connections allowed by both my Domain Name Set based rules to several IP addresses which the firefox browser uses while setting up the secure channels. These connections are logged with no url so I presume the host header is set to an IP address. According to http://www.isaserver.org/articles/isa2004_accessrules.html the rule should fail as the http protocol is matched to the domain set using host header fields and, in these cases, the reverse lookup certainly does not resolve to the domain name set (as tested via nslookup on a client).
Any ideas as to why the rule allows the connection?
Thanks
Andy
EDIT: just checked that the problem also applies when a Domain Name Set is replaced by a URL set
|