Dns Security Administration
Dns Security Administration
Administration
docs.paloaltonetworks.com
Contact Information
Corporate Headquarters:
Palo Alto Networks
3000 Tannery Way
Santa Clara, CA 95054
www.paloaltonetworks.com/company/contact-support
Copyright
Palo Alto Networks, Inc.
www.paloaltonetworks.com
© 2022-2022 Palo Alto Networks, Inc. Palo Alto Networks is a registered trademark of Palo
Alto Networks. A list of our trademarks can be found at www.paloaltonetworks.com/company/
trademarks.html. All other marks mentioned herein may be trademarks of their respective companies.
Last Revised
November 23, 2022
• Prisma Access (Managed by Strata Cloud Advanced DNS Security License (for
Manager) enhanced feature support) or DNS
• Prisma Access (Managed by Panorama) Security License
Palo Alto Networks® provides specialized integrated protection from DNS-based threats with two
security subscription options: DNS Security and Advanced DNS Security. These cloud-delivered
security subscriptions operate using shared underpinnings with Palo Alto Networks Threat
Prevention solutions to provide a comprehensive DNS security solution, and as such, require the
presence of an Advanced Threat Prevention or Threat Prevention subscription.
The DNS Security cloud service is designed to protect your organization from a multitude of
advanced DNS-based threats. By applying advanced machine learning and predictive analytics
to a diverse range of threat intelligence sources, DNS Security rapidly generates enhanced DNS
signatures to defend against known malicious DNS categories, as well as real-time analysis of
DNS requests to defend your network against newly generated and unknown malicious domains.
DNS Security can detect various DNS threats, including DNS tunneling, DNS rebinding attacks,
domains created using auto-generation, malware hosts, and many more.
With an active threat prevention solution operating on supported network security platforms,
customers can sinkhole DNS requests using a list of domains generated by Palo Alto Networks.
These locally-accessed, customizable DNS signature lists are packaged with antivirus and
WildFire updates and include the most relevant threats for policy enforcement and protection
at the time of publication. For improved coverage against threats using DNS, the DNS Security
subscription enables users to access real-time protections using advanced predictive analytics.
Using techniques such as DGA/DNS tunneling detection and machine learning, threats hidden
within DNS traffic can be proactively identified and shared through an infinitely scalable cloud
service. Because the DNS signatures and protections are stored in a cloud-based architecture,
you can access the full database of ever-expanding signatures that have been generated using
a multitude of data sources. This allows you to defend against an array of threats using DNS
in real-time against newly generated malicious domains. To combat future threats, updates to
the analysis, detection, and prevention capabilities of the DNS Security service will be available
through content releases.
5
About DNS Security Subscription Services
To access the basic DNS Security service, you must have a valid Advanced Threat
Prevention or Threat Prevention license and Advanced DNS Security or DNS Security
license in addition to any base licenses required to operate your network security
platform.
DNS Security subscriptions are available on the following Palo Alto Networks network security
platforms:
• Next-Generation firewalls, including the VM-Series and the CN-Series
• Prisma Access
The Advanced DNS Security service is a complementary subscription offering that operates in
conjunction with the DNS Security subscription which enabled access to new domain detectors
in the Advanced DNS Security cloud that inspect changes in DNS responses to detect various
types of DNS hijacking in real-time. With access to Advanced DNS Security operating on PAN-
OS 11.2 and later releases, you can detect and block DNS responses from hijacked domains and
misconfigured domains. Hijacked and misconfigured domains can be introduced into your network
by either directly manipulating DNS responses or by exploiting configuration settings of the DNS
infrastructure of an organization in order to redirect the user to a malicious domain from which
they initiate additional attacks. The primary difference between these two techniques is where
the exploit occurs. In the case of DNS hijacking, the attackers gains the ability to resolve DNS
queries to attacker-operated domains by compromising some aspect of an organization's DNS
infrastructure, be it the DNS provider’s administrative access, an MiTM attack during the DNS
resolution process, or the DNS server itself. Misconfigured domains present a similar problem
- the attacker seeks to incorporate their own malicious domain into an organization’s DNS by
taking advantage of domain configuration issues, outdated DNS records allowing attackers to take
ownership of the customer’s subdomain.
Advanced DNS Security can detect and categorize hijacked and misconfigured domains in real-
time by operating cloud based detection engines, which provide DNS health support by analyzing
DNS responses using ML-based analytics to detect malicious activity. Because these detectors are
located in the cloud, you can access a wide array of detection mechanisms that are updated and
deployed automatically without requiring the user to download update packages when changes to
detectors are made. Upon initial release, Advanced DNS Security supports two analysis engines:
DNS Misconfiguration Domains and Hijacking Domains. Additionally, DNS responses for all DNS
queries are sent to the Advanced DNS Security cloud for enhanced response analysis to more
accurately categorize and return a result in a real-time exchange. Analysis models are delivered
through content updates, however, enhancements to existing models are performed as a cloud-
side update, requiring no firewall update. Advanced DNS Security is enabled and configured
through the Anti-Spyware (or DNS Security) profile and require active Advanced DNS Security
and Advanced Threat Prevention (or Threat Prevention) licenses.
To access the Advanced DNS Security service, you must have a valid Advanced Threat
Prevention or Threat Prevention license and Advanced DNS Security license in addition to
any base licenses required to operate your network security platform.
Advanced DNS Security subscriptions are available on the following Palo Alto Networks network
security platforms:
• Next-Generation firewalls, including the VM-Series and the CN-Series
Learn about deploying and monitoring DNS Security and Advanced DNS Security in your network:
• Prisma Access (Managed by Strata Cloud Advanced DNS Security License (for
Manager) enhanced feature support) or DNS
• Prisma Access (Managed by Panorama) Security License
As cloud-based services, Advanced DNS Security and DNS Security allow you to access an
infinitely scalable DNS signature and protections source to defend your organization from
malicious domains. Domain signatures and protections generated by Palo Alto Networks are
derived from a multitude of sources, including WildFire traffic analysis, passive DNS, active
web crawling & malicious web content analysis, URL sandbox analysis, Honeynet, DGA reverse
engineering, telemetry data, whois, the Unit 42 research organization, and third party data
sources such as the Cyber Threat Alliance. This on-demand cloud database provides users with
access to the complete Palo Alto Network’s DNS signature set, including signatures generated
using advanced analysis techniques, as well as real-time DNS request analysis. Locally available,
downloadable DNS signature sets (packaged with the antivirus and WildFire updates) come with
a hard-coded capacity limitation of 100k signatures and do not include signatures generated
through advanced analysis. To better accommodate the influx of new DNS signatures being
produced on a daily basis, the cloud-based signature database provides users with instant access
to newly added DNS signatures without the need to download updates. If network connectivity
goes down or is otherwise unavailable, the firewall uses the onbox DNS signature set.
The DNS Security service operates real-time DNS request analysis using predictive analytics
and machine learning on multiple DNS data sources. This is used to generate protections for
DNS-based threats, which are accessible in real-time through configuration of the Anti-Spyware
Security profile attached to a Security policy rule. Each DNS threat category (the DNS Signature
Source) allows allow you to define separate policy actions as well as a log severity level for a
specific signature type. This enables you to create specific security policies based on the nature
of the threat, according to your network security protocols. Palo Alto Networks also generates
and maintains a list of explicitly allowable domains based on metrics from PAN-DB and Alexa.
These allow list domains are frequently accessed and known to be free of malicious content. The
DNS Security categories and the allow list are updated and extensible through PAN-OS content
releases.
PAN-OS 9.1 and earlier has a limited range of DNS Security source categories.
DNS Security and Advanced DNS Security currently supports detection of the following DNS
threat categories:
The universal threat ID number (indicated as ID in the Threat logs) maps to a specific
DNS detection mechanism used by DNS Security to classify domains. This shows the
precise categorization of the domain, alongside the broadly defined threat category, that
it belongs to.
• Command and Control Domains—C2 includes URLs and domains used by malware and/or
compromised systems to surreptitiously communicate with an attacker’s remote server to
receive malicious commands or exfiltrate data (this includes DNS tunneling detection and DGA
detection), or deplete resources on a target authoritative DNS servers (such as NXNSattack).
• DNS Tunnel Detection (UTID: 109001001/109001002)—DNS tunneling can be used
by attackers to encode data of non-DNS programs and protocols within DNS queries
and responses. This provides attackers with an open back channel with which they can
transfer files or remotely access the system. DNS tunnel detection uses machine learning
to analyze the behavioral qualities of DNS queries, including n-gram frequency analysis of
domains, entropy, query rate, and patterns to determine if the query is consistent with a
DNS tunneling-based attack. This includes certain next-generation DNS tunneling malware
that exfiltrates data slowly across multiple domains to avoid detection, such as TriFive and
Snugy. Combined with the firewall’s automated policy actions, this allows you to quickly
detect C2 or data theft hidden in DNS tunnels and to automatically block it, based on your
defined policy rules.
Domains that are determined to possess DNS tunneling capabilities are further
analyzed to provide details about the tools used to embed data onto DNS queries and
responses and the associated malware campaign name by DNS Security. The attribution
details are available in the threat logs as Threat ID/Name for the firewall and DNS
Security logs on Prisma Access as Threat Name Firewall using the following format:
Tunneling:<optional_list_of_tools/campaigns; dot-separated string)>:<domain_name> or
Tunneling_infil:<optional_list_of_tools/campaigns; dot-separated string)>:<domain_name>
based on the specific DNS tunnel domain type.
• DGA Domain Detection (UTID: 109000001)—Domain generation algorithms (DGAs) are
used to auto-generate domains, typically in large numbers within the context of establishing
a malicious command-and-control (C2) communications channel. DGA-based malware (such
as Pushdo, BankPatch, and CryptoLocker) limit the number of domains from being blocked
by hiding the location of their active C2 servers within a large number of possible suspects,
and can be algorithmically generated based on factors such as time of day, cryptographic
keys, dictionary-derived naming schemes, and other unique values. While most domains
generated by a DGA do not resolve as a valid domain, they must all be identified to fully
defend against a given threat. DGA analysis determines whether a domain is likely to have
been generated by a machine, rather than a person, by reverse-engineering and analyzing
other frequently used techniques found in DGAs. Palo Alto Networks then uses these
characteristics to identify and block previously unknown DGA-based threats in real-time.
• NXNSAttack (UTID: 109010007)—The NXNSAttack vulnerability present in the DNS
protocol affects all recursive DNS resolvers and can be used by malicious actors to launch
DDOS-like amplification attacks to disrupt the normal operation of vulnerable authoritative
DNS servers. NXNSAttack can introduce massive traffic spikes on an authoritative DNS
server by forcing the recursive DNS resolver to issue a large number of invalid requests to
potentially shut down the server.
• DNS Rebinding (UTID: 109010009)—DNS rebinding attacks lure users to an attacker-
controlled domain configured with a short TTL parameter to manipulate how domain names
are resolved to exploit and bypass the same-origin policy in browsers. This enables malicious
actors to use the client machine as an intermediary to attack or access a resource contained
within a private network.
• DNS Infiltration (UTID: 109001003)—DNS infiltration includes DNS queries that enable
malicious actors to hide and resolve minute payloads via a response to fraudulent A (IPv4)
and AAAA (IPv6) record requests. When the client resolves multiple subdomains, each
containing a A/AAAA record with an encoded component, the data contained within them
can be consolidated to form a malicious payload, which can then be executed on the client
machine. After executing the payload, it can introduce secondary payloads to establish a
DNS tunnel or additional exploits.
• DNS Traffic Profiling (UTID: 109010010)—(Requires Advanced DNS Security) DNS traffic
profiling is a cloud-based analyzer that detects malware attempting to establish a C2
connection, based on an assessment of DNS traffic patterns. As Advanced DNS Security
monitors your organization's DNS traffic, the outbound DNS request sequences are
vectorized to form DNS traffic profiles, which are then analyzed using ML techniques
that can associate the unique DNS request patterns with identifiable malicious C2 domain
profiles.
• Dynamic DNS Hosted Domains (UTID: 109020002) —Dynamic DNS (DDNS) services provide
mapping between hostnames and IP addresses in near real-time to keep changing IP addresses
linked to a specific domain, when static IPs are unavailable. This provides attackers a method of
infiltrating networks by using DDNS services to change the IP addresses that host command-
and-control servers. Malware campaigns and exploit kits can utilize DDNS services as part
of their payload distribution strategy. By utilizing DDNS domains as part of their hostname
infrastructure, adversaries can change the IP address associated with given DNS records and
more easily avoid detection. DNS Security detects exploitative DDNS services by filtering and
cross-referencing DNS data from various sources to generate candidate lists which are then
further validated to maximize accuracy.
• Malware Domains —Malicious domains host and distribute malware and can include
websites that attempt to install various threats (such as executables, scripts, viruses, drive-
by downloads). Malicious domains are distinguishable from C2 domains in that they deliver
malicious payloads into your network via an external source, whereas with C2, infected
endpoints typically attempt to connect to a remote server to retrieve additional instructions or
other malicious content.
• Malware Compromised DNS (UTID: 109003001)—Malware compromised DNS covers a
range of techniques, some legitimate, that result in the generation of seemingly genuine
hostnames and subdomains, which in actuality, are malicious. This includes newly observed
hostnames that mimic existing, reputable hostnames, in an attempt to impersonate or
otherwise mislead and evade database-centric security solutions. These can be quickly
produced en-masse to preempt their addition to database lists. Domain shadowing typically
follows after an attacker gains control of a domain account through a more conventional
attack. This provides the access necessary to create illegitimate subdomains used to
coordinate attacks, even though the root domain remains legitimate and valid, increasing the
likelihood of circumventing network security.
• Ransomware Domains (UTID: 109003002)—Ransomware is a subcategory of malware
that locks or cryptographically prevents users from accessing data in exchange for a
ransom payment, after which the system may be released back to the user by the attacker.
Ransomware can be distributed through malicious ransomware domains, which host the
seemingly legitimate files that users are tricked into downloading.
• Prisma Access (Managed by Strata Cloud Advanced DNS Security License (for
Manager) enhanced feature support) or DNS
• Prisma Access (Managed by Panorama) Security License
The DNS Security service collects server response and request information based on your security
policy rules, associated action, and the DNS query details when performing domain lookups
to generate DNS Security logs for Strata Logging Service-based activity applications (AIOps
for NGFW Free, Prisma Access, Strata Logging Service, etc). Additionally, the network security
platform forwards supplemental DNS data to the DNS Security cloud servers and is used by Palo
Alto Networks services to provide more accurate domain information (such as provider ASN,
hosting information, and geolocation identification). While this supplemental data is not necessary
to operate the DNS Security service, it provides the resources to generate improved analytics,
DNS detection, and prevention capabilities. This action occurs in less than 30 seconds after data
collection occurs. To minimize firewall performance impact, DNS Security telemetry operates with
minimal overhead, which can limit the total amount of DNS telemetry data sent to Strata Logging
Service; consequently only a subset of DNS queries are forwarded to Strata Logging Service as
DNS Security log entries. As a result, Palo Alto Networks recommends viewing logs for malicious
DNS requests as threat logs instead of DNS Security logs.
Malicious DNS queries are also recorded as threat logs and are submitted to the Strata
Logging Service using PAN-OS log forwarding (when appropriately configured).
Field Description
Response The IP address that the domain in the DNS query got resolved to.
Response Code The DNS response code that was received as an answer to your DNS
query.
Source IP The IP address of the system that made the DNS request.
Field Description
Source User When the firewall User-ID feature is enabled, the identity of the DNS
requester is shown.
Source Zone The configured source zone referenced in your security policy rule.
DNS expanded data collection is bypassed for domains added to the Allow list in DNS
Exceptions.
Data fields that can be used to potentially identify users (Source IP, Source User, and Source
Zone) can be withheld from automatic submission using the following CLI command: set
deviceconfig setting ctd cloud-dns-privacy-mask yes. You must commit the
changes for the update to take effect.
• Prisma Access (Managed by Strata Cloud Advanced DNS Security License (for
Manager) enhanced feature support) or DNS
• Prisma Access (Managed by Panorama) Security License
Palo Alto Networks maintains a network of global and regional domains that provide
service for DNS Security and Advanced DNS Security operations. These service domains
operate real-time DNS request analyzers, access to the DNS signature database and provide
advanced cloud-dependent functionality. By default, DNS Security and Advanced DNS
Security connects to the global service domains (dns.service.paloaltonetworks.com and adv-
dns.service.paloaltonetworks.com,respectively), which then automatically redirect to the regional
domain that is closest to the network security platform location.
to review the average latency. The relevant section is located under the Signature query API
heading.
The following table lists the DNS Security service domains:
Location URL
Location URL
Singapore dns-sg.service.paloaltonetworks.com
Bahrain dns-bh.service.paloaltonetworks.com
This setting does not impact how standard DNS Security queries are handled.
The following table lists the Advanced DNS Security service domains:
Location URL
Location URL
Bahrain bh.adv-dns.service.paloaltonetworks.com
Singapore sg.adv-dns.service.paloaltonetworks.com
Bahrain bh.adv-dns.service.paloaltonetworks.com
• Prisma Access (Managed by Strata Cloud Advanced DNS Security License (for
Manager) enhanced feature support) or DNS
• Prisma Access (Managed by Panorama) Security License
Before you can enable and configure Advanced DNS Security or DNS Security, you must obtain
and install a Threat Prevention (or Advanced Threat Prevention) license as well as an Advanced
DNS Security or DNS Security license in addition to any platform licenses from where it is
operated. Licenses are activated from the Palo Alto Networks Customer Support Portal and
must be active before DNS analysis can take place. Additionally, DNS Security subscription
services (similar to other Palo Alto Networks security services) are administered through security
profiles, which in turn is dependent on the configuration of network enforcement policies as
defined through security policy rules. Before enabling a DNS Security subscription service, it is
recommended that you familiarize yourself core components of the security platform in which the
security subscriptions are enabled. Refer to your product documentation for more information.
To enable and configure a DNS Security subscription service to function optimally within
your network security deployment, refer to the tasks below. While it may not be necessary
to implement all of the processes shown here, Palo Alto Networks recommends reviewing all
of the tasks to familiarize yourself with the available options for a successful deployment. It is
additionally recommended that you follow the best practices provided by Palo Alto Networks for
the optimum usability and security.
• Enable DNS Security or Advanced DNS Security on my network security platform to prevent
DNS threats from entering my network (required)
• Create domain signature exceptions and allow lists to limit false-positives and prevent internal
DNS servers from triggering DNS categorization
• Test the configured policy actions for the available domain categories
• Verify my firewall’s connectivity to the DNS Security service
• Limit dropped connections due to my latency by customizing my DNS lookup timeout setting
on the firewall
19
Configure DNS Security Subscription Services
• Prisma Access (Managed by Strata Cloud Advanced DNS Security License (for
Manager) enhanced feature support) or DNS
• Prisma Access (Managed by Panorama) Security License
To enable DNS Security, you must create (or modify) an Anti-Spyware security profile to access
the DNS Security service, configure the log severity and policy settings for the DNS signature
category (or categories), and then attach the profile to a security policy rule.
• Strata Cloud Manager
• PAN-OS & Panorama
STEP 2 | Verify that a DNS Security and a Threat Prevention (or Advanced Threat Prevention) license
is active. Select Manage > Configuration > NGFW and Prisma Access > Overview and click
the license usage terms link in the License panel. You should see green check marks next to
the following security services: Antivirus, Anti-Spyware, Vulnerability Protection, and DNS
Security.
STEP 3 | Verify that the paloalto-dns-security App-ID in your security policy is configured to enable
traffic from the DNS security cloud security service.
STEP 4 | Configure DNS Security signature policy settings to send malicious DNS queries to the
defined sinkhole.
If you use an external dynamic list as a domain allow list, it does not have precedence
over the DNS Security domain policy actions. As a result, when there is a domain
match to an entry in the EDL and a DNS Security domain category, the action
specified under DNS Security is still applied, even when the EDL is explicitly configured
with an action of Allow. If you want to add DNS domain exceptions, either configure
an EDL with an Alert action or add them to the DNS Domain/FQDN Allow List located
in the DNS Exceptions tab.
1. Select Manage > Configuration > NGFW and Prisma Access > Security Services > DNS
Security.
2. Create or modify an existing DNS Security profile.
3. Name the profile and, optionally, provide a description.
4. In the DNS Categories section, beneath the DNS Security heading, there are individually
configurable DNS signature sources, which allow you to define separate policy actions as
well as the packet capture setting.
Palo Alto Networks recommends using the default action setting for all signature
sources to ensure optimum coverage as well as to assist with incidence response
and remediation. For more information about the best practices for configuring
your DNS Security settings, refer to Best Practices for Securing Your Network
from Layer 4 and Layer 7 Evasions.
• Select an action to be taken when DNS lookups are made to known malware sites for
the DNS Security signature source. The options are alert, allow, block, or sinkhole.
Palo Alto Networks recommends setting the action to sinkhole.
• You can fully bypass DNS traffic inspection by configuring a policy action of Allow
with a corresponding log severity of None for each DNS signature source.
• In the Packet Capture drop-down, select single-packet to capture the first packet of
the session or extended-capture to set between 1-50 packets. You can then use the
packet captures for further analysis.
5. In the DNS Sinkhole Settings section, verify that a valid Sinkhole address is present.
For your convenience, the default setting (pan-sinkhole-default-ip) is set to access a
Palo Alto Networks sinkhole server. Palo Alto Networks can automatically refresh this
address through updates.
Sinkhole forges a response to a DNS query for domains that match the DNS
category configured for a sinkhole action to the specified sinkhole server, to
assist in identifying compromised hosts. When the default sinkhole FQDN is
used, the firewall sends the CNAME record as a response to the client, with
the expectation that an internal DNS server will resolve the CNAME record,
allowing malicious communications from the client to the configured sinkhole
server to be logged and readily identifiable. However, if clients are in networks
without an internal DNS server, or are using software or tools that cannot
be properly resolve a CNAME into an A record response, the DNS request is
dropped, resulting in incomplete traffic log details that are crucial for threat
analysis. In these instances, you should use the following sinkhole IP address:
(72.5.65.111).
If you want to modify the Sinkhole IPv4 or Sinkhole IPv6 address to a local server on
your network or to a loopback address, see Configure the Sinkhole IP Address to a Local
Server on Your Network.
STEP 7 | Optional—Create a decryption policy rule to decrypt DNS-over-TLS / port 853 traffic. The
decrypted DNS payload can then be processed using the DNS Security profile configuration
containing your DNS policy settings. When DNS-over-TLS traffic is decrypted, the resulting
DNS requests in the threat logs will appears as a conventional dns-base application with a
source port of 853.
STEP 8 | For other monitoring options, see Monitor DNS Security Subscription Services
STEP 2 | To take advantage of DNS Security, you must have an active DNS Security and Threat
Prevention (or Advanced Threat Prevention) subscription.
Verify that you have the necessary subscriptions. To verify which subscriptions that you
currently have licenses for, select Device > Licenses and verify that the appropriate licenses
display and have not expired.
STEP 3 | Verify that the paloalto-dns-security App-ID in your security policy is configured to enable
traffic from the DNS security cloud security service.
STEP 4 | Configure DNS Security signature policy settings to send malicious DNS queries to the
defined sinkhole.
If you use an external dynamic list as a domain allow list, it does not have precedence
over the DNS Security domain policy actions. As a result, when there is a domain
match to an entry in the EDL and a DNS Security domain category, the action
specified under DNS Security is still applied, even when the EDL is explicitly configured
with an action of Allow. If you want to add DNS domain exceptions, either configure
an EDL with an Alert action or add them to the DNS Domain/FQDN Allow List located
in the DNS Exceptions tab.
Palo Alto Networks recommends changing your default DNS Policies settings for
signature sources to ensure optimum coverage as well as to assist with incidence
response and remediation. Follow the best practices for configuring your DNS
Security settings as outlined in the Best Practices for Securing Your Network
from Layer 4 and Layer 7 Evasions.
• Specify the log severity level that is recorded when the firewall detects a domain
matching a DNS signature. For more information about the various log severity levels,
refer to Threat Severity Levels.
• Select an action to be taken when DNS lookups are made to known malware sites for
the DNS Security signature source. The options are default, allow, block, or sinkhole.
Verify that the action is set to sinkhole.
• You can fully bypass DNS traffic inspection by configuring a policy action of Allow
with a corresponding log severity of None for each DNS signature source.
• In the Packet Capture drop-down, select single-packet to capture the first packet of
the session or extended-capture to set between 1-50 packets. You can then use the
packet captures for further analysis.
6. In the DNS Sinkhole Settings section, verify that Sinkhole is enabled. For your
convenience, the default Sinkhole address (sinkhole.paloaltonetworks.com) is set to
access a Palo Alto Networks server. Palo Alto Networks can automatically refresh this
address through content updates.
Sinkhole forges a response to a DNS query for domains that match the DNS
category configured for a sinkhole action to the specified sinkhole server, to
assist in identifying compromised hosts. When the default sinkhole FQDN
(sinkhole.paloaltonetworks.com) is used, the firewall sends the CNAME record
as a response to the client, with the expectation that an internal DNS server will
resolve the CNAME record, allowing malicious communications from the client
to the configured sinkhole server to be logged and readily identifiable. However,
if clients are in networks without an internal DNS server, or are using software
or tools that cannot be properly resolve a CNAME into an A record response, the
DNS request is dropped, resulting in incomplete traffic log details that are crucial
for threat analysis. In these instances, you should use the following sinkhole IP
address: (72.5.65.111).
If you want to modify the Sinkhole IPv4 or Sinkhole IPv6 address to a local server on
your network or to a loopback address, see Configure the Sinkhole IP Address to a Local
Server on Your Network.
7. (Optional) Block the specified DNS resource record types record types used to exchange
keying information during the encryption of the client hello in the subsequent TLS
connection. The following DNS RR types are available: SVCB (64), HTTPS (65), and ANY
(255).
• While it is not necessary to block ECH in order to enable DNS Security over
DoH, Palo Alto Networks currently recommends blocking all DNS record
types used by ECH for optimum security.
• Type 64 and type 65 resource record standards are still in flux (in a draft
state) and are subject to change. For more information on DNS SVCB and
HTTPS RRs, refer to: Service binding and parameter specification via the
DNS (DNS SVCB and HTTPS RRs) as defined by the IETF.
STEP 7 | Optional—Create a decryption policy rule to decrypt DNS-over-TLS / port 853 traffic. The
decrypted DNS payload can then be processed using the Anti-Spyware profile configuration
containing your DNS policy settings. When DNS-over-TLS traffic is decrypted, the resulting
DNS requests in the threat logs will appears as a conventional dns-base application with a
source port of 853.
STEP 2 | To take advantage of DNS Security, you must have an active DNS Security and Threat
Prevention (or Advanced Threat Prevention) subscription.
Verify that you have the necessary subscriptions. To verify which subscriptions that you
currently have licenses for, select Device > Licenses and verify that the appropriate licenses
display and have not expired.
STEP 3 | Verify that the paloalto-dns-security App-ID in your security policy is configured to enable
traffic from the DNS security cloud security service.
STEP 4 | Configure DNS Security signature policy settings to send malicious DNS queries to the
defined sinkhole.
If you use an external dynamic list as a domain allow list, it does not have precedence
over the DNS Security domain policy actions. As a result, when there is a domain
match to an entry in the EDL and a DNS Security domain category, the action
specified under DNS Security is still applied, even when the EDL is explicitly configured
with an action of Allow. If you want to add DNS domain exceptions, either configure
an EDL with an Alert action or add them to the DNS Domain/FQDN Allow List located
in the DNS Exceptions tab.
Palo Alto Networks recommends changing your default DNS Policies settings for
signature sources to ensure optimum coverage as well as to assist with incidence
response and remediation. Follow the best practices for configuring your DNS
Security settings as outlined in the Best Practices for Securing Your Network
from Layer 4 and Layer 7 Evasions.
• Specify the log severity level that is recorded when the firewall detects a domain
matching a DNS signature. For more information about the various log severity levels,
refer to Threat Severity Levels.
• Select an action to be taken when DNS lookups are made to known malware sites for
the DNS Security signature source. The options are default, allow, block, or sinkhole.
Verify that the action is set to sinkhole.
• You can fully bypass DNS traffic inspection by configuring a policy action of Allow
with a corresponding log severity of None for each DNS signature source.
• In the Packet Capture drop-down, select single-packet to capture the first packet of
the session or extended-capture to set between 1-50 packets. You can then use the
packet captures for further analysis.
6. In the DNS Sinkhole Settings section, verify that Sinkhole is enabled. For your
convenience, the default Sinkhole address (sinkhole.paloaltonetworks.com) is set to
access a Palo Alto Networks server. Palo Alto Networks can automatically refresh this
address through content updates.
Sinkhole forges a response to a DNS query for domains that match the DNS
category configured for a sinkhole action to the specified sinkhole server, to
assist in identifying compromised hosts. When the default sinkhole FQDN
(sinkhole.paloaltonetworks.com) is used, the firewall sends the CNAME record
as a response to the client, with the expectation that an internal DNS server will
resolve the CNAME record, allowing malicious communications from the client
to the configured sinkhole server to be logged and readily identifiable. However,
if clients are in networks without an internal DNS server, or are using software
or tools that cannot be properly resolve a CNAME into an A record response, the
DNS request is dropped, resulting in incomplete traffic log details that are crucial
for threat analysis. In these instances, you should use the following sinkhole IP
address: (72.5.65.111).
If you want to modify the Sinkhole IPv4 or Sinkhole IPv6 address to a local server on
your network or to a loopback address, see Configure the Sinkhole IP Address to a Local
Server on Your Network.
STEP 7 | Optional—Create a decryption policy rule to decrypt DNS-over-TLS / port 853 traffic. The
decrypted DNS payload can then be processed using the Anti-Spyware profile configuration
containing your DNS policy settings. When DNS-over-TLS traffic is decrypted, the resulting
DNS requests in the threat logs will appears as a conventional dns-base application with a
source port of 853.
STEP 2 | To take advantage of DNS Security, you must have an active DNS Security and Threat
Prevention subscription.
Verify that you have the necessary subscriptions. To verify which subscriptions that you
currently have licenses for, select Device > Licenses and verify that the appropriate licenses
display and have not expired.
STEP 3 | Verify that the paloalto-dns-security App-ID in your security policy is configured to enable
traffic from the DNS security cloud security service.
STEP 4 | Configure DNS Security signature policy settings to send malware DNS queries to the
defined sinkhole.
If you use an external dynamic list as a domain allow list, it does not have precedence
over the DNS Security domain policy actions. As a result, when there is a domain
match to an entry in the EDL and a DNS Security domain category, the action
specified under DNS Security is still applied, even when the EDL is explicitly configured
with an action of Allow. If you want to add DNS domain exceptions, you can configure
an EDL with an Alert action.
access a Palo Alto Networks server. Palo Alto Networks can automatically refresh this
address through content updates.
Sinkhole forges a response to a DNS query for domains that match the DNS
category configured for a sinkhole action to the specified sinkhole server, to
assist in identifying compromised hosts. When the default sinkhole FQDN
(sinkhole.paloaltonetworks.com) is used, the firewall sends the CNAME record
as a response to the client, with the expectation that an internal DNS server will
resolve the CNAME record, allowing malicious communications from the client
to the configured sinkhole server to be logged and readily identifiable. However,
if clients are in networks without an internal DNS server, or are using software
or tools that cannot be properly resolve a CNAME into an A record response, the
DNS request is dropped, resulting in incomplete traffic log details that are crucial
for threat analysis. In these instances, you should use the following sinkhole IP
address: (72.5.65.111).
If you want to modify the Sinkhole IPv4 or Sinkhole IPv6 address to a local server on
your network or to a loopback address, see Configure the Sinkhole IP Address to a Local
Server on Your Network.
9. Click OK to save the Anti-Spyware profile.
STEP 7 | Optional—Create a decryption policy rule to decrypt DNS-over-TLS / port 853 traffic. The
decrypted DNS payload can then be processed using the Anti-Spyware profile configuration
containing your DNS policy settings. When DNS-over-TLS traffic is decrypted, the resulting
DNS requests in the threat logs will appears as a conventional dns-base application with a
source port of 853.
• NGFW (Managed by Strata Cloud Manager) Advanced DNS Security License (for
• NGFW (Managed by PAN-OS or Panorama) enhanced feature support)
Advanced DNS Security supplements your existing DNS Security configuration to provide
additional protection against DNS hijacking by inspecting changes to DNS responses. You should
have fully configured DNS Security settings before proceeding with this step.
To enable Advanced DNS Security, you must create (or modify) an Anti-Spyware security profile
to access the Advanced DNS Security service, configure the log severity and policy settings for
the DNS signature category (or categories), and then attach the profile to a security policy rule.
• PAN-OS 11.2 and later
STEP 3 | To prevent access to known and unknown malicious domains using Advanced DNS Security,
you must have an active Advanced DNS Security license. This should only be installed after
upgrading to PAN-OS 11.2.
Advanced DNS Security supports a licensing model that subsumes DNS Security
functionality into the Advanced DNS Security license when installed on a previously
unlicensed firewall. If you upgrade from a firewall with an existing DNS Security
license, entries indicating the presence of separate DNS Security and Advanced
DNS Security licenses are displayed. In this instance, the DNS Security license is
a passive entry and all DNS Security and Advanced DNS Security functionality is
conferred through the Advanced DNS License, including the relevant expiration date.
Firewalls without a previously installed DNS Security license show an Advanced DNS
Security license, however, it provides both DNS Security and Advanced DNS Security
functionality.
Consequently, if you downgrade from a PAN-OS release operating an Advanced DNS
Security license to a release that does not support Advanced DNS Security, the firewall
continues to display and confer DNS Security functionality through the Advanced DNS
Security license, however, it is limited to base DNS Security features.
To verify subscriptions for which you have currently-active licenses, select Device > Licenses
and verify that the appropriate licenses are available and have not expired.
STEP 4 | Update or create a new Anti-Spyware Security profile to enable real-time Advanced DNS
Security queries. Typically, this is your existing Anti-Spyware security profile used for the
DNS Security configuration.
1. Select an existing Anti-Spyware security profile or Add a new one (Objects > Security
Profiles > Anti-Spyware).
2. Select your Anti-Spyware security profile and then go to DNS Policies.
3. For each Advanced DNS Security domain category, specify a Log Severity and Policy Action
to take when a domain type is detected using a corresponding analysis engine. There are
currently two analysis engines available: DNS Misconfiguration Domains and Hijacking
Domains.
Policy Action Options:
• allow—The DNS query is allowed.
You can configure the firewall to generate an alert when the applicable
domain type is detected by setting the action to allow and the log severity to
informational.
• block—The DNS query is blocked.
• sinkhole—Forges a DNS response for a DNS query targeting a detected malicious
domain. This directs the resolution of the malicious domain name to a specific IP
address (referred to as the Sinkhole IP), which is embedded as the response. The default
Sinkhole IP address is set to access a Palo Alto Networks server. Palo Alto Networks can
automatically refresh this IP address through content updates.
Log Severity Options:
• none—The event does not have an associated log severity level.
• low—Warning-level threats that have very little impact on an organization's
infrastructure. They usually require local or physical system access and may often result
in victim privacy or DoS issues and information leakage.
• informational—Suspicious events that do not pose an immediate threat, but that are
reported to call attention to deeper problems that could possibly exist.
• medium—Minor threats in which impact is minimized, such as DoS attacks that do not
compromise the target or exploits that require an attacker to reside on the same LAN as
the victim, affect only non-standard configurations or obscure applications, or provide
very limited access.
• high—Threats that have the ability to become critical but have mitigating factors; for
example, they may be difficult to exploit, do not result in elevated privileges, or do not
have a large victim pool.
• critical—Serious threats, such as those that affect default installations of widely deployed
software, result in root compromise of servers, and the exploit code is widely available
to attackers. The attacker usually does not need any special authentication credentials or
knowledge about the individual victims and the target does not need to be manipulated
into performing any special functions.
4. Click OK to exit the Anti-Spyware Security Profile configuration dialog and Commit your
changes.
STEP 5 | (Optional) Specify any public-facing parent domains within your organization that you want
Advanced DNS Security to analyze and monitor for the presence of misconfigured domains.
Misconfigured domains are inadvertently created by domain owners who point alias records
to third party domains using CNAME, MX, NS record types, using entries that are no longer
valid, allowing an attacker to take over the domain by registering the expired or unused
domains.
TLDs (top-level domains) and root level domains cannot be added to the DNS Zone
Misconfigurations list.
1. Select an Anti-Spyware security profile (Objects > Security Profiles > Anti-Spyware) and go
to DNS Policies.
2. In the DNS Zone Misconfigurations section, add public-facing parent domains with an
optional description to assist you in identifying domain usage or ownership within your
organization.
Entries must have a "." contained in the domain using the following format (e.g.
paloaltonetworks.com), otherwise it gets parsed as a hostname, which is considered
a private domain.
3. Click OK to exit the Anti-Spyware Security Profile configuration dialog and Commit your
changes.
STEP 6 | (Optional) Configure the maximum Advanced DNS signature lookup timeout setting. When
this value is exceeded, the DNS response passes through without performing analysis using
Advanced DNS Security.
STEP 7 | (Optional [If you do not have the latest device certificate]) Install an updated firewall device
certificate used to authenticate to the Advanced Threat Prevention inline cloud analysis
service. Repeat for all firewalls enabled for inline cloud analysis.
If you have already installed an updated firewall device certificate as part of your IoT Security,
Device Telemetry, Advanced Threat Prevention, or Advanced URL Filtering onboarding
process, this step is not necessary.
STEP 8 | (Optional) Verify the status of your firewall connectivity to the Advanced DNS Security cloud
service.
STEP 9 | (Optional) Monitor activity on the firewall for DNS queries that have been detected using
Advanced DNS Security. DNS Security Categories analyzed using Advanced DNS Security
real-time analysis of the DNS response packet have the prefix ‘adns’ followed by the
category. For example, adns-dnsmisconfig, whereby ‘dnsmisconfig’ indicates the supported
DNS category type. If the DNS domain category was determined by analyzing the DNS
request packet, the specified category is displayed with the prefix ‘dns’ followed by the
category. For example, ‘dns-grayware.’
1. Access the Advanced DNS Security test domains to verify that the policy action for a
given threat type is being enforced.
2. Select Monitor > Logs > Threat. You can filter the logs based on the specific type of
Advanced DNS Security domain category, for example ( category-of-threatid
You must operate a firewall running PAN-OS 11.2 and later to take advantage
of enhanced Advanced DNS Security real-time analysis.
• DNS —adns-benign
• Malware Domains —adns-malware
• Command and Control Domains—adns-c2
• Phishing Domains—adns-phishing
• Dynamic DNS Hosted Domains—adns-ddns
• Newly Registered Domains—adns-new-domain
• Grayware Domains—adns-grayware
• Parked Domains—adns-parked
• Proxy Avoidance and Anonymizers—adns-proxy
• Ad Tracking Domains—adns-adtracking
If the DNS query does not complete within the specified timeout period for
Advanced DNS Security, the DNS Security categorization will be used, when
possible. In those instances, the legacy notation for the category is used, for
example, instead of adns-malware, it will be categorized as dns-malware,
indicating that the DNS Security categorization value was used.
3. Select a log entry to view the details of the DNS query.
4. The DNS Category is displayed under the Details pane of the detailed log view. In
addition, you can see other aspects of the threat, including the Threat ID, which
includes the origin domain, the specific threat category, and other associated
characteristics, as well as the associated Q type, and R data using the following format:
hijacking:<FQDN>:<QTYPE>:<RDATA>, whereby <QTYPE> represents the DNS
resource record type and <RDATA> represents the hijacked IP Address.
STEP 10 | (Optional) Retrieve a list of misconfigured domains and hijacked domains detected by the
Advanced DNS Security service. The misconfigured domains are based on the public-facing
parent domain entries added to DNS Zone Misconfigurations.
Misconfigured domain entries that are removed from your network are not
immediately reflected in the Advanced DNS Security dashboard statistics.
1. Use the credentials associated with your Palo Alto Networks support account and log in
to Strata Cloud Manager on the hub.
2. Select Dashboards > More Dashboards > DNS Security to open the DNS Security
dashboard.
3. From the DNS Security dashboard, refer to the following widgets:
• Misconfigured Domains—View a list of non-resolvable domains associated with
the user-specified public-facing parent domain(s). For each entry, there is a
misconfiguration reason and a traffic hit count based on the source IP.
• Prisma Access (Managed by Strata Cloud Advanced DNS Security License (for
Manager) enhanced feature support) or DNS
• Prisma Access (Managed by Panorama) Security License
You can get visibility and control into DNS Security over TLS requests by decrypting the DNS
payload contained within the encrypted DNS request. The decrypted DNS payload can then
be processed using the security profile configuration containing your DNS policy settings. DNS
requests that have been determined to have originated from TLS sources have a source port of
853 in the threat logs.
• Strata Cloud Manager
• PAN-OS & Panorama
STEP 2 | Enable DNS Security is configured to inspect DNS requests. You can use your existing
security profile if you want to use the same DNS Policies settings for DNS Security over TLS
traffic.
STEP 3 | Create a decryption policy rule with an action to decrypt HTTPS traffic on port 853, which
includes DNS Security over TLS traffic (refer to the Decryption Best Practices for more
information). When DNS Security over TLS traffic is decrypted, the resulting DNS requests in
the logs appear as conventional dns-base applications.
STEP 4 | (Optional) Search for activity on the firewall for decrypted TLS-encrypted DNS queries that
have been processed using DNS Security.
1. Select Activity > Log Viewer and select Threat logs. Use the query builder to filter
based on the application using dns-base and port 853 (which is exclusively used
for DNS Security over TLS transactions), for example, app = 'dns-base' AND
source_port = 853.
2. Select a log entry to view the details of the detected DNS threat.
3. The Application should display dns-base in the General pane and the Port in the Source
pane of the detailed log view. Other relevant details about the threat are displayed in
their corresponding tabs.
STEP 2 | Enable DNS Security is configured to inspect DNS requests. You can use your existing
security profile if you want to use the same DNS Policies settings for DNS Security over TLS
traffic.
STEP 3 | Create a decryption policy rule (similar to the example below) with an action to decrypt
HTTPS traffic on port 853, which includes DNS Security over TLS traffic (refer to the
Decryption Best Practices for more information). When DNS Security over TLS traffic
is decrypted, the resulting DNS requests in the logs appear as conventional dns-base
applications.
STEP 4 | (Optional) Search for activity on the firewall for decrypted TLS-encrypted DNS queries that
have been processed using DNS Security.
1. Select Monitor > Logs > Traffic and filter based on the application using dns-base and
port 853 (which is exclusively used for DNS Security over TLS transactions), for example,
( app eq dns-base ) and ( port.src eq 853 ).
2. Select a log entry to view the details of a detected DNS threat.
3. The Application should display dns-base in the General pane and the Port in the Source
pane of the detailed log view. Other relevant details about the threat are displayed in
their corresponding windows.
• Prisma Access (Managed by Strata Cloud Advanced DNS Security License (for
Manager) enhanced feature support) or DNS
• Prisma Access (Managed by Panorama) Security License
You can analyze and categorize the DNS payload contained within encrypted DNS traffic requests
to DNS hosts using HTTPS (DoH—[DNS-over-HTTPS]). If your organization currently blocks
all DoH requests as Palo Alto Networks recommends, you can transition away from that policy
as DNS Security now enables you extract the DNS hostname from the encrypted request and
apply your organization’s existing DNS Security policies. This allows you to safely access more
websites as support for DoH widens. DNS Security support for DoH is enabled by configuring
the firewall to decrypt the payload of DNS requests originating from a user-specified list of
DNS resolvers, providing support for a range of server options. The decrypted DNS payload
can then be processed using the Anti-spyware profile configuration containing your DNS policy
configuration. DNS requests that have been determined to be DoH are labeled as dns-over-https
in the traffic logs.
• Strata Cloud Manager
• PAN-OS 11.0 and later
STEP 2 | Create a Custom URL Category list that includes all DoH resolvers you want to enable traffic
to/from (you will need the DNS server URL(s)).
STEP 3 | Create a Decryption Policy Rule that references the custom URL category list that you
created in the previous step.
STEP 4 | Update or create a new anti-spyware security profile used to inspect DoH requests.
STEP 5 | Create or update a security policy rule and reference a DNS Security profile and a custom
URL category list (Manage > Configuration > PAN-OS and Prisma Access > Security
Services > URL Access Management) containing the approved list of DoH servers.
STEP 6 | Create a block policy to decrypt HTTPS traffic and block all remaining unsanctioned DoH
traffic that is not explicitly allowed by the custom URL category list (referenced in step 5) by
using the App-ID: dns-over-https and the following URL category: encrypted-dns.
If you already have an existing block policy to block DoH traffic, verify that the rule
is placed below the previous security policy rule used to match with specific DoH
resolvers listed in a custom URL category list object.
STEP 7 | (Optional) Search for activity on the firewall for HTTPS-encrypted DNS queries that have
been processed using DNS Security.
1. Select Activity > Logs > Log Viewer and select Threat.
2. Submit a log query based on the application, using dns-over-https, for example, app =
'dns-over-https'.
3. Select a log entry to view the details of a detected DNS threat that uses DoH.
4. The threat Application is displayed in the General pane of the detailed log view. Other
relevant details about the threat are displayed in their corresponding windows.
STEP 2 | Create a Custom URL Category list that includes all DoH resolvers you want to enable traffic
to/from (you will need the DNS server URL(s)).
STEP 3 | Create a Decryption Policy Rule that references the custom URL category list that you
created in the previous step.
STEP 4 | Update or create a new anti-spyware security profile used to inspect DoH requests.
STEP 5 | Create or update a security policy rule and reference an anti-spyware profile and a custom
URL category list (Objects > Custom Objects > URL Category) containing the approved list
of DoH servers.
STEP 6 | Create a block policy to decrypt HTTPS traffic and block all remaining unsanctioned DoH
traffic that is not explicitly allowed by the custom URL category list (referenced in step 5) by
using the App-ID: dns-over-https and the following URL category: encrypted-dns.
If you already have an existing block policy to block DoH traffic, verify that the rule
is placed below the previous security policy rule used to match with specific DoH
resolvers listed in a custom URL category list object.
STEP 7 | (Optional) Search for activity on the firewall for HTTPS-encrypted DNS queries that have
been processed using DNS Security.
1. Select Monitor > Logs > Traffic and filter based on the application using dns-over-https,
for example, ( app eq dns-over-https ).
2. Select a log entry to view the details of a detected DNS threat.
3. The Application should display dns-over-https in the General pane of the detailed log
view, indicating that this is DoH traffic that has been processed using DNS Security.
Other relevant details about the threat are displayed in their corresponding windows.
• Prisma Access (Managed by Strata Cloud Advanced DNS Security License (for
Manager) enhanced feature support) or DNS
• Prisma Access (Managed by Panorama) Security License
DNS Security creates threat signatures for domains that have been analyzed by the DNS Security
service. For these known domains, the signatures are referenced when a DNS query is received.
In some cases, it might be possible that the signature has incorrectly categorized a domain as a
threat, due to certain features or qualities present in the domain. In such circumstances, you can
add signature exceptions to bypass these false-positives. If there are known safe domains that are
categorized as malicious, such as internal domains, you can add a list of domains that will bypass
any DNS analysis. If your organization uses third party threat feeds as part of a comprehensive
threat intelligence solution, you can also reference those in the form of external dynamic lists
(EDLs) in your DNS Security profile.
• Strata Cloud Manager
• PAN-OS & Panorama
STEP 3 | Reference an external dynamic list (EDL) as part of your DNS Security profile to import third
party threat feeds.
1. Create an domain-based external dynamic list (Manage > Configuration > NGFW and
Prisma Access > Objects > External Dynamic Lists). For more information about EDLs,
see External Dynamic List.
2. Select Manage > Configuration > NGFW and Prisma Access > Security Services > DNS
Security.
3. In the External Dynamic Lists panel, select a domain list EDL and provide the Policy
Action and Packet Capture settings. In Apply to Profiles, select the DNS Security profile
for which you want the EDL domain list to apply to.
4. Save your changes when you have finished making your updates.
Create Domain Exceptions and Allow | Block Lists (PAN-OS 10.0 and later)
Add an allow list to specify a list of DNS domains / FQDNs to be explicitly allowed.
1. Select Objects > Security Profiles > Anti-Spyware.
2. Select a profile to modify.
3. Add or modify the Anti-Spyware profile from which you want to exclude the threat
signature, and select DNS Exceptions.
4. To Add a new FQDN allow list entry, provide the DNS domain or FQDN location and a
description.
Test Domains
Where Can I Use This? What Do I Need?
• Prisma Access (Managed by Strata Cloud Advanced DNS Security License (for
Manager) enhanced feature support) or DNS
• Prisma Access (Managed by Panorama) Security License
Palo Alto Networks provides the following DNS Security test domains to validate your policy
configuration based on the DNS category.
STEP 1 | Access the following test domains to verify that the policy action for a given threat type is
being enforced:
DNS Security
• C2—test-c2.testpanw.com
• DNS Tunneling—test-dnstun.testpanw.com
• DGA—test-dga.testpanw.com
• Dynamic DNS*—test-ddns.testpanw.com
• Malware—test-malware.testpanw.com
• Newly Registered Domains*—test-nrd.testpanw.com
• Phishing*—test-phishing.testpanw.com
• Grayware*—test-grayware.testpanw.com
• Parked*—test-parked.testpanw.com
• Proxy Avoidance and Anonymizers*—test-proxy.testpanw.com
• Fast Flux*—test-fastflux.testpanw.com
• Malicious NRD*—test-malicious-nrd.testpanw.com
• NXNS Attack*—test-nxns.testpanw.com
• Dangling*—test-dangling-domain.testpanw.com
• DNS Rebinding*—test-dns-rebinding.testpanw.com
• DNS Infiltration*—test-dns-infiltration.testpanw.com
• Wildcard Abuse*—test-wildcard-abuse.testpanw.com
• Strategically-Aged*—test-strategically-aged.testpanw.com
• Compromised DNS*—test-compromised-dns.testpanw.com
• Ad Tracking*—test-adtracking.testpanw.com
• CNAME Cloaking*—test-cname-cloaking.testpanw.com
• Ransomware*—test-ransomware.testpanw.com
• Stockpile*—test-stockpile-domain.testpanw.com
• Cybersquatting*—test-squatting.testpanw.com
• Subdomain Reputation*—test-subdomain-reputation.testpanw.com
The test domains marked with an * are not supported in PAN-OS 9.1.
The following test domain test cases should be added to your DNS server zone file of
testpanw.com before accessing the domain. These test cases match against the Advanced DNS
Security signatures and will generate the appropriate logs. Verify that the policy action for a
given threat type is being enforced.
• 1: DNS Misconfiguration Domain (Zone Dangling) Test Cases
Table
*.test-dnsmisconfig-zone- A 1.2.3.4
dangling.testpanw.com
test-ipv4.hijacking.testpanw.com A 1.2.3.5
*.test-ipv4- A 1.2.3.6
wildcard.hijacking.testpanw.com
test-ns-rrname.hijacking.testpanw.com NS test-ns.hijacking.testpanw.com
test-ns-rrname-rdata- NS 1.test-ns-wc.hijacking.testpanw.com
wc.hijacking.testpanw.com
1.test-ns-rrname-sub- NS test-ns.hijacking.testpanw.com
wc.hijacking.testpanw.com
test-rrname-wc.hijacking.testpanw.com NS test-ns-2.hijacking.testpanw.com
For NS records, you must use the following option:"dig +trace NS"
STEP 2 | Verify that the DNS query request has been processed by DNS Security by monitoring the
activity.
• NGFW (Managed by Strata Cloud Manager) Advanced DNS Security License (for
• NGFW (Managed by PAN-OS or Panorama) enhanced feature support) or DNS
Security License
• VM-Series
Advanced Threat Prevention or Threat
• CN-Series Prevention License
DNS Security
Verify your firewall connectivity to the DNS Security service. If you cannot reach the service,
verify that the following domain is not being blocked: dns.service.paloaltonetworks.com.
STEP 1 | Access the firewall CLI.
STEP 2 | Use the following CLI command to verify your firewall’s connection availability to the DNS
Security service.
For example:
Cache Size: 0
If your firewall has an active connection to the DNS Security service, the server details display
in the response output.
STEP 3 | Retrieve a specified domain’s transaction details, such as latency, TTL, and the signature
category.
Use the following CLI command on the firewall to review the details about a domain:
For example:
Completed in 178 ms
Entries: 2
For example:
...
Security Client ADNS(1)
Current cloud server: qa.adv-
dns.service.paloaltonetworks.com:443
Cloud connection: connected
Config:
Number of gRPC connections: 2, Number of workers: 8
Verify that the cloud connection status for Security Client AdnsTelemetry(2) and
Security Client ADNS(1) are showing active connections.
If you are unable to connect to the Advanced DNS Security cloud service, verify that the
Advanced DNS server is not being blocked: dns.service.paloaltonetworks.com.
• NGFW (Managed by Strata Cloud Manager) Advanced DNS Security License (for
• NGFW (Managed by PAN-OS or Panorama) enhanced feature support) or DNS
Security License
• VM-Series
Advanced Threat Prevention or Threat
• CN-Series Prevention License
DNS Security
If the firewall is unable to retrieve a signature verdict in the allotted time due to connectivity
issues, the request, including all subsequent DNS responses, are passed through. You can check
the average latency to verify that requests fall within the configured period. If the average latency
exceeds the configured period, consider updating the setting to a value that is higher than the
average latency to prevent requests from timing out.
STEP 1 | In the CLI, issue the following command to view the average latency.
STEP 2 | Scroll down through the output to the latency section under the Signature query API heading
and verify that the average latency falls within the defined timeout period. This latency
indicates the amount of time it takes, on average, to retrieve a signature verdict from the
DNS security service. Additional latency statistics for various latency periods can be found
below the averages.
STEP 3 | If the average latency is consistency above the default timeout value, you can raise the
setting so that the requests fall within a given period. Select Device > Content-ID and
update the Realtime Signature Lookup setting.
PAN_CTDF_DETECT_SERVICE_ADNS
cli_timeout: 1
req_total: 2
req_timed_out: 0
Hold:
adns rtt>=0ms: 0
adns rtt>=50ms: 2
adns rtt>=100ms: 0
adns rtt>=150ms: 0
adns rtt>=200ms: 0
adns rtt>=250ms: 0
adns rtt>=300ms: 0
adns rtt>=350ms: 0
adns rtt>=400ms: 0
adns rtt>=450ms: 0
STEP 2 | Configure the maximum Advanced DNS signature lookup timeout setting. When this value
is exceeded, the DNS response passes through without performing analysis using Advanced
DNS Security. DNS signatures (and their associated policies) that are delivered through
regular content updates or are part of configured EDLs (external dynamic lists) or DNS
exceptions are still applied.
1. Select Device > Setup > Content-ID > Advanced DNS Security.
2. Specify an updated maximum Advanced DNS signature lookup timeout setting in
milliseconds. The default is 100ms and is the recommended setting.
3. Click OK to confirm your changes.
Alternatively, you can use the following CLI command to configure the Advanced DNS
Security timeout value. You can set a value of 100-15,000ms in 100ms increments. The
default value is 100ms and is the recommended setting.
For example:
You can check the current timeout configuration using the following CLI command (refer to
the max-latency entry of the output).
• Prisma Access (Managed by Strata Cloud Advanced DNS Security License (for
Manager) enhanced feature support) or DNS
• Prisma Access (Managed by Panorama) Security License
DNS Security queries can be bypassed in cases where latency issues or other network issues are
present.
In cases where false-positives occur, Palo Alto Networks recommends creating specific
exceptions instead of bypassing DNS Security queries.
• Cloud Management
• PAN-OS & Panorama
STEP 2 | Go to Manage > Configuration > NGFW and Prisma Access > Security Services > DNS
Security and select the relevant DNS Security profile.
STEP 3 | Configure the DNS Security signature policy settings to bypass DNS Security queries. For
each DNS category, set the Action to allow and Packet Capture to disabled. In the following,
the DNS Security categories have been configured to bypass DNS Security queries.
STEP 4 | In the Overrides section, verify that there are no entries present; if necessary, delete all
Domain/FQDN overrides.
STEP 2 | Configure the DNS Security signature policy settings to bypass DNS Security queries.
1. Select Objects > Security Profiles > Anti-Spyware.
2. Select the profile containing your active DNS Security policy settings.
3. Select the DNS Policies tab.
4. For each DNS category, set the log severity to none, the policy action to allow, and
packet capture to disable. In the following, the DNS Security categories have been
configured to bypass DNS Security queries.
STEP 3 | Select DNS Exceptions and remove all DNS Domain/FQDN Allow List entries.
STEP 2 | Configure DNS Security signature policy settings to bypass DNS Security look-ups.
1. Select Objects > Security Profiles > Anti-Spyware.
2. Select the profile containing your active DNS Security policy settings.
3. Select the DNS Signatures tab.
4. Under Policies & Settings, set the policy action for Palo Alto Networks DNS Security to
an action of allow.
• Prisma Access (Managed by Strata Cloud Advanced DNS Security License (for
Manager) enhanced feature support) or DNS
• Prisma Access (Managed by Panorama) Security License
Palo Alto Networks provides several options to monitor DNS Security and Advanced DNS
Security activity to accommodate intelligence retrieval for a range of products that rely on DNS
Security subscription services and the associated traffic data. Depending on the product platform,
you can access high-level dashboards that provide DNS request statistics and usage trends,
including context into network activity, to specific DNS request details from specific users in the
form of logging data.
You can also view how the DNS Security subscription services integrate with other Palo Alto
Networks applications and security services to protect your organization from threats, as well
as get a high-level view of the overall operational health of your deployment, through the Strata
Cloud Manager Command Center. The command center functions as your NetSec homepage and
provides a comprehensive summary of the health, security, and efficiency of your network, in an
interactive visual dashboard with multiple data facets for easy, at-a-glace assessment.
For more specific details about DNS Security subscription service operations, the dashboard
provides a view into your networks DNS query data as well as the ability to drill down into various
DNS trends. Each dashboard card provides a unique view into how DNS requests and responses
are processed and categorized in a graphical report format. This allows you to see, at a glance, a
high-level view of your organization’s DNS usage statistics. It also provides a list of misconfigured
domains and hijacked domains detected by the Advanced DNS Security service, enabling you to
correct and rectify any DNS configuration errors. The misconfigured domains are based on the
public-facing parent domain entries added to DNS Zone Misconfigurations list.
You can also view the logs that are automatically generated when DNS requests are processed.
These event files are time-stamped and provide an audit trail when configured to do, based on
the DNS category log configuration. DNS log entries can contain various details about the DNS
request, including the nature of the DNS threat posed by the associated domain, as well as action
taken when the threat was detected.
Palo Alto Networks provides several methods to monitor the DNS Security activity based on your
platform.
• The Strata Cloud Manager Command Center
67
Monitor DNS Security Subscription Services
• Prisma Access (Managed by Strata Cloud Advanced DNS Security License (for
Manager) enhanced feature support) or DNS
• Prisma Access (Managed by Panorama) Security License
The DNS Security dashboard shows the statistics data generated by the Advanced DNS Security
and DNS Security subscription services in a fast, visual assessment report of your organization’s
DNS usage. View and drill down into various DNS trends discovered in your network. Each
dashboard card provides a unique view into how DNS requests are processed and categorized.
Select dashboard cards to change the context of the dashboard or view more information about a
specific trend, domain, or statistic.
The DNS Security dashboard is available on Prisma Access and AIOps for NGFW. You can interact
with the DNS Security Dashboard Cards to alter the context of the dashboard or view more
information about a specific trend, domain, or statistic. You can also customize the formatting to
display current trends or historical data, across relevant data points.
• Strata Cloud Manager
• AIOps for NGFW Free
• Prisma Access (Managed by Strata Cloud Advanced DNS Security License (for
Manager) enhanced feature support) or DNS
• Prisma Access (Managed by Panorama) Security License
The cards populating the DNS Security dashboard are interactive and allows you to view
additional details or pivot to a list of specific requests, events, and domains, as it pertains to how
the content is shown.
The following list provides an overview of the DNS Security dashboard cards:
DNS Requests Displays the total number of DNS requests that have been
processed by DNS Security.
Malicious DNS Requests Displays a stacked bar graph showing DNS requests that have
been categorized based on the currently available types that are
considered malicious. The total number is shown in the upper-
left while a breakdown of categorical variables are indicated
below.
High-Risk DNS Category Displays a trend chart showing a breakdown of the DNS
Trend requests based on the DNS category or the action applied to the
DNS request over the observable time range.
DNS Category Distribution Displays a flow diagram that provides a visualization of the
Across Actions distributions of actions taken for high-risk DNS categories. A
Top 10 Domains Provides a list of the top 10 most commonly requested domains
from your network along with the DNS category and the action
taken. You can view more details and the relevant logs for
a domain by clicking the appropriate icon. Select View All
DNS Requests for a complete list of domains that have been
accessed.
DNS Resolvers Provides two lists showing the most resolved malicious domains
and the least resolved domains in your network.
STEP 2 | Select Dashboards > More Dashboards > DNS Security to open the DNS Security
dashboard.
STEP 3 | From the dashboard, configure your filter options using the available drop downs.
1. Filter by time range—Select from Last hour, Last 24 hours, Last 7 days, or Last 30 days
to display data for a specific time-frame.
2. Filter by DNS category—Select from Select All, MalwareCommand and Control,
Phishing, Grayware, Exceptions List, Newly Registered, Dynamic DNS, Proxy, Parked,
Benign, Ad Track to filter the data set based on a DNS type.
STEP 4 | Optionally, you can also Download, Share, and Schedule Activity Reports.
STEP 5 | You can re-contextualize, interact, and pivot from the data provided by the dashboard cards.
For an overview of each of the DNS Security dashboard cards, see DNS Security Dashboard
cards.
STEP 2 | Select Dashboards > More Dashboards > DNS Security to open the DNS Security
dashboard.
STEP 3 | From the dashboard, configure your filter options using the available drop downs.
1. Filter by time range—Select from Last hour, Last 24 hours, Last 7 days, or Last 30 days
to display data for a specific time-frame.
2. Filter by DNS category—Select from C2 (DGA, Tunneling, other C2), Malware, Newly
Registered Domain, Phishing, Dynamic DNS, Allow List, Benign, Grayware, Parked,
Proxy, and Any Category, to filter the data set based on a DNS type.
The Allow List category is a list maintained by Palo Alto Networks of explicitly
allowable domains based on metrics from PAN-DB and Alexa. These allow list
domains are frequently accessed and known to be free from malicious content.
3. Filter by DNS action—Select from Allow, Block, and Sinkhole to filter based on the
action taken on a DNS query based on your DNS Security profile action settings.
STEP 4 | Optionally, you can also Download, Share, and Schedule Activity Reports.
STEP 5 | You can re-contextualize, interact, and pivot from the data provided by the dashboard cards.
For an overview of each of the DNS Security dashboard cards, see DNS Security Dashboard
cards.
• Prisma Access (Managed by Strata Cloud Advanced DNS Security License (for
Manager) enhanced feature support) or DNS
• Prisma Access (Managed by Panorama) Security License
You can browse, search, and view DNS Security logs that are automatically generated when DNS
Security encounters a qualifying event. Typically, this includes any domain category that DNS
Security analyzes unless it is specifically configured with a log severity level of none. Log entries
provide numerous details about the event, including the threat level and, if applicable, the nature
of threat.
DNS Security logs are accessible directly on the firewall or through Strata Logging Service-based
log viewers (AIOps for NGFW Free, Cloud Management, Strata Logging Service, etc). While the
firewall allows you to access malicious threat log entries that are generated when users make
DNS queries, benign DNS requests are not recorded. DNS Security data is also forwarded to
Strata Logging Service through log forwarding (as threat logs) and DNS Security telemetry (as
DNS Security logs), which are then referenced by various activity log viewer applications. DNS
Security telemetry operates with minimal overhead, which limits the amount of data sent to
Strata Logging Service; as a result, only a subset of DNS queries are forwarded to Strata Logging
Service as DNS Security log entries, regardless of the severity level, threat type, or category. The
threat logs for malicious DNS requests that are forwarded to Strata Logging Service using log
forwarding are available in their entirety. As a result, Palo Alto Networks recommends viewing
logs for malicious DNS requests as threat logs instead of DNS Security logs.
• Strata Cloud Manager
• PAN-OS & Panorama
• AIOps for NGFW Free
• Strata Logging Service
STEP 1 | Use the credentials associated with your Palo Alto Networks support account and log in to
the Strata Cloud Manager on the hub.
STEP 2 | Search for DNS queries that have been processed using DNS Security.
1. Select Incidents and Alerts > Log Viewer.
2. Constrain your search using the threat filter and submit a log query based on the DNS
category, for example, threat_category.value = 'dns-c2' to view logs that
have been determined to be a C2 domain. To search for other DNS types, replace c2
with another supported DNS category (ddns, parked, malware, etc). Adjust the search
criteria as necessary for your search, including additional query parameters (such as the
severity level and subtype) along with a date range.
one leveraging DNS tunneling techniques, can be found here: Leveraging DNS Tunneling
for Tracking and Scanning.
The DNS tunnel attribution might produce the associated tool and campaign
entries some time after the initial DNS tunnel detection has completed. In this
instance, only the domain name is initially specified alongside the DNS tunnel
category. When the DNS tunnel attribution component finishes, the complete
details will display as expected in the Threat ID/Name field, including any DNS
tunneling tools and campaigns.
STEP 2 | Search for activity on the firewall for queries that have been processed using DNS Security.
1. Select Monitor > Logs > Threat and filter based on the DNS category.
Consider the following examples:
• ( category-of-threatid eq dns-c2 ) to view logs that have been
determined to be a C2 domain by DNS Security.
• ( category-of-threatid eq adns-hijacking ), whereby the variable
adns-hijacking indicates DNS queries that have been categorized as a malicious
DNS hijacking attempt by Advanced DNS Security.
To search for other DNS types, replace c2 with another supported DNS category (ddns,
parked, malware, etc).
one leveraging DNS tunneling techniques, can be found here: Leveraging DNS Tunneling
for Tracking and Scanning.
The DNS tunnel attribution might produce the associated tool and campaign
entries some time after the initial DNS tunnel detection has completed. In this
instance, only the domain name is initially specified alongside the DNS tunnel
category. When the DNS tunnel attribution component finishes, the complete
details will display as expected in the Threat ID/Name field, including any DNS
tunneling tools and campaigns.
STEP 1 | Use the credentials associated with your Palo Alto Networks support account and log in to
the AIOps for NGFW Free application on the hub.
STEP 2 | Search for DNS queries that have been processed using DNS Security in AIOps for NGFW
Free.
1. Select Incidents and Alerts > Log Viewer.
2. Constrain your search using the threat filter and submit a log query based on the DNS
category, for example, threat_category.value = 'dns-c2' to view logs that
have been determined to be a C2 domain. To search for other DNS types, replace c2
with another supported DNS category (ddns, parked, malware, etc). Adjust the search
criteria as necessary for your search, including additional query parameters (such as the
severity level and subtype) along with a date range.
3. Select a log entry to view the details of a detected DNS threat.
4. The threat Category is displayed in the Details pane of the detailed log view. Other
relevant details about the threat are displayed in their corresponding windows.
STEP 2 | Allocate Storage Based on Log Type. If storage space has not been allocated for DNS
Security logs on Strata Logging Service, logging entries will not be viewable through Strata
Logging Service.
STEP 3 | Search for DNS queries that have been processed using DNS Security in Strata Logging
Service.
1. Select Explore to open the Strata Logging Service log viewer.
2. Constrain your search using the threat filter and submit a log query based on the DNS
category, for example, threat_category.value = 'dns-c2' to view logs that
have been determined to be a C2 domain. To search for other DNS types, replace c2
with another supported DNS category (ddns, parked, malware, etc). Adjust the search
criteria as necessary for your search, including additional query parameters (such as the
severity level and subtype) along with a date range.
3. Select a log entry to view the details of a detected DNS threat.
4. The threat Category is displayed in the Details pane of the detailed log view. Other
relevant details about the threat are displayed in their corresponding windows.