Edit the Cloud Content Settings

Edit the Cloud Content Settings to specify the server to send your Enterprise DLP (data loss prevention) files for scanning.

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 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 which to send your Enterprise DLP files for scanning.

Select

Device

Setup

Content-ID

and select the

Template

associated with the managed firewalls that are leveraging Enterprise DLP.

Edit the Cloud Content FQDN.

Edit the

Cloud Content Settings

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

United Kingdom
—

uk.hawkeye.services-edge.paloaltonetworks.com

Click

Commit and push your configuration changes to your managed firewalls leveraging Enterprise DLP.

The

Commit and Push

command is not 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.

Select

Commit

Commit to Panorama

and

Commit

Select

Commit

Push to Devices

and

Edit Selections

Select

Device Groups

and

Include Device and Network Templates

Click

Push

your configuration changes to your managed firewalls that are leveraging Enterprise DLP.

Document:Enterprise DLP Administrator’s Guide

Edit the Cloud Content Settings

Edit the Cloud Content Settings

Recommended For You

Document:Enterprise DLP Administrator’s Guide

Edit the Cloud Content Settings

Edit the Cloud Content Settings

Recommended For You

Recommended Videos