Netskope Global Technical Success (GTS)
Netskope DLP – Designing DLP Profiles and File Filters in Netskope
Netskope Cloud Version - 127
Introduction
This article explains how to create and use DLP Profiles in Netskope.
A DLP Profile is a container that brings together one or more DLP Rules and applies additional filters and classifications, including file types and size-based criteria.
This step is essential for organizing DLP logic and optimizing what kinds of files and content are inspected in various use cases.
What is a DLP Profile?
A DLP Profile combines:
- One or more DLP Rules (the detection logic)
- A File Profile (filters files by type, size, and extension)
Profiles allow you to group rules by business purpose or regulatory need, then apply them selectively using DLP Policies.
Core Components of a DLP Profile
1. File Profile (Filtering by File Types and Sizes)
| What is it? | Why it matters | Example Use Case |
| Defines filters to include or exclude files based on MIME types, file extensions, and file size.It controls which files are eligible for inspection by DLP. | Ensures only relevant files are scanned — improving performance, reducing false positives, and focusing inspection on meaningful data.It helps avoid scanning videos, binaries, or oversized files unnecessarily. | Only inspect .docx, .pdf, and .xlsx files under 10MB; skip media formats like .mp4 or .zip. |
2. Rule Classification
| What is it? | Why it matters | Example Use Case |
| A set of detection logic elements — including DLP Rules, File Classifiers, and Fingerprint Rules — that determine what sensitive content to look for.It defines what Netskope should detect in files during inspection. | Helps organize detection logic based on business needs, improve accuracy, and support modular, reusable policy structures.It ensures that the inspection is meaningful and aligned to actual data protection goals. | A “PII Protection” profile with DLP Rules for Aadhaar and PAN, and a Fingerprint Rule for employee records. |
Best Practices for Effective Profiles
| Best Practice | Why It’s Important |
| Group rules by use case | Easier to manage and audit |
| Limit to relevant file types | Avoids scanning formats unlikely to contain sensitive content |
| Apply size limits | Helps skip large binaries or media files |
| Avoid overloading one profile | Keeps profiles modular and clear in intent |
| Review detection trends regularly | Helps refine filters based on actual data movement and incidents |
What’s Next?
Once your DLP Profiles are ready, you need to apply them using DLP Policies — which connect profiles to users, apps, and actions.
Terms and Conditions
- All documented information undergoes testing and verification to ensure accuracy.
- In the future, it is possible that the application's functionality may be altered by the vendor. If any such changes are brought to our attention, we will promptly update the documentation to reflect them.
Notes
- This article is authored by Netskope Global Technical Success (GTS).
- For any further inquiries related to this article, please contact Netskope GTS by submitting a support case with 'Case Type – How To Questions'.
