Login security issues:
- ISA 2006 can upgrade connections to HTTPS when authentication is required, but it does not support downgrading from HTTPS to HTTP after an authenticated session has been securely established.
- Using HTTPS for all parts of your published infrastructure may cause unacceptably high CPU usage on your server, or require the purchase of several certificates.
- There is no easy way to use ISA link translation to force certain links from HTTP to HTTPS (or vice versa).
Solution
PageGuard from Collective Software augments the capabilities of ISA 2006 to allow HTTP site publishing with HTTPS authentication. PageGuard integrates into ISA to seamlessly solve protocol redirection, without resorting to scripts or other changes on your web servers.
Features
- PageGuard can protect the authentication dialog on a dual HTTP/HTTPS listener and require login over HTTPS, without requiring all parts of the site to use HTTPS.
-
PageGuard can specify certain publishing
rules, URLs, and/or file extensions that should always be served
over HTTPS. This flexibility allows you to protect certain content
or pages such as:
- Sensitive documents
- Secondary login forms of your internal servers that should be served over HTTPS when being transmitted over the Internet.
- PageGuard can specify certain publishing rules, URLs, and/or file extensions that should always be served over HTTP. This allows you to “force” connections to go to HTTP after authentication is completed, or after an HTTPS page has been viewed.
Powerpoint slides from sales presentation
Download PageGuard documentation
Download PageGuard v1.0.5 (evaluations must be activated in 30 days)
Purchase PageGuard licenses online
PageGuard knowledge base articles