It would be very nice if Let's Encrypt certificates (letsencrypt.org) can be generated directly from the XG Gui. So that the "Let's Encrypt Client" is integrated in the XG. Would it be possible?
Best Regards

At the moment there are different type of authentication missing even on UTM9 against ISA server 2006, such as:

1. Two-factor authentication using forms-based authentication and a client certificate.


2. Delegation of credentials by using NTLM or Kerberos authentication.


3. Kerberos constrained delegation.


4. Secure Sockets Layer (SSL) client certificate constraints

In this way, XG and UTM9 are the very alternative to ISA Server.

Many small installation could benefit from ability to publish User Portal using Business Rule instead of enabling it directly in Device Access section. The difference is that a single IP can be used to host both User Portal and custom Web applications such as Web mail, Web storage, Web cameras, etc.

Now, the only solution is to change User Portal listening port to something non-standard but this limits the ability to use it from some network environments where only standard WWW ports (80,443) are allowed.

Migrating from TMG 2010 server to XG 330. Currently, have a few websites, like OWA, remote desktop, etc...that we require 2 factor authentication. Would be great if WAF rules supported OTP authentication using the built in OTP product. Was told by support this is not possible. Thanks.

Same idea as http://ideas.sophos.com/forums/17359-utm-formerly-asg-feature-requests/suggestions/6101344-url-redirection for the UTM. We need the ability to redirect URL requests.

For example:

http://email.mydoamin.com -> https://email.mydoamin.com/owa

On HTTP/S NLB I would like to have more features, such as:

Weighted roud-robin

Weighted least connection

Hash based on Source/Destination IP

Hash based on Cookies

Hash based on Header/URL

Thanks

Allow IPv6 (and IPv4) for WAF

our customers are asking for the http/2 Support for there webservers, please add the http/2 Support to the WAF - Webserverprotection

Other UTM/WAF vendors integrate virtual patching features on their product. A really brute force protection in missing on WAF too.
Please add it.

Please add support for HSTS, HTTP Strict Transport Security on sophos XG WAF

Recently we have create a new ticket with Sophos support (#9307623) and they confirm that 'at a time a user would be part of one group'. It leads us to the hard way when having 2 websites which are needed to be authenticated with 2 domain groups, and from them, we have multipla users who are belonged to these 2 groups as well. Therefore, we can not separate to authencate these ones properly.

I suggest Sophos should improve this feature to make customers easy to configure many authenticated websites appropriately.

Thanks.

Allow the use of wildcard domain names for Webservers. Also allow them to be sorted in priority so that a more specfic FQDN takes precidence over a wildcard domain.

Please provide the option in the Reverse proxy to enable encodedslashes for a specific virtual webserver.

Because some web applications use for example %2F for a slash and the reverse proxy cannot translate this back to / because of allowencodedslashes is not enabled by default. So this results in a 404 error.

http://httpd.apache.org/docs/current/mod/core.html#allowencodedslashes

This is essential for Web Applications like SAP Fiori! I think we not the only company who have this issue.

Team, This request is to include the actual signature ID being invoked in the GUI WAF logs. Including this will assist us when figured out which rule to bypass, if needed.

Many of the sites nowadays are behind CloudFlare. It would be great to have an option to inspect and see the real IP address in the WAF logs / Reports.

It will be like 1 raw entry in the Apache configs!

You had support for Remote Desktop Gateway protocoll (Windows 2008 and 2008 R2) implenented. In the state of the art fw, the modern OS (Windows 2012, Windows 2012, Windows 2019) is not supported for some protocolls.

Hello Team,

Asking assistance if we could be able to add Certificate-based Authentication for web server protection. We have customer here needing this as requirement on their set up.

Version 18 has changed how Business Application Rules work. DNAT is done by a combination of NAT policy and regular firewall rules, which can have scheduled on/off times.

WAF/Webserver Protection rules cannot currently be associated with schedules.

This item is created so that folk who previously supported the Business Rule schedule feature because of a WAF requirement can transfer their votes here.

Currently, the ability to customise the Webserver Protection block page messages is not present.

When the WAF (Web application Firewall) blocks a page, it returns 'page cannot be display'. This should be customisable.

The AntiVirus engine on the WAF should also be customisable on the block page returned.

Provide the facility to publish sub-directories in path selection as well as static 'web server'. This is useful for many different reasons and has traditionally been known as proxy pathing. This allows a user to enter an FQDN and to have that transparently connect to a sub-directory of the web server. Also, it allows virtual directories of a single FQDN to transparently map to different sub-directories of the same server, or even a different web server entirely.