KB44783 - Pre-approving Pulse Secure's System Extension/Network Filter policy approval dialog popup when Traffic Enforcement is enabled on MacOS Big Sur via MDM payload
KB44592 - Pulse Desktop Client for macOS Open Issues on Big Sur
KB44631 - After upgrading to macOS 11.0 (Big Sur), end users may receive Error 1205 "Failed to setup virtual adaptor" when Traffic Enforcement or Lock Down Mode are configured
KB44688 - Availability of FIPS compliant Pulse Desktop Client for Windows/macOS from 9.1R11 onwards.
KB44521 - macOS Big Sur (11.0) Support
KB44617 - Pulse Desktop Client On MacOS Takes A Delayed Time To Load
TSB44876 - On some macOS endpoints, it is observed that the Pulse Desktop Client & browser based applications are affected.
KB44898 - Basic Paths and troubleshooting in Mac OS respective to PSAL and Pulse Desktop Client features
KB44809 - PSAL behavior on MAC OS Big Sur
KB44015 - End users may observe kernel panic or Pulse Desktop Client crashing issues on macOS 9.0 and above with Pulse Desktop client version 9.0R1 - 9.0R3.1 installed
What would you like to know?
< Back to search results
KB44608 - Traffic Enforcement Network Content Filtering behavior in MacOS from Pulse Desktop 9.1R8.2
Last Modified Date
10/21/2020 5:39 PM
Traffic Enforcement Network Content Filtering behavior in MacOS from Pulse Desktop 9.1R8.2
After upgrading to 9.1R8.2 and enabling Traffic Enforcement on a MacOS platform, a popup message will appear notifying that Pulse Secure will be filtering Network Contents.
Problem or Goal
After upgrading to 9.1R8.2 and enabling Traffic Enforcement, MacOS platform receives a popup message regarding Pulse Secure will be filtering Network Contents.
This is an expected behavior with system extension introduced in 9.1R8.2 release. Pulse uses the 'Content-filter-provider' entitlement to filter the traffic.
Fore details about entitlements, refer to
Pulse cannot avoid / bypass the 'Content Filtering' prompt.
The 'Content Filtering' notification will only show once.
However, customers can try to whitelist the Pulse Secure system extension. To whitelist the Pulse Secure extension, see the Pulse Secure TeamID and bundle ID using
This can be done for any MDM provider; JAMF being one of them.
Was this article helpful?
Please tell us how we can make this article more useful.