Objective

Highlight the outcome that improvements to international predefined entities are part of Netskope’s long-term roadmap

Netskope existing detection mostly relies on a third-party entity.

Prerequisite

This issue generally applies to all Netskope Standard and Professional DLP modules, including, but not limited to, NGSWG DLP, Email DLP, Endpoint DLP, and more.

Context

Customers can test pre-defined identifiers in their own languages, particularly in non-English regions, to verify whether they function correctly. They may only trigger the sample data demonstrated in the UI, so using a variety of real-life samples is highly recommended for more accurate verification.

Do You Know?

Non-numerical identifiers such as addresses, names, or terms are likely to bypass Netskope’s DLP detection mechanism without triggering alerts or appearing in DLP incidents. This means the administrator will be unable to track or investigate the data leakage incident.

Notes

We’ve discovered that others have already raised similar concerns. We have reported this to Netskope Support and the Account team, but their actions are limited. Please be aware that neither data identifiers nor regex can be trusted 100% for an unknown period of time.