Create a DLP Policy

Overview

Creating a Data Leak Prevention (DLP) policy in Zaperon enables administrators to detect, monitor, and prevent unauthorized data movement across applications, endpoints, clipboards, and storage media. Zaperon DLP policies help protect regulated, confidential, and business-critical data by inspecting content in real time and enforcing security actions such as Log or Block before a data leak occurs.

Zaperon supports multiple DLP policy types to provide comprehensive endpoint-level protection:

Application DLP – Controls data uploads, downloads, and sharing activities across web and desktop applications.

With Zaperon DLP, organizations can apply granular controls based on data type, file attributes, activity type, destination, and user groups, ensuring strong data protection without disrupting employee productivity. These policies work seamlessly for agent-based users, enabling continuous visibility, policy enforcement, and compliance with industry and regulatory requirements.

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.
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 – Select Application DLP as the policy type to monitor and control sensitive data movement within cloud and SaaS applications. You can define protected applications, application tags, and specific user activities (such as upload, download, share, or delete) to prevent unauthorized data leakage for agent-based users.

3. Click Add Condition to create condition sets that define when the DLP policy applies. You can add up to 3 condition sets, using AND/OR logic to match content types and data dictionaries. The policy triggers when any condition set is satisfied..

4. Once the policy is saved successfully, a confirmation message appears indicating that the policy is saved and applied to group.

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

Managing DLP Policy

After creating a Data Leak Prevention (DLP) policy, you can continue to manage it based on your security and operational requirements. Zaperon allows administrators to control how and where a policy is enforced without recreating it.

You can configure and update policy conditions, content types, and actions to ensure sensitive data is protected across applications, files, email, and web activities. Policies can be enabled or disabled as needed to test changes or troubleshoot issues.

If a DLP policy is no longer required, it can be permanently deleted to keep policy management clean and reduce unnecessary rule processing.

→ Refer to Edit a DLP Policy.

→ Refer to Delete DLP Policy.

→ Refer to Enable/Disable DLP Policy.

Summary

Creating a DLP policy ensures your data protection strategy begins with clearly defined rules and controls. By configuring accurate conditions and scope, administrators can proactively prevent data leakage and adapt to organizational security needs.

Google Sites

Report abuse