DLP App

Log in to the DLP app on the hub.
If you don’t already have access to the DLP app on the hub, see the hub Getting Started Guide. Only Superusers can access the hub.
Select
Data Profiles
Add Data Profile
Classic Data Profile
.
You can also create a new data profile by copying an existing data profile. This allows you to quickly modify an existing data profile with additional match criteria while preserving the original data profile from which the new data profile was copied.
Data profiles created by copying an existing data profile are appended with
Copy - <name_of_original_data_profile>
. This name can be edited as needed.
Adding an EDM data set to a copied data profile is supported only if the original data profile had an EDM data set to begin with. Adding an EDM data set to a data profile that doesn’t already have an EDM data set isn’t supported.
Configure the Primary Rule for the data profile.
Data pattern match criteria for traffic that you want to allow must be added to the Primary Rule. Data pattern match criteria for traffic that you want to block can be added to either Primary Rule or Secondary Rule.
Enter a descriptive
Data Profile Name
.
Add Pattern Group
and
Add Data Pattern
.
Define the match criteria.
Data Pattern
—Select a custom or predefined data pattern.
Occurrence Condition
—Specify the occurrences condition required to trigger a Security policy rule action.
Any
—Security policy rule action triggered if
Enterprise DLP
detects at least one instance of matched traffic.
Less than or equal to
—Security policy rule action triggered if
Enterprise DLP
detects instances of matched traffic, with the maximum being the specified
Count
.
More than or equal to
—Security policy rule action triggered if
Enterprise DLP
detects instances of matched traffic, with a minimum being the specified
Count
.
Between (inclusive)
—Security policy rule action triggered if
Enterprise DLP
detects any number of instances of matched traffic between the specific
Count
range.
Count
—Specify the number of instances of matched traffic required to trigger a Security policy rule action. Range is
1
-
500
.
For example, to match a pattern that appears three or more times in a file, select
More than or equal to
as the
Occurrence Condition
and specify
3
as the
Threshold
.
Confidence
—Specify the confidence level required for a Security policy rule action to be taken (
High
or
Low
).
(
Optional
)
Add Data Pattern
to add additional data pattern match criteria to the Primary rule.
(
Optional
)
Add Data Pattern Group
to add additional data pattern conditions using
AND
or
OR
operators to the Primary Rule.
Refer to the descriptions above to configure any additional data pattern conditions as needed.
(
Optional
) Configure a Secondary Rule.
Data pattern match criteria added to the Secondary Rule block all traffic that meets the match criteria for the data patterns by default and can’t be modified. If you want to allow traffic that matches a data pattern match criteria, add it to the Primary Rule.
Review the
Data Profile Preview
to verify the data profile match criteria.
Save
the data profile.

Verify that the data profile you created.
DLP App on the hub—
Log in to the DLP app on the hub as a Superuser and select
Data Profiles
to view the data profile you created.
Strata Cloud Manager
—Log in to
Strata Cloud Manager
and select
Manage
Configuration
Security Services
Data Loss Prevention
and search for the data profile you created.
Panorama
and
Prisma Access (Managed by Panorama)
See Update a Data Profile for more information on which data profile settings are editable on
Panorama
for a data profile created on
Strata Cloud Manager
.
Log in to the
Panorama
web interface.
Select
Objects
DLP
Data Filtering Profiles
and navigate to the data profile you created.
(
Optional
) Edit the data profile Action to block traffic.
The Action for a data profile created on
Strata Cloud Manager
is configured to
Alert
by default.
If the data profile has both Primary and Secondary Patterns, changing the data profile Action on
Panorama
deletes all Secondary Pattern match criteria.
Select the data profile created on
Strata Cloud Manager
.
Set the data profile Action to
Block
traffic that matches the data profile match criteria.
Select
Commit
Commit to
Panorama
and
Commit
.
Click
OK
.
Select
Commit
Push to Devices
and
Edit Selections
.
Select
Device Groups
and
Include Device and Network Templates
.
Push
your configuration changes to your managed firewalls that are using
Enterprise DLP
.
Attach the data profile to a Security policy rule.
SaaS Security
— Add a new asset rule and specify the match criteria using data profile you created.
Prisma Access (Managed by Strata Cloud Manager)
—Modify a DLP Rule for Prisma Access on Strata Cloud Manager.
Panorama
and
Prisma Access (Managed by Panorama)
Log in to the
Panorama
web interface.
Select
Policies
Security
and specify the
Device Group
.
Select the Security policy rule to which you want to add the data profile.
Select
Actions
and set the
Profile Type
to
Profiles
.
Select the
Data Filtering
profile you created.
Click
OK
.
Select
Commit
and
Commit and Push
.