: Create a Data Profile with Data Patterns and EDM Data Sets on Strata Cloud Manager
Focus
Focus

Create a Data Profile with Data Patterns and EDM Data Sets on Strata Cloud Manager

Table of Contents

Create a Data Profile with Data Patterns and EDM Data Sets on
Strata Cloud Manager

Create and configure an
Enterprise Data Loss Prevention (E-DLP)
data profile containing a predefined or custom data pattern and an EDM data set on
Strata Cloud Manager
.
Where Can I Use This?
What Do I Need?
  • Panorama
  • Strata Cloud Manager
  • Enterprise Data Loss Prevention (E-DLP)
    license
  • (
    Panorama
    ) Device management license
  • (
    Panorama
    ) Support license
  • (
    Panorama
    )
    Panorama
    plugin for
    Enterprise DLP
    1.0.4 or later
  • (
    Strata Cloud Manager
    )
    Prisma Access
    license
  • (
    Strata Cloud Manager
    )
    AIOps for NGFW Premium
    license
  • (
    Strata Cloud Manager
    )
    AIOps for NGFW Free
    license
Enterprise Data Loss Prevention (E-DLP)
supports creation of data profiles that contains at least one predefined or custom
Enterprise DLP
data pattern and at least one EDM dataset pattern. Data profiles with a data pattern and an EDM data set created on
Cloud Management
are viewable on
Panorama
,
Prisma Access (Panorama Managed)
,
Strata Cloud Manager
, and the DLP app on the hub.
When you create a data profile using predefined data 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.
Updating a data profile to include only data patterns isn’t supported if the data profile includes at least one data pattern and one EDM data set when it was initially created. However, updating a data profile that includes both EDM data sets and data patterns to only include EDM data sets is supported.
See Create a Data Profile on Strata Cloud Manager to create a data profile containing only predefined or custom data patterns. See Create a Data Profile with EDM Data Sets on Strata Cloud Manager to create a data profile containing only EDM data sets.
  1. Log into
    Strata Cloud Manager
    .
  2. Select
    Manage
    Configuration
    Security Services
    Data Loss Prevention
    Data Profiles
    and
    Add Data Profile
    Advanced 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.
  3. 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.
    1. Enter a descriptive
      Data Profile Name
      .
    2. Select the data pattern operator (
      AND
      or
      OR
      ).
    3. Add Data Pattern
      .
    4. Define the data pattern 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
        ).
      • Unique Occurrences
        —Check (enable) to detect only unique instances of traffic matches. Only unique occurrences of traffic matches are counted toward the specified
        Count
        .
        This setting is disabled by default. Keep
        Unique Occurrences
        disabled if you want all instances of traffic matches to count toward the specified
        Count
        .
    5. Add EDM Dataset
      and define the match criteria.
      See Create a Data Profile with EDM Data Sets on Strata Cloud Manager for more information on configuring EDM data set match criteria in a data profile.
      • EDM Dataset
        —Select an EDM data set uploaded to the DLP cloud service.
      • 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
        .
    6. Configure the EDM data set
      Primary Fields
      values.
      1. Configure whether a Security policy rule action is taken if
        Any (OR)
        or
        All (AND)
        primary fields are matched and if
        Any (OR)
        or
        All (AND)
        secondary fields are matched.
      2. (
        Any(OR) only
        ) Enter the
        Count
        to specify the number of instances of matched traffic required to trigger a Security policy rule action. Range is
        1
        -
        500
        .
        When you select
        Any (OR)
        , the maximum
        Count
        setting is one less than the total number of fields included in the
        Primary Field
        or
        Secondary Field
        .
      3. Select the
        Primary Fields
        values.
        The list of available values is populated from the selected EDM data set. You must select at least one primary field value.
        You’re required to add at least one column where the column values occurs up to 12 times in the selected EDM data set for the
        Primary 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.
    7. (
      Optional
      )
      Add Group
      to nest additional match criteria for a data pattern or EDM data set so you can more accurately define your compliance rules.
      When you click
      Add Group
      , the new match criteria group is nested under the most recently added data pattern or EDM data set. You can’t nest a new match criteria group between existing data patterns or EDM data sets. If multiple data patterns or EDM data sets are added, you must remove the data patterns or EDM data sets that follow the data pattern or EDM data set for which you want to add the nested match criteria. For example, you added
      EDM_Dataset1
      ,
      Data_Pattern2
      , and
      EDM_Dataset3
      to the Primary Rule. If you wanted to added nested match criteria to
      Data_Pattern2
      , you must first remove
      EDM_Dataset3
      from the Primary Rule.
      You can select the same data pattern or EDM data set or a different data pattern EDM data set to more accurately define your compliance rules. Nesting match criteria is supported only when the data profile includes an EDM data set.
      Enterprise DLP
      supports up to three level of additional nesting groups for each data pattern or EDM data set. You can nest additional data patterns or EDM data sets under a data pattern or EDM data set added to the Primary or Secondary Rule.
      Nested match criteria support the
      AND
      ,
      OR
      , and
      NOT
      operators. Refer to the descriptions above to configure the nested match criteria.
    8. (
      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 pattern conditions. If you want to allow traffic that matches a data pattern match criteria, add it to the Primary Rule.
    9. Review the
      Data Profile Preview
      to verify the data profile match criteria.
    10. Save
      the data profile.

Recommended For You