Create a Data Profile with EDM Datasets on the DLP App
Create an Enterprise data loss prevention (DLP) data profile using Exact Data Matching (EDM) datasets in the DLP app on the hub.
Create a data profile with Exact Data Matching (EDM) datasets in the DLP app on the hub. Data profiles with EDM datasets created in the DLP app are automatically synchronized with your Panorama™ management server so you can leverage the data profile in your Security policy rules. In order for the DLP cloud service to render a match verdict using on the data profile, scanned files containing primary and secondary field values must be within 100 character of each other. Otherwise, the DLP cloud service is unable to render a match verdict. Data profiles with an EDM dataset can only be created on the DLP app on the hub and are viewable on Panorama, Prisma Access (Panorama Managed), Prisma Access (Cloud Managed), and the DLP app on the hub. Viewing a data profile created on the DLP app on Panorama requires Panorama plugin for Enterprise DLP 1.0.4 or later release.
Updating a data profile to include only data patterns is not allowed if the data profile includes at least one EDM dataset when it was initially created. However, updating a data profile that includes only EDM datasets to include EDM datasets and data patterns is supported.
See Create a Data Profile on the DLP App to create a data profile containing only predefined or custom data patterns.
- Select.Data ProfilesAdd Data ProfileWith EDM or a combination of EDM and Data PatternsYou 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 withCopy - <name_of_original_data_profile>. This name can be edited as needed.Adding an EDM dataset to a copied data profile is supported only if the original data profile had an EDM dataset to begin with. Adding an EDM dataset to a data profile that does not already have an EDM dataset is not supported.
- Create the Primary Rule for the data profile.
- Enter a descriptiveData Profile Name.
- For the Primary Rule, select the operator (ANDorOR) andAdd EDM Dataset.
- Select the EDM dataset to include.The list of available data sets are the EDM data sets uploaded using the EDM CLI application.
- Specify theOccurrencesrequired to trigger a Security policy rule action.The occurrences value you configure determine how many times values in the Primary Field and Secondary Fields are encountered before triggering an action.
- Select thePrimary Fieldvalues.The list of available values is populated from the selected EDM data set. You must select at least one primary field value.You are required to add at least one column where the column values occurs up to 12 times in the selected EDM data set for thePrimary Field. For example, if the EDM data set contains columns for first name, last name, social security number, and credit card number, add social security number and credit card in the primary field.
- (Optional) Select theSecondary Fieldvalues.The list of available fields is populated from the selected EDM data set.For the best results for exact data matching, include any columns that could be repeated in the secondary field. For example, if the EDM data set contains columns for first name, last name, social security number, and credit card number, add first name and last name in the secondary field.
- (Optional)Add EDM Datasetto add additional data pattern conditions usingANDorORoperators to the Primary Rule.Refer to the descriptions above to configure any additional data pattern conditions as needed.
- Configure the match criteria for a Security policy rule action based on the values in the primary and secondary fields.When you selectAny (OR), the maximumCountsetting is one less than the total number of fields included in thePrimary FieldorSecondary Field.Configure whether an action ifAny (OR)orAll (AND)primary fields are matched and ifAny (OR)orAll (AND)secondary fields are matched.For example, you configure the data profile to scan for at least 20 occurrences that match for All primary fields and Any secondary fields with a match count of 3. When applied to a Security policy rule, an action is taken when a scanned file contains at least 20 matches to all primary field values and any 3 of the secondary field values.
- (Optional)Add Groupto nest additional match criteria for an EDM dataset so you can more accurately define your compliance rules.When you clickAdd Group, the new match criteria group is nested under the most recently added EDM dataset. You cannot nest a new match criteria group between existing EDM datasets. If multiple EDM datasets are added, you must remove the EDM datasets that follow the EDM dataset for which you want to added the nested match criteria. For example, you addedEDM_Dataset1,EDM_Dataset2, andEDM_Dataset3to the Primary Rule. If you wanted to added nested match criteria toEDM_Dataset2, you must first removeEDM_Dataset3from the Primary Rule.You can select the same EDM dataset or a different EDM dataset to more accurately define your compliance rules. Nesting match criteria is supported only when the data profile includes an EDM dataset. Enterprise DLP supports up to 3 level of additional nesting groups for each EDM dataset. You can nest additional EDM datasets under an EDM dataset added to the Primary or Secondary Rule.Nested match criteria support theAND,OR, andNOToperators. Refer to the descriptions above to configure the nested match criteria.
- (Optional) Configure a Secondary Rule for the data profile.Data pattern match criteria added to the Secondary Rule block all traffic that meet the match criteria for the data patterns by default and cannot be modified. If you want to allow traffic that matches a data pattern match criteria, add it to the Primary Rule.
- Review theData Profile Previewto verify the data profile match criteria.
- Savethe data profile.
- Verify that the data profile you created.
- Prisma Access (Cloud Managed)
- Selectand search for the data profile you created.ManageConfigurationSecurity ServicesData Loss Prevention
- Panorama and Prisma Access (Panorama Managed)See Update a Data Filtering Profile on Panorama for more information on which data profile settings are editable on Panorama for a data profile created on Prisma Access (Cloud Managed).
- Selectand navigate to the data profile you created.ObjectsDLPData Filtering Profiles
- (Optional) Edit the data profile Action to block traffic.The Action for a data profile created on the Prisma Access (Cloud Managed) is configured toAlertby 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 Prisma Access (Cloud Managed).
- Set the data profile Action toBlocktraffic that matches the data profile match criteria.
- SelectandCommitCommit to PanoramaCommit.
- SelectandCommitPush to DevicesEdit Selections.
- SelectDevice GroupsandInclude Device and Network Templates.
- Pushyour configuration changes to your managed firewalls that are leveraging Enterprise DLP.
- Attach the data profile to a Security policy rule.
- Panorama and Prisma Access (Panorama Managed)
- Selectand specify thePoliciesSecurityDevice Group.
- Select the Security policy rule to which you want to add the data profile.
- SelectActionsand set theProfile TypetoProfiles.
- Select theData Filteringprofile you created.
- SelectCommitandCommit and Push.
Recommended For You
Recommended videos not found.