I decided to write a description of my firewall policy today. I have been tweaking it again to get the RSS Reader webpart to work. I think if I write it out I will better be able to see any logic errors.
General Firewall Policy Description
- Allow computers in the local domain complete access to other computers in the local domain.
- Deny inbound access from the internet.
- Allow computers in the local domain anonymous outbound access to the internet with the following protocols:
- Authenticate the user using Windows integrated authentication for IP protocols other than the ones listed above.
- Minimize the downloading of advertising and sexual content.
Firewall Rules and Implementation
- Direct Access Rule Direct access to computers in the local domain is granted via the proxy client configuration for the web browser.
- Default Inbound Access Rule – Inbound access from the Internet is denied by the ISA firewall by default.
- Protocol rule #1 If the client is from the local domain, anonymous outbound access is granted to the Internet for the normal protocol set, HTTP, HTTPS, FTP, POP3, SMTP, and NTP. Almost all internet access will go through this rule.
- Protocol rule #2 If a client requires access to an IP protocol outside of the normal protocol set, that client must be authenticated using windows integrated authentication.
- Site and content rule #1 – Deny content from known advertising websites listed in the No Ads destination set and redirect the link to a local web page. This rule increases bandwidth by reducing the amount of unnecessary content being downloaded from the internet.
- Site and content rule #2 – Deny content from known sexual websites listed in the No Sex destination set and redirect the link to a local policy web page.
- Site and content rule #3 Allow clients from the local domain access to all domains that have not been explicitly denied.
- Do not authenticate outbound listener. I think this is a temporary fix to get the RSS reader webpart to work and requires that the web.config have a <defaultproxy> statement. This is opposite of what the folks at www.isaserver.org recommend but their recommendation does not work for my server. All http connections end up being anonymous but I don't care.