Your request for Endpoint Protector was sent!
One of our representatives will contact you shortly to schedule a demo.
Free, custom demo to suit your needs
One of our representatives will contact you shortly to schedule a live demo. We'll answer questions, address your concerns and tailor the demo to your needs.

* We don't share your personal info with anyone.
Check out our Privacy Policy for more information.
Please use a valid email address!
Thousands of global clients
already use our product
Trusted by companies of all sizes, from all industries. Fortune 500 companies, Universities, Governments, Banks, Media, and more.
Join them
Endpoint Protector Knowledge Base

Below you can explore FAQs related to Endpoint Protector and find the information you need. For any other additional questions, suggestions, and improvements please contact the support team.

Why isn’t DPI inspecting content when VPN add-ons are installed on browsers?

Endpoint Protector is an endpoint DLP solution. As such, content inspection occurs on the endpoint, when a monitored application accesses a file that is being monitored for content (using custom content dictionaries, predefined content, regexes, etc.).
With the introduction of the Deep Packet Inspection functionality, an additional content inspection mechanism that inspect the packets sent to the network is also available. As an enterprise solution, the DPI feature within Endpoint Protector is designed to work in scenarios where only corporate VPNs are used. Such VPN solutions provide various configuration options that can be utilized by a network administrator to correlate the overall, company-wide security policy.

End-users are generally restricted and prohibited from installing their own applications or deploying individual solutions such as VPN add-ons in various browsers. This approach is put in place by network administrators to ensure business continuity, limit exposure and risks and, ensure data security measures are effective.

The DPI feature within Endpoint Protector is not designed to cover scenarios where end-users deploy their own, browser-based add-on VPNs. For such scenarios, the Deep Packet Inspection functionality should be disabled, allowing the default method of confidential content inspection.
Was this article helpful?
Can you please tell us how we can improve this article.
Thank you for your feedback!