Non-File Based for Panorama
Focus
Focus
Enterprise DLP

Non-File Based for Panorama

Table of Contents


Non-File Based for
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.
  1. Log in to the
    Panorama
    web interface.
  2. Edit the Data Filtering Settings on
    Panorama
    to 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 you
    Enable Non File DLP
    after you install
    Panorama
    plugin for
    Enterprise DLP
    3.0.1.
  3. Create one or more data patterns.
  4. (
    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 be
    Shared
    to 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.
  5. (
    Optional
    ) Create a custom URL category to define URL traffic you want to exclude from inspection.
    The URL category must be
    Shared
    to 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.
  6. Select
    Objects
    DLP
    Data Filtering Profiles
    .
  7. Add
    a new data filtering profile.
  8. (
    Optional
    ) Configure the data filtering profile to scan
    File Based
    traffic.
    Data filtering profiles support scanning both file based and non-file based traffic. Select
    Yes
    to scan for both file based and non-file based traffic. Select
    No
    to 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.
  9. Configure the data filtering profile to scan
    Non-File Based
    traffic.
    Select
    Yes
    to scan for non-file based traffic.
  10. Verify that
    Shared
    is enabled.
    All
    Enterprise DLP
    data profiles must be
    Shared
    across all device groups. This setting is enabled by default and cannot be disabled.
  11. Define the match criteria.
    • If you select
      Basic
      , configure the following:
      • Primary Pattern
        Add
        one 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 the
        Threshold
        parameter. Specify
        Any
        to ignore the threshold.
        • 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
          Threshold
          .
        • More than or equal to
          —Security policy rule action triggered if
          Enterprise DLP
          detects instances of matched traffic, with a minimum being the specified
          Threshold
          .
        • Between (inclusive)
          —Security policy rule action triggered if
          Enterprise DLP
          detects any number of instances of matched traffic between the specific
          Threshold
          range.
      • Occurrence
        —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
        Operator
        and specify
        3
        as the
        Threshold
        .
      • Confidence
        —Specify the confidence level required for a Security policy rule action to be taken (
        High
        or
        Low
        ).
    • If you select
      Advanced
      , you can create expressions by dragging and dropping data patterns,
      Confidence
      levels,
      Operators
      , and
      Occurrence
      values 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
      , and
      Operator
      or
      Occurrence
      ).
  12. Select an
    Action
    (
    Alert
    or
    Block
    ) to perform on matching traffic.
    If the data profile has both Primary and Secondary Patterns, changing the data profile Action on
    Panorama
    deletes all Secondary Pattern match criteria.
  13. (
    Optional
    ) Configure the URL category list to exclude URL traffic from inspection.
    The URL category list can only be configured when
    Non-File Based
    traffic inspection is enabled.
    1. Select
      URL Category List Excluded From Non-File
      .
    2. Add
      a new URL category list.
    3. Select a predefined URL category, custom URL category or EDL.
  14. Configure the application exclusion list to exclude application traffic from inspection.
    The application list can only be configured when
    Non-File Based
    traffic inspection is enabled. At least one application list or application group is required to create a data filtering profile for inspecting non-file traffic.
    1. Select
      Application List Excluded From Non-File
      .
    2. Add
      an application filter or application group.
      If you didn’t create a custom application filter or application group, you must add the
      DLP App Exclusion Filter
      .
  15. For the
    Direction
    , only
    Upload
    is supported for inspection of non-file based traffic.
  16. Set the
    Log Severity
    recorded for files that match this rule.
    You can select
    critical
    ,
    high
    ,
    medium
    ,
    low
    , or
    informational
    . The default severity is
    informational
    .
  17. Click
    OK
    to save your changes.
  18. Attach the data filtering profile to a Security policy rule.
    1. Select
      Policies
      Security
      and specify the
      Device Group
      .
    2. Select the Security policy rule to which you want to add the data filtering profile.
    3. Select
      Actions
      and set the
      Profile Type
      to
      Profiles
      .
    4. Select the
      Data Filtering
      profile you created previously.
    5. Click
      OK
      .
  19. Commit and push the new configuration to your managed firewalls to complete the
    Enterprise DLP
    plugin installation.
    This step is required for
    Enterprise DLP
    data filtering profile names to appear in Data Filtering logs.
    The
    Commit and Push
    command isn’t recommended for
    Enterprise DLP
    configuration changes. Using the
    Commit and Push
    command 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
      1. Select
        Commit
        Commit to
        Panorama
        and
        Commit
        .
      2. Select
        Commit
        Push to Devices
        and
        Edit Selections
        .
      3. Select
        Device Groups
        and
        Include Device and Network Templates
        .
      4. Click
        OK
        .
      5. Push
        your configuration changes to your managed firewalls that are using
        Enterprise DLP
        .
    • Partial configuration push from Panorama
      You must always include the temporary
      __dlp
      administrator when performing a partial configuration push. This is required to keep
      Panorama
      and the DLP cloud service in sync.
      For example, you have an
      admin
      Panorama
      admin user who is allowed to commit and push configuration changes. The
      admin
      user made changes to the
      Enterprise DLP
      configuration and only wants to commit and push these changes to managed firewalls. In this case, the
      admin
      user is required to also select the
      __dlp
      user in the partial commit and push operations.
      1. Select
        Commit
        Commit to
        Panorama
        .
      2. Select
        Commit Changes Made By
        and then click the current Panorama admin user to select additional admins to include in the partial commit.
        In this example, the
        admin
        user is currently logged in and performing the commit operation. The
        admin
        user must click
        admin
        and then select the
        __dlp
        user. If there are additional configuration changes made by other Panorama admins they can be selected here as well.
        Click
        OK
        to continue.
      3. Commit
        .
      4. Select
        Commit
        Push to Devices
        .
      5. Select
        Push Changes Made By
        and then click the current Panorama admin user to select additional admins to include in the partial push.
        In this example, the
        admin
        user is currently logged in and performing the push operation. The
        admin
        user must click
        admin
        and then select the
        __dlp
        user. If there are additional configuration changes made by other Panorama admins they can be selected here as well.
        Click
        OK
        to continue.
      6. Select
        Device Groups
        and
        Include Device and Network Templates
        .
      7. Click
        OK
        .
      8. Push
        your configuration changes to your managed firewalls that are using
        Enterprise DLP
        .


Recommended For You