1/4
Blocking VPN Usage for The LAN Users

xonivre Lv1  Posted 2026-Sep-26 15:20

Hello Sangfor Expert,

I need assistance with blocking VPN usage for our LAN users.

I created an Application Control policy with the following configuration:

Source Zone: LAN
Source Address: Our LAN network
Destination Zone: WAN
Destination Address: All
Application: Proxy Tool
Action: Deny

However, users are still able to access the Internet using Proton VPN and other VPN applications.

Could you please advise me on the recommended configuration for Sangfor NSF-1100A-I to effectively block VPN applications and prevent users from bypassing our Internet access-control policies?

Any guidance regarding the appropriate application categories, services, protocols, or additional policies that should be configured would be greatly appreciated.

Thank you for your assistance.

Muhammad Abid has solved this question and earned 20 coins.

Posting a reply earns you 2 coins. An accepted reply earns you 20 coins and another 10 coins for replying within 10 minutes. (Expired) What is Coin?

Enter your mobile phone number and company name for better service. Go

For your Sangfor NSF-1100A-I, blocking only Application = Proxy Tool is usually not sufficient. Sangfor's own guidance recommends selecting the VPN-related application categories/signatures, and current Application Control policies require both Services and Applications to be specified for the rule to match.

Recommended configuration

Create a dedicated policy:

Policies → Access Control → Application Control → Add

Setting        Recommended
Source Zone        LAN
Source Address        Your LAN subnet
Destination Zone        WAN
Destination Address        All
Services        Required services / VPN-related protocols
Applications        All VPN / Proxy Avoidance applications
Action        Deny

Logging        Enable

For Applications, don't select only Proxy Tool. Look for categories/signatures such as:

VPN
Proxy / Proxy Avoidance
Anonymous Proxy
VPN Client
Specific VPN applications, including Proton VPN, where the signature exists
Other tunneling/anonymous-browser applications

Sangfor's community guidance specifically recommends selecting all VPN categories rather than relying on a single Proxy Tools signature.

Also control VPN protocols

Depending on your Sangfor version, create/deny appropriate services for protocols commonly used by VPN clients, such as:

IPsec / IKE
PPTP
L2TP
OpenVPN
QUIC/UDP-based traffic, where appropriate

Be careful with broad protocol blocking because some legitimate business applications can use the same protocols.

Important: check QUIC

QUIC can allow applications to use UDP instead of normal HTTPS/TCP inspection. Sangfor's current documentation explicitly notes that applications such as YouTube may use QUIC and that the relevant protocol should be included in Application Control when necessary.

If Proton VPN is still working, check the traffic/application logs while Proton VPN is connected. The key question is:

What application/protocol is NSF actually identifying that traffic as?

If it is showing as Unknown, HTTPS, QUIC, or another generic application rather than Proton VPN/VPN, your Proxy Tool → Deny rule may never match it.

SSL Decryption

For HTTPS-encrypted traffic, consider enabling SSL/TLS inspection/decryption where appropriate. NSF supports outbound SSL/TLS inspection, including TLS 1.3.

Without inspection, some VPN/proxy traffic can be difficult to identify at the application layer.

If users are deliberately bypassing detection

For stronger enforcement, Sangfor's Endpoint Secure + NGAF/NSF Application Containment / Proxy Avoidance Protection is specifically designed to identify VPN/proxy applications running on endpoints and enforce blocking policies.

So I would use this approach:

1. Block VPN/Proxy application categories
2. Block relevant VPN protocols/services
3. Control QUIC where required
4. Enable SSL inspection where appropriate
5. Keep application/IPS signatures updated
6. Check logs while Proton VPN is running
7. If endpoint VPNs still bypass detection → Endpoint Secure/Application Containment

One important point: don't simply block TCP 80/443 for the LAN, because normal Internet access depends heavily on those ports. Instead, use Application Control, protocol controls, inspection, and endpoint enforcement together.

If you give me your NSF-1100A-I firmware version and a screenshot of Policies → Access Control → Application Control → Add, I can tell you exactly which Applications and Services to select and in what policy order for your version.
Is this answer helpful?
Newbie006434 Lv2  Posted 2026-Sep-26 23:51
  
Thanks for sharing this solution, really helpful! The part about enabling SSL inspection for VPN blocking is key. I was also stuck on Proton VPN bypassing policies, this explains it perfectly.
Andre Agave Lv2  Posted 2026-Sep-26 22:28
  
For effective VPN blocking on NSF-1100A-I:
✅ Block all VPN-related application categories, not only "Proxy Tool"
✅ Enable SSL Inspection / SSL Decryption
✅ Block common VPN protocols (OpenVPN, IPSec, PPTP, L2TP)
✅ Keep Application & IPS signatures updated
✅ Review traffic logs to identify undetected applications
✅ Integrate with Endpoint Secure for advanced anti-VPN protection
If Proton VPN is still bypassing the policy after these recommendations are applied, please provide:
•NSF firmware version
•Screenshot of the Application Control policy
•Application Control logs when Proton VPN is connected
•Traffic log entries for the VPN session
We can then verify whether the traffic is being identified under another application signature or requires additional SSL inspection configuration.
Newbie900829 Lv2  Posted 2026-Sep-26 19:22
  
Hi,
To block Proton VPN on NGAF-1100A, just blocking "Proxy Tool" is not enough.
Please do this:
1. Update App signature to latest.
2. In Application Control policy (LAN to WAN - Deny), add: *Proxy Tool, VPN, Anonymizer* categories.
3. Enable *SSL Content Inspection* - without it VPN bypasses easily.
4. Block *UDP 443* and *DoH/DoT* in App Control to force normal DNS.
5. Put this deny policy on TOP.

After that, clear sessions and test.

Thanks.
Newbie380273 Lv2  Posted 2026-Sep-26 16:45
  

Hi Sir,

Your current policy is correct but incomplete. Proton VPN uses Stealth and TLS tunneling, so it will bypass if you only block "Proxy Tool".

On NGAF M1100-A / NSF-1100A you need to do this combo:

1. Edit your Application Control rule and add the full VPN Category. Don't add single app. Add: VPN, IPSec-VPN, SSL-VPN, Proxy, Anonymizer, ProtonVPN, NordVPN, ExpressVPN, Shadowsocks. Set Action to Deny and place it on top priority.

2. This is most important: Enable Decrypt / SSL Inspection. Go to SSL Inspection -> Enable SSL Decrypt for Application Control. Without decrypt, NGAF cannot detect Proton VPN because it runs inside HTTPS.

3. Block QUIC - Proton uses QUIC to bypass. Go to Application and add QUIC -> Deny.

4. Block DoH - Users bypass DNS filtering via DoH. Block Application "DoH / DNS over HTTPS" and create a firewall rule: Allow DNS only to your internal DNS, Deny all other UDP 53.

5. Update your Application Signature Library to latest version.

After config, do Diagnostics -> Clear Sessions and test again.

This combination will effectively block VPN on LAN.

Thank you.

I Can Help:

Change

Moderator on This Board

1
160
3

Started Topics

Followers

Follow

1190
263
101

Started Topics

Followers

Follow

Board Leaders