Modify an Enterprise Data Loss Prevention (E-DLP) rule to enforce data security standards on Strata Cloud Manager.
On May 7, 2025, Palo Alto Networks is introducing new Evidence Storage and Syslog Forwarding service IP
addresses to improve performance and expand availability for these services
globally.
You must allow these new service IP addresses on your network
to avoid disruptions for these services. Review the Enterprise DLPRelease Notes for more
information.
Where Can I Use This?
What Do I Need?
NGFW (Managed by Strata Cloud Manager)
Prisma Access (Managed by Strata Cloud Manager)
Enterprise Data Loss Prevention (E-DLP) license
Review the Supported
Platforms for details on the required license
for each enforcement point.
Or any of the following licenses that include the Enterprise DLP license
Prisma Access CASB license
Next-Generation
CASB for Prisma Access and NGFW (CASB-X) license
Data Security license
Configure a DLP rule to define the type of traffic to inspect, the impacted file types, action,
and log severity for the data profile match criteria. Enterprise Data Loss Prevention (E-DLP)
automatically creates a DLP rule when you create a new data profile. After you configure the data filtering
profile, you must create a Profile Group containing the data filtering profile and
attached it to a Security policy rule so the NGFW or Prisma Access tenant can enforce your data security standards.
Select ManageConfigurationData Loss PreventionDLP Rules and in the Actions column, Edit the DLP
rule.
The DLP rule has an identical name as the data profile from which it was
automatically created.
(Optional) Enter a Description for the DLP rule.
Modify the DLP rule Match Criteria.
Expand all
Collapse all
File Based
Enable DLP rule match criteria for file-based based
traffic.
(Prisma Access 5.1 and later) Select the
File Scan Mode to explicitly
include or exclude specific file types.
A DLP rule supports only one type of file mode. You can't
configure a DLP rule to both include and exclude specific
file types.
Include—Enterprise DLP
only inspects the selected file types. The NGFW or Prisma Access tenant
ignores all other file types and does not forward
them to Enterprise DLP for inspection and
verdict rendering.
Exclude—The NGFW or Prisma Access tenant excludes the selected
file types and does not send them Enterprise DLP for inspection and verdict rendering. The NGFW or Prisma Access tenant
forwards all other file types to Enterprise DLP
but Enterprise DLP inspects and renders
verdicts only on supported file
types.
All supported file types are included in the match criteria
by default.
Specify the File Direction
(Upload,
Download, or
Both).
The default file direction is
Upload. File direction
support is dependent on the app. Review the list of supported apps to
learn which file directions Enterprise DLP supports.
Non-File Based
Enable DLP rule match criteria for non-file based
traffic.
Select the URL Category List
Exclusions to exclude forwarding traffic
from one or more specific URLs to Enterprise DLP.
You can use a predefined URL category or create a custom URL
category in the Global
Configuration Scope. You can select multiple URL categories
to exclude traffic from non-file inspection.
Select the Application List Exclusion
to exclude forwarding traffic from one or more specific apps
to Enterprise DLP.
You can use a predefined application filter or create a custom application
filter in the Global
Configuration Scope. You can select multiple application
filters to exclude app traffic from non-file inspection.
Enterprise DLP requires at least one Application
Filter if you enable exclusions for non-file based
traffic. Palo Alto Networks recommends adding the
predefined DLP App
Exclusion application filter if you
don't have a custom or predefined application filter you
want to add.
Configure the Action & Log settings.
Select the Action (Alert,
or Block) taken when Enterprise DLP detects
sensitive data.
The default action is Alert.
Set the Log Severity when Enterprise DLP
detects traffic that matches the DLP rule.
The default severity is Low.
(Best Practices for File Based Inspection) Create a File Blocking profile and create a
Block Rule to block the file types you don't
explicitly forwarded to Enterprise DLP.
Palo Alto Networks recommends creating this File Blocking profile to ensure
sensitive data can't be exfiltrated in file types Enterprise DLP
doesn't support.
Create a Shared Profile Group for the Enterprise DLP data filtering profile.
Select ManageConfigurationNGFW and Prisma AccessSecurity ServicesProfile Groups and Add Profile Group.
Enter a descriptive Name for the Profile
Group.
(Best Practices for File Based Inspection) For the File
Blocking Profile, select the File Blocking profile you created in the
previous step.
For the Data Loss Prevention Profile, select the Enterprise DLP
data profile.
Add any other additional profiles as needed.
Save the profile group.
Create a Security policy rule and attached the Profile Group.
Select ManageConfigurationNGFW and Prisma AccessSecurity ServicesSecurity Policy and Add Rule.
You can also update an existing Security policy to attach a Profile
Group for Enterprise DLP filtering.
Configure the Security policy as needed.
Navigate to the Action and Advanced Inspection section, and select the
Profile Group you created in the previous
step.