Create a DLP Policy

Overview

Creating a Data Leak Prevention (DLP) policy in Zaperon allows administrators to detect, monitor, and prevent the unauthorized movement of sensitive data across applications and endpoints. DLP policies help protect regulated, confidential, and business-critical information by inspecting content in real time and enforcing security actions such as Log or Block.

With Zaperon DLP, organizations can prevent data leaks without disrupting user productivity by applying granular controls based on data type, file characteristics, and user groups.

Why Create a DLP Policy?

Organizations create DLP policies to reduce the risk of data breaches and accidental data exposure. Common reasons include:

Certificate-pinned applications (messaging, conferencing, SaaS platforms).
Vendor-recommended inspection bypass.
Applications that fail during SSL/TLS inspection.
Critical business services requiring uninterrupted connectivity.
Preventing leakage of sensitive data such as credit card numbers, Aadhaar numbers, bank details, or personal identifiers.
Enforcing regulatory and compliance requirements (PCI DSS, GDPR, etc.).
Monitoring data movement across cloud applications like Microsoft 365 and Google Workspace.
Controlling uploads, downloads, sharing such as on WhatsApp, Telegram, etc. and clipboard activities like Screenshots, Copy, Paste.
Gaining visibility into how sensitive data is accessed and used across the organization.

When to Create a DLP Policy?

You should create a Data Leak Prevention (DLP) policy when your organization needs to identify and control the movement of specific types of sensitive data, not just applications or users.

Sensitive or regulated data must be protected from unauthorized sharing
Users access business applications from managed endpoints
Compliance mandates require monitoring or blocking specific data types
You want to log data movement for audit or investigation purposes
Security teams need fine-grained control over data flows across applications

Note:

1. DLP policies rely on Data Dictionaries to identify what sensitive data looks like. A Data Dictionary defines patterns, exact matches, or predefined identifiers that the Zaperon DLP engine uses to inspect content.

2. Data Leak Protection works only for agent-based users.

Before creating a DLP policy, ensure that required data dictionaries are available.

→ Refer to Add Data Dictionary – Choose predefined or create custom data dictionary to detect sensitive information.

Without a Data Dictionary, DLP policies cannot inspect or classify sensitive data, which may result in incomplete protection or false negatives.

Creating a New DLP Policy

1. To create a policy, go to Data Protection and click on Create Policy button.

2. Enter all the details and click Next.

You can create 3 types of DLP Policy:

Application DLP – If you select application DLP as policy type

Clipboard DLP – Define list of domains which are allowed for user by clicking Add Domain.

Storage Media DLP – Define list of domains which are allowed for user by clicking Add Domain.

3. On successful creation of policy, confirmation message will appear.

4. New policy created will appear in the policy list.

5. New policy created will appear in the policy list.

Managing and Deleting Policy

DLP policy .... add more content here

You can review or remove exclusions at any time from the Global Web Exclusions page.

→ Refer to Delete Global Web Exclusions (Replace this for dlp)

Summary

Global Web Exclusions enable organizations to maintain application compatibility while enforcing strong Secure Web controls. By selectively bypassing inspection for trusted domains, Zaperon supports certificate-pinned applications, ensures business continuity, and aligns with industry-standard Secure Web Gateway practices. (Replace this for DLP)

Google Sites

Report abuse