DNS Security Analytics
Table of Contents
Expand All
|
Collapse All
Next-Generation Firewall Docs
-
PAN-OS 10.0 (EoL)
- PAN-OS 11.1 & Later
- PAN-OS 11.0 (EoL)
- PAN-OS 10.2
- PAN-OS 10.1
- PAN-OS 10.0 (EoL)
- PAN-OS 9.1 (EoL)
- Cloud Management of NGFWs
-
- Management Interfaces
-
- Launch the Web Interface
- Configure Banners, Message of the Day, and Logos
- Use the Administrator Login Activity Indicators to Detect Account Misuse
- Manage and Monitor Administrative Tasks
- Commit, Validate, and Preview Firewall Configuration Changes
- Export Configuration Table Data
- Use Global Find to Search the Firewall or Panorama Management Server
- Manage Locks for Restricting Configuration Changes
-
-
- Define Access to the Web Interface Tabs
- Provide Granular Access to the Monitor Tab
- Provide Granular Access to the Policy Tab
- Provide Granular Access to the Objects Tab
- Provide Granular Access to the Network Tab
- Provide Granular Access to the Device Tab
- Define User Privacy Settings in the Admin Role Profile
- Restrict Administrator Access to Commit and Validate Functions
- Provide Granular Access to Global Settings
- Provide Granular Access to the Panorama Tab
- Provide Granular Access to Operations Settings
- Panorama Web Interface Access Privileges
-
- Reset the Firewall to Factory Default Settings
-
- Plan Your Authentication Deployment
- Configure SAML Authentication
- Configure Kerberos Single Sign-On
- Configure Kerberos Server Authentication
- Configure TACACS+ Authentication
- Configure RADIUS Authentication
- Configure LDAP Authentication
- Configure Local Database Authentication
- Configure an Authentication Profile and Sequence
- Test Authentication Server Connectivity
- Troubleshoot Authentication Issues
-
- Keys and Certificates
- Default Trusted Certificate Authorities (CAs)
- Certificate Deployment
- Configure the Master Key
- Export a Certificate and Private Key
- Configure a Certificate Profile
- Configure an SSL/TLS Service Profile
- Configure an SSH Service Profile
- Replace the Certificate for Inbound Management Traffic
- Configure the Key Size for SSL Forward Proxy Server Certificates
-
- HA Overview
-
- Prerequisites for Active/Active HA
- Configure Active/Active HA
-
- Use Case: Configure Active/Active HA with Route-Based Redundancy
- Use Case: Configure Active/Active HA with Floating IP Addresses
- Use Case: Configure Active/Active HA with ARP Load-Sharing
- Use Case: Configure Active/Active HA with Floating IP Address Bound to Active-Primary Firewall
- Use Case: Configure Active/Active HA with Source DIPP NAT Using Floating IP Addresses
- Use Case: Configure Separate Source NAT IP Address Pools for Active/Active HA Firewalls
- Use Case: Configure Active/Active HA for ARP Load-Sharing with Destination NAT
- Use Case: Configure Active/Active HA for ARP Load-Sharing with Destination NAT in Layer 3
- HA Clustering Overview
- HA Clustering Best Practices and Provisioning
- Configure HA Clustering
- Refresh HA1 SSH Keys and Configure Key Options
- HA Firewall States
-
- Use the Dashboard
- Monitor Applications and Threats
- Monitor Block List
-
- Report Types
- View Reports
- Configure the Expiration Period and Run Time for Reports
- Disable Predefined Reports
- Custom Reports
- Generate Custom Reports
- Generate the SaaS Application Usage Report
- Manage PDF Summary Reports
- Generate User/Group Activity Reports
- Manage Report Groups
- Schedule Reports for Email Delivery
- Manage Report Storage Capacity
- View Policy Rule Usage
- Use External Services for Monitoring
- Configure Log Forwarding
- Configure Email Alerts
-
- Configure Syslog Monitoring
-
- Traffic Log Fields
- Threat Log Fields
- URL Filtering Log Fields
- Data Filtering Log Fields
- HIP Match Log Fields
- GlobalProtect Log Fields
- IP-Tag Log Fields
- User-ID Log Fields
- Decryption Log Fields
- Tunnel Inspection Log Fields
- SCTP Log Fields
- Authentication Log Fields
- Config Log Fields
- System Log Fields
- Correlated Events Log Fields
- GTP Log Fields
- Syslog Severity
- Custom Log/Event Format
- Escape Sequences
- Forward Logs to an HTTP/S Destination
- Firewall Interface Identifiers in SNMP Managers and NetFlow Collectors
- Monitor Transceivers
-
- User-ID Overview
- Enable User-ID
- Map Users to Groups
- Enable User- and Group-Based Policy
- Enable Policy for Users with Multiple Accounts
- Verify the User-ID Configuration
-
- App-ID Overview
- App-ID and HTTP/2 Inspection
- Manage Custom or Unknown Applications
- Safely Enable Applications on Default Ports
- Applications with Implicit Support
- Application Level Gateways
- Disable the SIP Application-level Gateway (ALG)
- Maintain Custom Timeouts for Data Center Applications
-
- Best Practices for Securing Your Network from Layer 4 and Layer 7 Evasions
- Set Up Antivirus, Anti-Spyware, and Vulnerability Protection
- Set Up File Blocking
- Prevent Brute Force Attacks
- Customize the Action and Trigger Conditions for a Brute Force Signature
- Enable Evasion Signatures
- Monitor Blocked IP Addresses
- Threat Signature Categories
- Create Threat Exceptions
- Custom Signatures
- Share Threat Intelligence with Palo Alto Networks
- Threat Prevention Resources
-
- Decryption Overview
-
- Keys and Certificates for Decryption Policies
- SSL Forward Proxy
- SSL Forward Proxy Decryption Profile
- SSL Inbound Inspection
- SSL Inbound Inspection Decryption Profile
- SSL Protocol Settings Decryption Profile
- SSH Proxy
- SSH Proxy Decryption Profile
- Profile for No Decryption
- SSL Decryption for Elliptical Curve Cryptography (ECC) Certificates
- Perfect Forward Secrecy (PFS) Support for SSL Decryption
- SSL Decryption and Subject Alternative Names (SANs)
- TLSv1.3 Decryption
- High Availability Support for Decrypted Sessions
- Decryption Mirroring
- Configure SSL Forward Proxy
- Configure SSL Inbound Inspection
- Configure SSH Proxy
- Configure Server Certificate Verification for Undecrypted Traffic
- Enable Users to Opt Out of SSL Decryption
- Temporarily Disable SSL Decryption
- Configure Decryption Port Mirroring
- Verify Decryption
-
- How Decryption Broker Works
- Layer 3 Security Chain Guidelines
- Configure Decryption Broker with One or More Layer 3 Security Chain
- Transparent Bridge Security Chain Guidelines
- Configure Decryption Broker with a Single Transparent Bridge Security Chain
- Configure Decryption Broker with Multiple Transparent Bridge Security Chains
- Activate Free Licenses for Decryption Features
-
- About Palo Alto Networks URL Filtering Solution
- How Advanced URL Filtering Works
- URL Filtering Inline ML
- URL Filtering Use Cases
- Plan Your URL Filtering Deployment
- URL Filtering Best Practices
- Activate The Advanced URL Filtering Subscription
- Test URL Filtering Configuration
- Configure URL Filtering
- Configure URL Filtering Inline ML
- Log Only the Page a User Visits
- Create a Custom URL Category
- URL Category Exceptions
- Use an External Dynamic List in a URL Filtering Profile
- Allow Password Access to Certain Sites
- URL Filtering Response Pages
- Customize the URL Filtering Response Pages
- HTTP Header Logging
- Request to Change the Category for a URL
-
-
- Tap Interfaces
-
- Layer 2 and Layer 3 Packets over a Virtual Wire
- Port Speeds of Virtual Wire Interfaces
- LLDP over a Virtual Wire
- Aggregated Interfaces for a Virtual Wire
- Virtual Wire Support of High Availability
- Zone Protection for a Virtual Wire Interface
- VLAN-Tagged Traffic
- Virtual Wire Subinterfaces
- Configure Virtual Wires
- Configure an Aggregate Interface Group
- Configure Bonjour Reflector for Network Segmentation
- Use Interface Management Profiles to Restrict Access
- Virtual Routers
- Service Routes
- RIP
- Route Redistribution
-
- DNS Overview
- DNS Proxy Object
- DNS Server Profile
- Multi-Tenant DNS Deployments
- Configure a DNS Proxy Object
- Configure a DNS Server Profile
- Use Case 1: Firewall Requires DNS Resolution
- Use Case 2: ISP Tenant Uses DNS Proxy to Handle DNS Resolution for Security Policies, Reporting, and Services within its Virtual System
- Use Case 3: Firewall Acts as DNS Proxy Between Client and Server
- DNS Proxy Rule and FQDN Matching
- Dynamic DNS Overview
- Configure Dynamic DNS for Firewall Interfaces
-
- NAT Rule Capacities
- Dynamic IP and Port NAT Oversubscription
- Dataplane NAT Memory Statistics
-
- Translate Internal Client IP Addresses to Your Public IP Address (Source DIPP NAT)
- Enable Clients on the Internal Network to Access your Public Servers (Destination U-Turn NAT)
- Enable Bi-Directional Address Translation for Your Public-Facing Servers (Static Source NAT)
- Configure Destination NAT with DNS Rewrite
- Configure Destination NAT Using Dynamic IP Addresses
- Modify the Oversubscription Rate for DIPP NAT
- Reserve Dynamic IP NAT Addresses
- Disable NAT for a Specific Host or Interface
-
-
- Policy Types
- Policy Objects
- Track Rules Within a Rulebase
- Enforce Policy Rule Description, Tag, and Audit Comment
- Move or Clone a Policy Rule or Object to a Different Virtual System
-
- External Dynamic List
- Built-in External Dynamic Lists
- Configure the Firewall to Access an External Dynamic List
- Retrieve an External Dynamic List from the Web Server
- View External Dynamic List Entries
- Exclude Entries from an External Dynamic List
- Enforce Policy on an External Dynamic List
- Find External Dynamic Lists That Failed Authentication
- Disable Authentication for an External Dynamic List
- Register IP Addresses and Tags Dynamically
- Use Dynamic User Groups in Policy
- Use Auto-Tagging to Automate Security Actions
- CLI Commands for Dynamic IP Addresses and Tags
- Test Policy Rules
-
- Network Segmentation Using Zones
- How Do Zones Protect the Network?
-
PAN-OS 11.1 & Later
- PAN-OS 11.1 & Later
- PAN-OS 11.0 (EoL)
- PAN-OS 10.2
- PAN-OS 10.1
-
- Tap Interfaces
-
- Layer 2 and Layer 3 Packets over a Virtual Wire
- Port Speeds of Virtual Wire Interfaces
- LLDP over a Virtual Wire
- Aggregated Interfaces for a Virtual Wire
- Virtual Wire Support of High Availability
- Zone Protection for a Virtual Wire Interface
- VLAN-Tagged Traffic
- Virtual Wire Subinterfaces
- Configure Virtual Wires
- Configure a PPPoE Client on a Subinterface
- Configure an IPv6 PPPoE Client
- Configure an Aggregate Interface Group
- Configure Bonjour Reflector for Network Segmentation
- Use Interface Management Profiles to Restrict Access
-
- DHCP Overview
- Firewall as a DHCP Server and Client
- Firewall as a DHCPv6 Client
- DHCP Messages
- Dynamic IPv6 Addressing on the Management Interface
- Configure an Interface as a DHCP Server
- Configure an Interface as a DHCPv4 Client
- Configure an Interface as a DHCPv6 Client with Prefix Delegation
- Configure the Management Interface as a DHCP Client
- Configure the Management Interface for Dynamic IPv6 Address Assignment
- Configure an Interface as a DHCP Relay Agent
-
- DNS Overview
- DNS Proxy Object
- DNS Server Profile
- Multi-Tenant DNS Deployments
- Configure a DNS Proxy Object
- Configure a DNS Server Profile
- Use Case 1: Firewall Requires DNS Resolution
- Use Case 2: ISP Tenant Uses DNS Proxy to Handle DNS Resolution for Security Policies, Reporting, and Services within its Virtual System
- Use Case 3: Firewall Acts as DNS Proxy Between Client and Server
- DNS Proxy Rule and FQDN Matching
-
- NAT Rule Capacities
- Dynamic IP and Port NAT Oversubscription
- Dataplane NAT Memory Statistics
-
- Translate Internal Client IP Addresses to Your Public IP Address (Source DIPP NAT)
- Create a Source NAT Rule with Persistent DIPP
- PAN-OS
- Strata Cloud Manager
- Enable Clients on the Internal Network to Access your Public Servers (Destination U-Turn NAT)
- Enable Bi-Directional Address Translation for Your Public-Facing Servers (Static Source NAT)
- Configure Destination NAT with DNS Rewrite
- Configure Destination NAT Using Dynamic IP Addresses
- Modify the Oversubscription Rate for DIPP NAT
- Reserve Dynamic IP NAT Addresses
- Disable NAT for a Specific Host or Interface
-
- Network Packet Broker Overview
- How Network Packet Broker Works
- Prepare to Deploy Network Packet Broker
- Configure Transparent Bridge Security Chains
- Configure Routed Layer 3 Security Chains
- Network Packet Broker HA Support
- User Interface Changes for Network Packet Broker
- Limitations of Network Packet Broker
- Troubleshoot Network Packet Broker
-
- Enable Advanced Routing
- Logical Router Overview
- Configure a Logical Router
- Create a Static Route
- Configure BGP on an Advanced Routing Engine
- Create BGP Routing Profiles
- Create Filters for the Advanced Routing Engine
- Configure OSPFv2 on an Advanced Routing Engine
- Create OSPF Routing Profiles
- Configure OSPFv3 on an Advanced Routing Engine
- Create OSPFv3 Routing Profiles
- Configure RIPv2 on an Advanced Routing Engine
- Create RIPv2 Routing Profiles
- Create BFD Profiles
- Configure IPv4 Multicast
- Configure MSDP
- Create Multicast Routing Profiles
- Create an IPv4 MRoute
-
-
PAN-OS 11.2
- PAN-OS 11.2
- PAN-OS 11.1
- PAN-OS 11.0 (EoL)
- PAN-OS 10.2
- PAN-OS 10.1
- PAN-OS 10.0 (EoL)
- PAN-OS 9.1 (EoL)
- PAN-OS 9.0 (EoL)
- PAN-OS 8.1 (EoL)
- Cloud Management and AIOps for NGFW
End-of-Life (EoL)
DNS Security Analytics
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.
You can view your organization’s DNS statistics data generated
by the DNS Security Cloud service using AutoFocus. This provides
a fast, visual assessment describing the breakdown of DNS requests
passing through your network based on the available DNS categories.
Alternatively, you can retrieve domain information, as well as the
transaction details, such as latency and TTL using the test dns-proxy dns-signature fqdn <domain> command.
Upon upgrade to PAN-OS 10.0 and later, the DNS Security
source gets redefined into new categories to provide extended granular
controls; as a result, the new categories will overwrite the previously
defined action and acquire default settings. Make sure to reapply
any sinkhole, log severity, and packet captures settings appropriate
for the newly defined DNS Security Categories.
The DNS Security service currently supports detection of the
following DNS threat categories:
The universal threat ID number (indicated as ID in the
Threat logs) maps to the 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.
- 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.
- 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.
- Newly Registered Domains (UTID: 109020001)—Newly registered domains are domains that have been recently added by a TLD operator or had change in ownership within the last 32 days. While new domains can be created for legitimate purposes, the vast majority are often used to facilitate malicious activities, such as operating as C2 servers or used to distribute malware, spam, PUP/adware. Palo Alto Networks detects newly registered domains by monitoring specific feeds (domain registries and registrars) and using zone files, passive DNS, WHOIS data to detect registration campaigns.
- Phishing Domains (UTID: 109010001) —Phishing domains attempt to lure users into submitting sensitive data, such as personal information or user credentials, by masquerading as legitimate websites through phishing or pharming. These malicious activities can be conducted through social engineering campaigns (whereby a seemingly trusted source manipulates users into submitting personal information via email or other forms of electronic communications) or through web traffic redirection, which directs users to fraudulent sites that appear legitimate.
- Grayware Domains (UTID: 109010002) —(Available with installation of PAN-OS content release 8290 and later). Grayware domains generally do not pose a direct security threat, however, they can facilitate vectors of attack, produce various undesirable behaviors, or might simply contain questionable/offensive content.These can include websites and domains that:
- Attempt to trick users into granting remote access.
- Contain adware and other unsolicited applications (such as cryptominers, hijackers, and PUPs [potentially unwanted programs]).
- Deploy domain identification concealment actions using fast flux techniques (fastflux detection - UTID: 109010005).
- Demonstrate malicious behavior and usage as evidenced through DNS security predicative analytics (malicious NRD - UTID: 109010006).
- Take advantage of user errors when entering web page addresses (typosquatting domains).
- Redirect traffic from a legitimate source to a malicious website due to an improperly configured or stale DNS record on an authoritative DNS server that has not been removed or otherwise corrected (dangling DNS - UTID: 109010008).
- Promote illegal activities or scams.
- Include wildcard DNS entries, which can be used to evade block lists or enable wildcard DNS attacks by routing traffic to malicious websites (Wildcard abuse - UTID: 109002001).
- Indicate the presence of DNS traffic with anomalous characteristics when compared to established baseline profiles built from collected DNS data (Anomaly detection).
- Have been registered months or years in advance and left in a state of dormancy to bypass reputation checks when they become active. This also includes newly observed domains that have never been seen or otherwise evaluated (Strategically-aged domains - UTID: 109002002).
- Parked Domains (UTID: 109010003)—(Available with installation of PAN-OS content release 8318 and later) Parked domains are typically inactive websites that host limited content, often in the form of click-through ads which may generate revenue for the host entity, but generally do not contain content that is useful to the end user. While they often function as a legitimate placeholder or as nothing more than a benign nuisance, they could also be used as a possible vector for distribution of malware.
- Proxy Avoidance and Anonymizers (UTID: 109010004)—(Available with installation of PAN-OS content release 8340 and later) Proxy Avoidance and Anonymizers is traffic to services that are used to bypass content filtering policies. Users who attempt to circumvent an organization’s content filtering policies via anonymizer proxy services are blocked at the DNS level.
- Ad Tracking Domains (UTID: 109004000)—(Available with installation of PAN-OS content release 8586 and later) Ad Tracking domains deliver certain types of marketing automation content for webpages in order to track user engagement (such as link clicks, web page navigation, etc). Typically, these third-party domains are concealed through the use of a vanity URL to appear to be part of the originating domain.
- CNAME Cloaking (UTID: 109004001)—CNAME cloaking provides an alternate means of concealing a URL by modifying a web request for a subdomain to appear as if it originates from the same website, though in actuality, the subdomain uses a CNAME to resolve to a third-party domain. This technique circumvents some browser-based privacy protections which could potentially connect to a suspicious CNAME destination.