Next-Generation Firewall
Device > Certificate Management > SSL Decryption Exclusion
Table of Contents
Device > Certificate Management > SSL Decryption Exclusion
View and manage SSL/TLS decryption exclusions
![]()
. There are two types of decryption exclusions,
predefined exclusions and custom exclusions:
- Predefined decryption exclusions allow applications and services that might break when the firewall decrypts them to remain encrypted. Palo Alto Networks defines and regularly updates the list of predefined decryption exclusions as part of Applications and Threats content updates. Predefined exclusions are enabled by default, but you can disable them as needed.
- You can create custom decryption exclusions to exclude server traffic from decryption. All traffic originating from or destined to the targeted server remains encrypted.You can also exclude traffic from decryptionbased on application, source, destination, URL category, or service.
![]()
Use the settings on this page to modify or add a decryption
exclusion and to manage decryption
exclusions.
SSL Decryption Exclusions
Settings | Description |
|---|---|
Modify or Add a Decryption
Exclusion | |
Hostname | Enter a Hostname to define a
custom decryption exclusion. The firewall compares the hostname to
the SNI requested by the client or to the CN presented in the server
certificate. The firewall excludes sessions in which the server
presents a CN that contains the defined domain from
decryption. You can use asterisks (*) as wildcards to create
decryption exclusions for multiple hostnames associated with a
domain. Asterisks behave the same way that carets (^) behave for
URL category
exceptions—each asterisk controls one variable subdomain
(label) in the hostname. This enables you to create both very
specific and very general exclusions. For example:
To exclude video-stats.video.google.com from decryption but not
video.google.com, add *.*.google.com to the SSL Decryption Exclusion
list. Hostnames should be unique for each entry. If a
predefined entry is delivered to the firewall that matches an
existing custom entry, the custom entry takes precedence. You cannot edit the hostname for a predefined decryption exclusion. |
Shared | Select Shared to share a
decryption exclusion across all virtual systems in a multiple
virtual system firewall. While predefined decryption
exclusions are shared by default, you can enable and disable both
predefined and custom entries for a specific virtual
system. |
Description | (Optional) Describe the application that you
are excluding from decryption, including why the application breaks
when decrypted. |
Exclude | Exclude the application from decryption. Disable this
option to start decrypting an application that was previously
excluded from decryption. |
Manage Decryption Exclusions | |
Enable | Enable one or more entries to
exclude them from decryption. |
Disable | Disable one or more predefined decryption exclusions. This effectively
removes support for the applications because they break
decryption. Use this option to ensure certain encrypted applications do not enter your network. |
Show obsoletes | Select Show obsoletes to view
predefined entries that Palo Alto Networks no longer defines as
decryption exclusions. More about obsolete
entries:Updates to predefined decryption exclusions
(including the removal of a predefined entry) are delivered to the
firewall as part of Applications and Threats content updates.
Predefined entries with Exclude from
decryption enabled are automatically removed from
the list of SSL decryption exclusions when the firewall receives a
content update that no longer includes that entry. However,
predefined entries with Exclude from
decryption disabled remain on the SSL decryption
exclusion list even after the firewall receives a content update
that no longer includes that entry. When you select Show
obsoletes, you will see disabled predefined entries
that are no longer enforced. You can remove these entries manually
as needed. |
Show Local Exclusion Cache | Show Local Exclusion Cache displays sites that the firewall automatically
excluded from decryption due to technical issues that prevent
decryption, such as pinned certificates, client authentication, or
unsupported ciphers. Each cache entry includes information about the
application, the server, the reason the firewall excluded the site
from decryption, the decryption profile applied to the traffic, and
the virtual system (vsys). The firewall populates the Local SSL Decryption Cache with locally discovered decryption
exceptions, based on the settings of the decryption profile
associated with the decryption policy rule that controls the
traffic. Sites remain in the local cache for 12 hours and then age
out.
The Local SSL Decryption Cache differs from the SSL Decryption
Exclusion List (DeviceCertificate
ManagementSSL Decryption
Exclusion). The SSL Decryption Exclusion List is for
more permanent exclusions. It contains predefined sites identified
by Palo Alto Networks as preventing decryption and exclusions you
choose to add. |