DNS Security Setup

The DNS Security Setup guides you through basic ETP setup. These steps are required to get up and running with ETP.

Note: If your organization already deployed a location and policy, and you are already directing DNS traffic from the enterprise DNS server to ETP, you do not need to complete the DNS Security Setup process. If that’s the case, these steps are highlighted in green.

To complete the DNS Security Setup, you must configure these features:

1a. Locations

A location is a public IP address or a named collection of public IP addresses that belong to a region or geographic area in your network, such as a CIDR block for an office branch or your company headquarters.

You must create a location with the public IP addresses that apply to regions in your network. For more information, see Locations and Create a location.

After this step is completed, you can create a policy.

1b. Policies

A policy is a group of settings that define how ETP handles known or suspected threat events and access control events. You assign a policy to a location.

To complete this step, you must create a policy and assign the location you created to the policy. For more information, see Policies and Create a policy.

After this step is completed, you can deploy the location and policy to the ETP network.

1c. Deploy

Your policy and location configuration does not take effect until you deploy them to the ETP network. For instructions, see Deploy configuration changes. For more information, see Deploying configuration changes.

1d. DNS Forwarding

You must forward external DNS traffic from your enterprise DNS server or Active Directory server to ETP. This step is necessary for your ETP implementation. For more information, see DNS forwarding.