1. Home
    2. Enterprise DLP
    3. Enterprise DLP Administrator’s Guide
    4. Set Up Enterprise DLP
    5. Set Up the Enterprise DLP Plugin on Panorama
    6. Edit the Enterprise DLP Settings
    7. Edit the Cloud Content Settings

    Edit the Cloud Content Settings

    Edit the Cloud Content Settings to specify the server to send your
    Enterprise data loss prevention (DLP)
     files for inspection.
    By default,
    Enterprise data loss prevention (DLP)
     is configured using a Cloud Content Fully Qualified Domain Name (FQDN) that automatically resolves to the closet Cloud Services server to inspect matching traffic. If you have specific data residency requirements, you can specify a regional Cloud Services server by editing the Cloud Content FQDN to which to send your
    Enterprise DLP
     traffic for inspection.
    2. Select
      Device
      Setup
      Content-ID
       and select the
      Template
       associated with the managed firewalls using
      Enterprise DLP
      .
    3. Edit the Cloud Content FQDN.
      1. Edit the
        Cloud Content Settings
        .
      2. Modify the
        Public Cloud Server
         based on your data residency requirements.
        Enterprise DLP
         data and data processing, including Incidents, reports, and DLP verdicts, are generated in the specified Public Cloud Server region.
        Enterprise DLP
         is configured to resolve to the closest Public Cloud Server by default.
        • Default
          —
          hawkeye.services-edge.paloaltonetworks.com
          The default Public Cloud Server automatically resolves to the closest Public Cloud Server to where the inspected traffic originated. If a new Public Cloud Server is deployed in a region closer to where the inspected traffic originated,
          Enterprise DLP
           data and data processing is generated in that new region.
        • APAC
          —
          apac.hawkeye.services-edge.paloaltonetworks.com
        • Australia
          —
          au.hawkeye.services-edge.paloaltonetworks.com
        • Europe
          —
          eu.hawkeye.services-edge.paloaltonetworks.com
        • India
          —
          in.hawkeye.services-edge.paloaltonetworks.com
        • United States
          —
          us.hawkeye.services-edge.paloaltonetworks.com
        • United Kingdom
          —
          uk.hawkeye.services-edge.paloaltonetworks.com
      3. Click
        OK
        .
    4. Commit and push your configuration changes to your managed firewalls using
      Enterprise DLP
      .
      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.
      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
        .

    Recommended For You

    Recommended Videos

    Recommended videos not found.

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

    Techdocs Logo