Updated: December 20, 2018
Lock down mode was designed to block all network connectivity (except for a few core features) when the end user is not connected to the Pulse Connect Secure device. For more information about the behavior, please refer to KB40363 - Behavior of "Lock Down this connection" (also known as Lock Down Mode)
As of December 2018, Pulse Secure does recommend the following software releases and deployment guidelines with lock down mode:
- Deploy Pulse Connect Secure and Pulse Desktop Client (PDC) 9.0R3 (lock down exceptions rules were added with PDC 9.0R2 for both macOS and Windows)
- Pulse Desktop Client should be deployed with one connection. If multiple connections are needed with VPN Only Access, please refer to KB43981 - VPN Only Access with resolvable address (location awareness rule) with more than one connection will cause the lock down firewall to start after the VPN tunnel is created with Pulse Desktop Client 9.0R1 / 5.3R6 and below
- Third-party applications that require network connectivity prior to the VPN tunnel being established, Pulse Secure recommends to add the network range or application to the exception list.
For more information, please refer to KB43665 - Lockdown mode exception rules feature
Below is an on-going list of known third-party applications that may have issues when lock down mode is enabled. Please continue to monitor this article as we will continue to add to this list as new issue are discovered.