Unable to block Hoxx VPN

Hi Vineeth,

Can you check the application rule, based on the Screenshot, the policy is allowed.

Hi Eric,

It is already blocked in the applications filter. The VPN is using URLs (General Business category) for evading detection.

Hi Erick,

The application signature version is 18.19.54. 

I added a test FW rule on top. Hoxx VPN is still working. 

Hi rfcat_vk,

Yes, I have HTTPS scanning enabled. I can't install CA on end devices. I have a decryption rule for TLS/SSL inspection to block invalid certificates to block Hotspot Shield and Betternet VPN.

Gi, what are your public IPs? Also the firewall rules use the web proxy by the ticking of the scan boxes. At this stage ssl/tls does not scan UDP traffic, so what type of traffic is shown for the VPNs?

ian

The VPN is using TCP/80, and TCP/443. I think at this point DPI should be blocking the traffic. I enabled "Non-SSL/TLS traffic on port 443" and "VPN Over 443" blocking in the applications filter. Hoxx VPN is somehow able to evade the detection.

Hi,

you are not using DPI in the rule you have shown above as I explained. You will need to deploy CAs to enable scanning. You have don't decrepit enabled on your SSL/TLS rule so you can't see the applications inside the encrypted packets.

What are the external IP addresses you are using on your internal network and where are they assigned from?

Ian

Regarding external IP Addresses, I have a /24 which I am announcing using BGP and using them in my network. They are assigned by my router which has the DHCP server. 

Regarding application blocking, I meant applications filter which uses IPS app signatures for "Non-SSL/TLS traffic on port 443" and "VPN Over 443" should be blocking the traffic.

A few months ago, I had a client who tried to access VPN over TCP/443 once using OpenVPN. IPS was able to detect it and block it. Not sure what happened after I upgraded it to the latest version of the firmware. It never worked after that. 

You need a combination of ips and application policies at the very minimum and maybe web policies. Ips alone will identify  the application/web traffic but will not block it, that is a function of the application and web policies.

ian

IPS is unable to detect it. Earlier, OpenVPN wasn't detected when running it on TCP/80, and TCP/443 but after a signature update IPS started detecting it. I think the app signature is broken and needs to be fixed for "Non-SSL/TLS traffic on port 443" and "VPN Over 443".

IPS will not be able to detect it unless it can look inside the encrypted packets because the encryption starts on your client PC and the data within the packet is opaque to the xg unless you install a CA which will allow the XG to examine the packet contents. All IPS will see is a source and destination connection using 443.

Ian

IPS will not be able to detect it unless it can look inside the encrypted packets because the encryption starts on your client PC and the data within the packet is opaque to the xg unless you install a CA which will allow the XG to examine the packet contents. All IPS will see is a source and destination connection using 443.

Ian