Enterprise DLP
Non-File Based for Panorama
Table of Contents
Non-File Based for Panorama
Panorama
Create a data filtering profile for the
Enterprise Data Loss Prevention (E-DLP)
on the Panorama™ management server
to inspect non-file traffic for sensitive data.- Log in to thePanoramaweb interface.
- Edit the Data Filtering Settings onPanoramato configure the minimum and maximum data size limits and the actions the firewall takes when uploading non-file data to the DLP cloud service.Palo Alto Networks recommends verifying youEnable Non File DLPafter you installPanoramaplugin forEnterprise DLP3.0.1.
- Create one or more data patterns.
- (Optional) Create a custom application filter or application group to define predefined or custom application traffic you want to exclude from inspection.The application filter and application group must beSharedto be used in the data filtering profile application exclusion list. Data filtering profiles for non-file traffic inspection support either both custom application filters and application groups. You aren’t required to add both.
- (Optional) Create a custom URL category to define URL traffic you want to exclude from inspection.The URL category must beSharedto be used in the data filtering profile URL exclusion list.To include the custom URL category in the URL exclusion list of a data filtering profile, adding the custom URL category to a URL Filtering profile isn’t required.
- Select.ObjectsDLPData Filtering Profiles
- Adda new data filtering profile.
- (Optional) Configure the data filtering profile to scanFile Basedtraffic.Data filtering profiles support scanning both file based and non-file based traffic. SelectYesto scan for both file based and non-file based traffic. SelectNoto only scan for non-file based traffic. Configuring the data filtering profile not to scan for file based traffic has no impact on scanning non-file based traffic.
- Configure the data filtering profile to scanNon-File Basedtraffic.SelectYesto scan for non-file based traffic.
- Verify thatSharedis enabled.AllEnterprise DLPdata profiles must beSharedacross all device groups. This setting is enabled by default and cannot be disabled.
- Define the match criteria.
- If you selectBasic, configure the following:
- Primary Pattern—Addone or more data patterns to specify as the match criteria.If you specify more than one data pattern, the managed firewall uses a boolean OR match in the match criteria.
- Match—Select whether the pattern you specify should match (include) or not match (exclude) the specified criteria.
- Operator—Select a boolean operator to use with theThresholdparameter. SpecifyAnyto ignore the threshold.
- Any—Security policy rule action triggered ifEnterprise DLPdetects at least one instance of matched traffic.
- Less than or equal to—Security policy rule action triggered ifEnterprise DLPdetects instances of matched traffic, with the maximum being the specifiedThreshold.
- More than or equal to—Security policy rule action triggered ifEnterprise DLPdetects instances of matched traffic, with a minimum being the specifiedThreshold.
- Between (inclusive)—Security policy rule action triggered ifEnterprise DLPdetects any number of instances of matched traffic between the specificThresholdrange.
- Occurrence—Specify the number of instances of matched traffic required to trigger a Security policy rule action. Range is1-500.For example, to match a pattern that appears three or more times in a file, selectmore_than_or_equal_toas theOperatorand specify3as theThreshold.
- Confidence—Specify the confidence level required for a Security policy rule action to be taken (HighorLow).
- If you selectAdvanced, you can create expressions by dragging and dropping data patterns,Confidencelevels,Operators, andOccurrencevalues into the field in the center of the page.Specify the values in the order that they’re shown in the following screenshot (data pattern,Confidence, andOperatororOccurrence).
- Select anAction(AlertorBlock) to perform on matching traffic.If the data profile has both Primary and Secondary Patterns, changing the data profile Action onPanoramadeletes all Secondary Pattern match criteria.
- (Optional) Configure the URL category list to exclude URL traffic from inspection.The URL category list can only be configured whenNon-File Basedtraffic inspection is enabled.
- SelectURL Category List Excluded From Non-File.
- Adda new URL category list.
- Select a predefined URL category, custom URL category or EDL.
- Configure the application exclusion list to exclude application traffic from inspection.The application list can only be configured whenNon-File Basedtraffic inspection is enabled. At least one application list or application group is required to create a data filtering profile for inspecting non-file traffic.
- SelectApplication List Excluded From Non-File.
- Addan application filter or application group.If you didn’t create a custom application filter or application group, you must add theDLP App Exclusion Filter.
- For theDirection, onlyUploadis supported for inspection of non-file based traffic.
- Set theLog Severityrecorded for files that match this rule.You can selectcritical,high,medium,low, orinformational. The default severity isinformational.
- ClickOKto save your changes.
- Attach the data filtering profile to a Security policy rule.
- Selectand specify thePoliciesSecurityDevice Group.
- Select the Security policy rule to which you want to add the data filtering profile.
- SelectActionsand set theProfile TypetoProfiles.
- Select theData Filteringprofile you created previously.
- ClickOK.
- Commit and push the new configuration to your managed firewalls to complete theEnterprise DLPplugin installation.This step is required forEnterprise DLPdata filtering profile names to appear in Data Filtering logs.TheCommit and Pushcommand isn’t recommended forEnterprise DLPconfiguration changes. Using theCommit and Pushcommand requires the additional and unnecessary overheard of manually selecting the impacted templates and managed firewalls in the Push Scope Selection.
- Full configuration push from Panorama
- SelectandCommitCommit toPanoramaCommit.
- SelectandCommitPush to DevicesEdit Selections.
- SelectDevice GroupsandInclude Device and Network Templates.
- ClickOK.
- Pushyour configuration changes to your managed firewalls that are usingEnterprise DLP.
- Partial configuration push from PanoramaYou must always include the temporary__dlpadministrator when performing a partial configuration push. This is required to keepPanoramaand the DLP cloud service in sync.For example, you have anadminPanoramaadmin user who is allowed to commit and push configuration changes. Theadminuser made changes to theEnterprise DLPconfiguration and only wants to commit and push these changes to managed firewalls. In this case, theadminuser is required to also select the__dlpuser in the partial commit and push operations.
- Select.CommitCommit toPanorama
- SelectCommit Changes Made Byand then click the current Panorama admin user to select additional admins to include in the partial commit.In this example, theadminuser is currently logged in and performing the commit operation. Theadminuser must clickadminand then select the__dlpuser. If there are additional configuration changes made by other Panorama admins they can be selected here as well.ClickOKto continue.
- Commit.
- Select.CommitPush to Devices
- SelectPush Changes Made Byand then click the current Panorama admin user to select additional admins to include in the partial push.In this example, theadminuser is currently logged in and performing the push operation. Theadminuser must clickadminand then select the__dlpuser. If there are additional configuration changes made by other Panorama admins they can be selected here as well.ClickOKto continue.
- SelectDevice GroupsandInclude Device and Network Templates.
- ClickOK.
- Pushyour configuration changes to your managed firewalls that are usingEnterprise DLP.