>
    Create a Nested Data Profile
    Focus
    Download PDF
    Focus
    1. Home
    2. Enterprise DLP
    3. Configure Enterprise DLP
    4. Data Profiles
    5. Create a Nested Data Profile
    Download PDF
    Enterprise DLP

    Create a Nested Data Profile

    Table of Contents

    Create a Nested Data Profile

    Create a single Enterprise Data Loss Prevention (E-DLP) data profile containing multiple data profiles to simplify management of sensitive data leaving your network.
    Where Can I Use This?What Do I Need?
    • NGFW (Managed by Panorama or Strata Cloud Manager)
    • Prisma Access (Managed by Panorama or 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
    Enterprise Data Loss Prevention (E-DLP) supports creating a single data profile that contains multiple nested data profiles. Creating a single data profile that contains multiple nested data profiles allows you to consolidate the match criteria to prevent exfiltration of sensitive data to a single data profile that can be used in a single Security policy rule. This allows you to simplify the management of sensitive data leaving your network and reduces the need to manage multiple Security policy rules and data profiles.
    When you create a data profile that contains predefined data profiles and patterns, be sure to consider the detection types used by the predefined data patterns because the detection type determines how Enterprise DLP arrives at a verdict for scanned files.
    • Adding, deleting, or otherwise modifying the nested data profiles you add to data profile is supported only from the DLP app on the hub and Strata Cloud Manager, but not from Panorama.
    • Adding a nested data profile to another nested data profile is not supported.
    • Nesting a data profile that includes an EDM data set to an existing data profile if one wasn’t included when the data profile was originally created is supported.

    Strata Cloud Manager

    Create and configure an Enterprise Data Loss Prevention (E-DLP) data profile containing multiple data profiles on Strata Cloud Manager.
    1. Log in to Strata Cloud Manager.
    2. (Optional) Create your classic or advanced data profiles on Strata Cloud Manager.
      You can create a data profile that contains multiple data profiles using both predefined data profiles and custom data profiles you create.
    3. Select ManageConfigurationData Loss PreventionData Profiles and Add Data ProfilesNested Data Profiles.
      You can also create a new data profile by copying an existing data profile that already contains multiple data profiles. This allows you to quickly modify an existing data profile with additional data profile 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>.
    4. Enter the Data Profile Name.
    5. Configure the Primary Rule for the data profile.
      Add Data Profile to add predefined or custom data profiles. Repeat this step to include additional data profiles.
      Data profile match criteria for traffic that you want to allow must be added to the Primary Rule. Data profiles match criteria for traffic that you want to block can be added to either Primary Rule or Secondary Rule.
      A data profile containing multiple data profiles support any combination of data profiles with data patterns only, data patterns and EDM data sets, and EDM data sets only.
      Only the OR operator is supported.
    6. (Optional) Configure a Secondary Rule.
      Add Data Profile to add predefined or custom data profiles. Repeat this step to include additional data profiles.
      Data profile match criteria added to the Secondary Rule block all traffic that meets the match criteria for the data profile by default and can’t be modified. If you want to allow traffic that matches a data profile match criteria, add it to the Primary Rule.
      A data profile containing multiple data profiles support any combination of data profiles with data patterns only, data patterns and EDM data sets, and EDM data sets only.
      Only the OR operator is supported.
    7. Save the data profile.
    8. 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 ManageConfigurationSecurity ServicesData 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.
        If the data profile has both Primary and Secondary Patterns, changing the data profile Action on Panorama deletes all Secondary Pattern match criteria.
        1. Select the data profile created on Strata Cloud Manager.
        2. Set the data profile Action to Block traffic that matches the data profile match criteria.
        3. Select CommitCommit to Panorama and Commit.
        4. Click OK.
        5. Select CommitPush to Devices and Edit Selections.
        6. Select Device Groups and Include Device and Network Templates.
        7. Push your configuration changes to your managed firewalls that are using Enterprise DLP.
    9. Create a Security policy rule and associate the data profile.

    DLP App

    Create an Enterprise Data Loss Prevention (E-DLP) data profile containing multiple data profiles on the DLP app.
    1. 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.
    2. (Optional) Create your classic or advanced data profiles on the DLP app.
      You can create a data profile that contains multiple data profiles using both predefined data profiles and custom data profiles you create.
    3. Select Data ProfilesAdd Data ProfileNested Data Profiles.
      You can also create a new data profile by copying an existing data profile that already contains multiple data profiles. This allows you to quickly modify an existing data profile with additional data profile 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>.
    4. Enter the Data Profile Name.
    5. Configure the Primary Rule for the data profile.
      Add Data Profile to add predefined or custom data profiles. Repeat this step to include additional data profiles.
      Data profile match criteria for traffic that you want to allow must be added to the Primary Rule. Data profiles match criteria for traffic that you want to block can be added to either Primary Rule or Secondary Rule.
      A data profile containing multiple data profiles support any combination of data profiles with data patterns only, data patterns and EDM data sets, and EDM data sets only.
      Only the OR operator is supported.
    6. (Optional) Configure a Secondary Rule.
      Add Data Profile to add predefined or custom data profiles. Repeat this step to include additional data profiles.
      Data profile match criteria added to the Secondary Rule block all traffic that meets the match criteria for the data profile by default and can’t be modified. If you want to allow traffic that matches a data profile match criteria, add it to the Primary Rule.
      A data profile containing multiple data profiles support any combination of data profiles with data patterns only, data patterns and EDM data sets, and EDM data sets only.
      Only the OR operator is supported.
    7. Save the data profile.
    8. 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 ManageConfigurationSecurity ServicesData 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 the DLP app.
      1. Log in to the Panorama web interface.
      2. Select ObjectsDLPData Filtering Profiles and navigate to the data profile you created.
      3. (Optional) Edit the data profile Action to block traffic.
        The Action for a data profile created on the DLP app 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.
        1. Select the data profile created on the DLP app.
        2. Set the data profile Action to Block traffic that matches the data profile match criteria.
        3. Select CommitCommit to Panorama and Commit.
        4. Click OK.
        5. Select CommitPush to Devices and Edit Selections.
        6. Select Device Groups and Include Device and Network Templates.
        7. Push your configuration changes to your managed firewalls that are using Enterprise DLP.
    9. Attach the data profile to a Security policy rule.
      1. Log in to the Panorama web interface.
      2. Select PoliciesSecurity and specify the Device Group.
      3. Select the Security policy rule to which you want to add the data profile.
      4. Select Actions and set the Profile Type to Profiles.
      5. Select the Data Filtering profile you created.
      6. Click OK.
      7. Select Commit and Commit and Push.

    © 2024 Palo Alto Networks, Inc. All rights reserved.