Creating DLP Policies

Creating DLP Policies

The Barracuda SecureEdge Manager allows administrators to inspect network traffic for sensitive data and to block or log it before it leaves the network. Data Loss Prevention (DLP) operates inline within the SecureEdge inspection pipeline. At the DLP gate, content is held until classification completes or until the configured inline timeout is reached. DLP is inactive by default and is enabled by creating one or more DLP policies for a workspace. Each policy matches a Source and Destination on a given Direction, tests the content against one or more Classifiers, and applies an Action. Policies are evaluated in order, and the first match wins. For available detection models, see Available DLP Classifiers.

Policy selection is based only on the configured source and destination. Classifiers do not determine which policy is selected.

Before You Begin

  • You must have a valid Barracuda SecureEdge Premium Access subscription. DLP is included with Premium Access at no additional cost and is not available in SecureEdge Access Standard.

  • TLS Inspection must be enabled and configured. DLP can inspect only traffic that SecureEdge has terminated. Traffic not TLS‑inspected is invisible to DLP and generate no log entry.

  • Users must enroll with the SecureEdge Access Agent and route through a SecureEdge point of presence.

Users enrolled on a seat other than Premium Access are exempt from DLP enforcement. Their uploads are allowed through without being scanned.

Available Templates

Four suggested templates are available when creating a policy. Each template preselects an action and a set of classifiers, and you can confirm or edit the policy name before saving. Click View all 4 to see every template. To hide the templates, click Dismiss.

Template

Description

Template

Description

PCI-DSS — Cardholder Data

Block card & financial data uploads

HIPAA — Health Information

Block protected health uploads

Monitor Shadow-AI Services

Log high-risk uploads to AI apps

Monitor GDPR — EU Personal Data

Log EU personal data uploads

Step 1. Create a DLP Policy

  1. Go to Barracuda SecureEdge and log in with your existing Barracuda Cloud Control account.

  2. The chosen Tenant/Workspace is displayed in the top menu bar.

  3. From the drop-down menu, select the workspace you want to configure DLP for.

  4. Go to Security.

  5. Expand the Data Loss Prevention menu on the left and select Policies.

  6. The DLP Policies window opens. Suggested policy templates are displayed at the top of the page.

  7. Do one of the following:

    • To create a policy from a pre-built template, select a template from the Suggested policy templates section. Click Add.

    • To create a policy from scratch, click + Add DLP policy in the top-right corner and keep Custom Policy selected.

  8. new-policy.png
  9. Click + Add DLP policy.

  10. A Custom policy templates opens. Note: To resize the template window, click the double‑arrow icon at the top-left corner of the window. To make the template full screen, click the bidirectional arrow icon.

  11. Specify values for the following:

    • Name – Enter a unique name for the policy.

    • Description – Enter a brief description.

    • Action – Select the action to take when the policy matches traffic:

      • Do Not Scan – Matched traffic is not sent to DLP for scanning. This is the hidden default action for traffic that does not match any rule. It can be selected explicitly to override other rules.

      • Scan & Log – Matched traffic is sent to DLP for scanning but is allowed regardless of the scan results. The results are logged and may support alerting in the future.

      • Scan & Enforce – Matched traffic is sent to DLP for scanning. If classifiers are found, traffic is blocked. If threats are matched, it is allowed or blocked according to the configured threat settings.

    • Source – Select the source type and then the values to match:

      • All Sources – Matches every user and network. No further configuration is required.

      • IP/Network – Enter one or more IP address or network in CIDR notation, and click + Add.

      • User/Group – Select users or groups from the drop-down list, or type to search. Select All Users to match every enrolled user.

    • Destination – Select the destination type and then the values to match:

      • All Destinations – Matches every destination. No further configuration is required.

      • Domain – Enter one or more valid domains and click + Add.
        Note: Example domains (e.g., dropbox.com, drive.google.com) are illustrative only. You must use verified domains that work and matches for your SecureEdge DLP features.

        custom-policy.png



    • Direction – Select the direction of traffic to inspect:

      • Select Upload to inspect uploaded traffic. Supported formats: PDF, DOC/DOCX, PPT/PPTX, XLS/XLSX, TXT, MD, CSV, TSV, JPEG, PNG.

    • Classifiers – Click + Add classifiers. The Add DLP classifiers window opens.

      • Select one or more classifiers for the policy to enforce, and then click Save classifiers.
        Note: Classifiers are grouped by compliance profile. Click a group to expand it or click Expand all to view all classifiers. Choose specific classifiers or click Select All to pick them all. To reset, click Clear all.

        classifiers-save.png
    • In the Settings section, do one of the following:

      • Global settings used – Leave Global settings used disabled to inherit the workspace default settings. In this case, Strict mode enabled, the file size limit is 10 MB, and the inline timeout is 15 seconds. By default, policies use the global settings.

        global-setup-used.png

         

      • To override the global settings, turn on the Global settings used toggle. When enabled, the toggle changes to Global settings overridden, and you can configure the following settings:

        • Strict mode – Click to enable/disable. Content is blocked if file size is exceeded or inline processing times out. Scan results may still be available in logs. Recommended for high security policies.

        • File size limit – Select the maximum file size for DLP scanning from the drop-down menu (1 MB–10 MB).

        • Inline timeout – Select the timeout threshold for inline scanning from the drop-down menu (5–30 seconds).

  12. Click Save policy. To clear every field and start again, click Clear all.

After the configuration is complete, you can see that the new policy at the top of the DLP policies list. When a user’s traffic matches the policy and the uploaded content is detected by one of the selected classifiers, the configured action is applied and the event appears in the DLP logs.

dlp-table.png

How Policies Are Evaluated

DLP policies are evaluated from the top of the list downwards, and the first matching policy determines the action taken. No further policies are evaluated. New policies are inserted at the top of the list, giving them the highest priority. To create an exception, place a more specific Do Not Scan policy above a broader Scan & Enforce policy. The Default action row at the bottom of the policy list applies when there is no policy for the source and destination. It is fixed at Do Not Scan, shown for transparency, and cannot be changed.

Filter and Search Functions

The DLP policies table shows one row per policy, in evaluation order. Each row displays a drag handle and the priority number. The Action, Classifiers, and Direction columns can be filtered using the filter icon in the column header. To find a policy in a long list, type in the Search policies box.

Traffic that does not match any DLP policy is not scanned and is allowed through.

 

Edit a DLP Policy 

  1. Select the workspace you want to edit the DLP policy for.

  2. Go to the Security > Data Loss Prevention > Policies.

  3. The DLP policies page opens. Click the three-vertical-dots icon to edit the policy.

    edit-policy.png
  4. Click Edit policy.

  5. Edit the value you are interested in. 

  6. Click Save policy.

Note that the template drop-down does not appear when editing an existing policy.

 

Delete a DLP Policy 

  1. Select the workspace containing your DLP policies.

  2. Go to the DLP policies page.

  3. The DLP policies window opens. Click the three-vertical-dots icon to delete the policy.

  4. Click Delete policy.

  5. The Delete DLP policy <Name of policy>  window opens.

  6. Confirm the deletion and click Ok.

After deletion, the remaining policies retain their relative order and the deleted policy no longer applies.

 

Duplicate a DLP Policy

  1. Select the workspace containing your DLP policies.

  2. Go to the Security > Data Loss Prevention > Policies.

  3. The DLP policies window opens. Click the three-vertical-dots icon to duplicate the policy.

    duplicate-policy.png
  4. Click Duplicate policy.

  5. The create form opens with every field prefilled to match the source policy, except the name.

  6. Enter a new name, adjust any fields you want to change, and click Save policy.

 

(Optional) Stop DLP Scanning for a Workspace

To stop DLP scanning while preserving your configuration, create a policy with the Do Not Scan action that matches All Sources and All Destinations, and place it at the top of the policy list. This preserves existing policies and their order while preventing traffic from being sent to DLP for inspection.

Alternatively, you can delete all policies. When no policies exist, the Default action of Do Not Scan is applied to all traffic.

After the changes take effect, traffic is no longer scanned and no new DLP log entries are generated.

 

(Optional) Scan AI Prompts for Sensitive Data

You can scan AI prompts for sensitive data using Prompt Inspection. Text submitted to generative AI services is inspected by Prompt Inspection, which is configured under Security > Prompt Inspection. To enable sensitive data detection, turn on the PII scanning option in a Prompt Inspection policy. This allows DLP classifiers to inspect prompts for personally identifiable information (PII), such as credit card numbers and social security numbers.

For example, if a user submits the prompt "Summarize this customer record: Jane Smith, SSN 123-45-6789, credit card 4111 1111 1111 1111" to a generative AI service, Prompt Inspection can use DLP classifiers to detect the social security number and credit card number within the prompt. Based on the Prompt Inspection policy configuration, SecureEdge can then allow or block the prompt before it is submitted to the AI service.

For more information, see Creating Prompt Inspection Policies.

 

Step 2. View in DLP Logs

You can view and verify DLP policies enforcement events in DLP logs under Reports > Logs > DLP Logs in SecureEdge Manager. You can use filters to group and review log contents. You can create custom logs and save them.

For more information, see Verifying DLP Policy Enforcement Events in DLP Logs

 

Further Information


We value your feedback.
If you have questions, suggestions, or feedback on our documentation, contact the Campus Product Documentation team.
For general product inquiries or technical support, please contact the global Barracuda Support team.