will there be a feature like Authentication / captive portal (e.g. the proxy settings"transparent with authentication" ) for enabling a reverse proxy?
This would be so usfull for small installations with no frontend exchange / DMZ.
(juniper calls this "webauth" )319 votes
We are hard at work on this feature and will deliver the first implementation of front end authentication as part of our Web Server protection (reverse proxy) in UTM 9.2. The public beta will begin in October. Stay Tuned!
One of the most important problems of the website users is, when they want to open the page that is HTTPS, they forget to type HTTPS at the beginning of the address and the request is sent via HTTP. Therefore they can not view the page successfully. If the "URL redirection" feature will provided on Sophos UTM or WAF it is possible to automatically redirect all HTTP requests to HTTPS before the request reaches to the real web server. This will solve the problem of the website users.260 votes
A mix up in communication resulted in this feature being tagged as completed. It is in fact something we will release in UTM 9.2, so it will have the status changed back to “planned” and we will updated you again when the feature is implemented in UTM.
WAF doesn't support ActiveSync 14.1, i.e. after you install SP3 for Exchange 2010, you can't use use WAF to protect your ActiveSync Server anymore. This is poor.134 votes
I would appreciate to support certificate-based authentication like at Microsoft TMG. I don't know why Sophos is making advertisements for "Replace your TMG with Sophos UTM" if UTM even can't do this! I want the reverse proxy to check a client certificate, If this certificate is not valid or it doesn't exists it shows an error page.110 votes
Astaro 8 now supports an HTTP reverse proxy, but it is not as feature rich as it does not allow for custom configurations. 10.0.0.1:5449/ ProxyPassReverse /director2/ http://10.0.0.1:5449/
Since the Apache reverse proxy service is already configured for mod_rewrite, among other things, simply having a way to include these settings in an advanced section or via the command-line is all that may be necessary.103 votes
It would be great, if you could add " *.domain.com " in WAF.
So that you dont need to add every single FQDN for every site.89 votes
This feature will be included as part of UTM 9.2 which will enter beta in September 2013. Stay tuned!
we are hosting a SignalR hub (http://signalr.net/) behind a Sophos UTM 320. We use the Web Server Protection feature extensively in our environment, and as such have opted to use the same for this.
SignalR will always try to use Web Sockets (http://en.wikipedia.org/wiki/WebSocket), a new HTML5 API, and fallback to other technologies where this isn't possible to be used.
Since we've been hosting the hub via the reverse proxy, none of our clients are able to connect via Web Sockets :so having support for websockets in WAF would be super cool72 votes
Please provide the option to use reverse proxy also with transparent mode. This way permits to have the real remote host IP traced on the web server log files instead of the IP of the firewall. Now without transparent mode, every web analyzer software is not able to give real traffic reports...54 votes
I would like to see an option to deny or allow certain ip adresses that can access the webservers. Not only based on country but on the ip adres itself.44 votes
For web sites with larger uploads (e.g. ownCloud) there is currently a 128MB (134217728 byte) limit in Web Server protection, the so called request body limit in ModSecurity.
Please add the possibility to configure this parameter (it's "SecRequestBodyLimit" in the Apache config) to allow larger uploads to sites protected by WAF.39 votes
The WAF strips the Accept-Encoding header from client requests, which is fine, as compression is not generally useful between the origin server and the proxy. However, it doesn't use the header itself, either. It doesn't compress proxied traffic before returning it to the client. Interestingly, pages generated by the WAF itself (such as error documents) are compressed. Only the proxied content remains uncompressed, and this can have a substantial impact on page speed.38 votes
Equal as Outlook Anywhere Remote Desktop uses RPC requests. In the meantime Outlook Anywhere is supported officially by UTM 9.1 So I hope the effort for the develovers will be small to implement it as well. I think the advantage will be huge for many of use, because many customer ask for it.36 votes
Support for form to form authentication with one time passwords in the WAF.
The WAF should be able to pass authentication through to a website which authenticates using a form (as opposed to only basic auth) if there is configuration on the UTM that defines the URL to the page which can process the login (not the login form) and the field names for the username and password.29 votes
Similar to support for Outlook Anywhere, it would be really beneficial if the WAF allowed for the publishing of Remote Desktop Gateway and handled those methods. RDG_OUT_DATA followed by RPC_IN_DATA and RPC_OUT_DATA, and including /RemoteDesktopGateway in the request. It seems like common functionality that many customers must be looking for...26 votes
Enable Web Application Firewall support to specify cipher strengths it can accept. Either cipher-by-cipher basis or on a weak/med/strong cat
Enable Web Application Firewall support to specify cipher strengths it can accept. Either cipher-by-cipher basis or on a weak/med/strong category.25 votes
The strong security features like URL-hardening, cookie-signing and form-hardening are still not available with owa newer than 2003. The knowledgebase just told me, to deactivate those feature. But they are important for higher security level.24 votes
When using ASG to terminate SSL sessions (SSL Offloading), it’s sometimes needed to get the client certificate (mutual authentication) and pass some SSL info such as SSL Session IDs and Client-SSL Certificate information (e.g. certificate fingerprint and serial number) inside HTTP header to be used and processed by the protected web applications.
An example of this use; let’s assume that I have a plain-text web application with certificate-based user authentication, so, it’s necessary to have such features in my WAF appliance.23 votes
Please implement the ability to restrict access to specific paths on a website to defined source IP's. Usually this has been done on the webserver, but NAT'ting of the Webserver Protection breaks this feature on webservers (sees the internal IP of UTM instead of public source IP).
Website globally allowed
path /administrator only allowed to defined source IP's
Partner hosts a private company Website - should anly be accessible from Company public IP's
path / only allowed to defined source IP's17 votes
Add Email and SNMP Notification for Web Application Firewall (HTTP/S Reverse Proxy) when the ASG found a Virus in Web Application Firewall traffic.
This is very useful for the Network Administrator to find any Security holes.14 votes
There are many situations where a Web application needs to know whether the original connection was made over HTTPS or HTTP. Typically, SSL proxies communicate this by inserting the X-Forwarded-Proto header into the request. Currently, the ASG only adds the following headers:
- Don't see your idea?