Enable Evasion Signatures
Focus
Advanced Threat Prevention Powered by Precision AI®

Enable Evasion Signatures

Table of Contents

Enable Evasion Signatures

Evasion signatures detect sophisticated HTTP and TLS threats by identifying domain mismatches.
Where Can I Use This?What Do I Need?
  • Prisma Access (Managed by Panorama or Strata Cloud Manager)
  • NGFW (Managed by Panorama or Strata Cloud Manager)
  • VM-Series
  • CN-Series
  • Advanced Threat Prevention (for enhanced feature support) or Threat Prevention License
Palo Alto Networks evasion signatures provide a critical layer of defense against sophisticated threats that attempt to bypass security filters by crafting inconsistent HTTP or TLS requests. These signatures are specifically designed to identify and alert on instances where a client initiates a connection to a domain that differs from the one specified in the initial DNS query. This capability is vital for detecting advanced evasion tactics, such as domain fronting or unauthorized tunneling, where an attacker attempts to hide malicious traffic inside seemingly legitimate protocol handshakes.
The NGFW must maintain visibility into the client's name resolution process. Consequently, evasion signatures are only functional when the firewall is configured to act as a DNS proxy, allowing it to resolve domain name queries and cache the intent of the client. By correlating the intercepted DNS request with the subsequent application-layer traffic, the firewall can accurately identify destination mismatches that would otherwise bypass standard pattern-matching signatures.
As a best practice, administrators should ensure the DNS proxy feature is enabled on the relevant interfaces before deploying evasion-specific signatures within their Anti-Spyware or Vulnerability Protection profiles. Once the DNS proxy is active, the firewall can cross-reference the cached DNS data with HTTP Host headers or TLS Server Name Indication (SNI) fields. This integrated approach ensures that any attempt to circumvent security policies through destination manipulation is logged and mitigated in real-time.
  1. Enable a firewall intermediate to clients and servers to act as a DNS proxy.
    • Specify the interfaces on which you want the firewall to listen for DNS queries.
    • Define the DNS servers with which the firewall communicates to resolve DNS requests.
    • Set up static FQDN-to-IP address entries that the firewall can resolve locally, without reaching out to DNS servers.
    • Enable caching for resolved hostname-to-IP-address mappings.
  2. Get the latest Applications and Threats content version (at least content version 579 or later).
    1. Select DeviceDynamic Updates.
    2. Check Now to get the latest Applications and Threats content update.
    3. Download and Install Applications and Threats content version 579 (or later).
  3. Define how the firewall should enforce traffic matched to evasion signatures.
    1. Select ObjectsSecurity ProfilesAnti-Spyware and Add or modify an Anti-spyware profile.
    2. Select Exceptions and select Show all signatures.
    3. Filter signatures based on the keyword evasion.
    4. For all evasion signatures, set the Action to any setting other than allow or the default action (the default action is for evasion signatures is allow). For example, set the Action for signature IDs 14978 and 14984 to alert or drop.
    5. Click OK to save the updated Anti-spyware profile.
    6. Attach the Anti-spyware profile to a security policy rule: Select PoliciesSecurity, select the desired policy to modify and then click the Actions tab. In Profile Settings, click the drop-down next to Anti-Spyware and select the anti-spyware profile you just modified to enforce evasion signatures.
  4. Commit your changes.
    Click Commit.