Edit the Cloud Content Settings

Edit the Cloud Content Settings to specify the server to send your Enterprise Data Loss Prevention (DLP) files for scanning.
By default, Enterprise Data Loss Prevention (DLP) is configured with a Cloud Content Fully Qualified Domain Name (FQDN) that automatically resolves to the closet Cloud Services server to scan your Enterprise DLP files. If you have specific data residency requirements, you can specify a regional Cloud Services server by editing the Cloud Content FQDN to send your Enterprise Data Loss Prevention (DLP) files for scanning.
  1. Select
    Device
    Setup
    Content-ID
    and select the
    Template
    associated with the managed firewalls leveraging Enterprise DLP.
  2. Edit the Cloud Content FQDN.
    1. Edit the
      Cloud Content Settings
      .
    2. Modify the
      Public Cloud Server
      based on your data residency requirements.
      • APAC
        apac.hawkeye.services-edge.paloaltonetworks.com
      • Europe
        eu.hawkeye.services-edge.paloaltonetworks.com
      • United States
        us.hawkeye.services-edge.paloaltonetworks.com
    3. Click
      OK
      to save your configuration changes.
  3. Commit and push your configuration changes to your managed firewalls leveraging Enterprise DLP.
    While a performing a
    Commit and Push
    is supported, it is not recommended for Enterprise DLP configuration changes and requires you to manually select the impacted templates and managed firewalls in the Push Scope Selection.
    1. Select
      Commit
      Commit to Panorama
      and
      Commit
      your configuration changes.
    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.

Recommended For You