Add servers that break decryption for technical reasons, such as an internal custom
application, to the SSL decryption exclusion list to automatically exclude them from
decryption.
| Where Can I Use
This? | What Do I Need? |
|
|
No separate license required for decryption when using NGFWs or
Prisma Access.
Note: The features and capabilities available to you in
Strata Cloud Manager depend on your active license(s).
|
Sometimes applications, websites, or services encounter technical issues when
decryption is attempted. Reasons that sites break decryption technically include
pinned certificates, client authentication, incomplete certificate chains, and
unsupported ciphers. For HTTP public key pinning (HPKP), most browsers that use HPKP
permit Forward Proxy decryption as long as you install the enterprise CA certificate
(or the certificate chain) on the client. The most common sites that break
decryption or do not work optimally are included in
Palo Alto Networks predefined decryption exclusion
list.
If decryption breaks an important application or service technically, you can add the
hostname of the site hosting the application or service to a custom SSL decryption
exclusion list. The Next-Generation Firewall (NGFW) doesn’t decrypt,
inspect, or apply Security policy rules or decryption policy rules to traffic on
this list. For example, an internal custom application that breaks decryption but is
business-critical should be added to the list so the custom application traffic is
allowed. If a website whose applications and services break decryption technically
is not on either the predefined or custom decryption exclusion list, it is blocked.
For security purposes, be sure that only sites you need for business purposes are
added to this list.
Before adding a custom exclusion, check the predefined exclusion list. If the
hostname is already listed, a custom entry is not required.
The SSL decryption exclusion list is
not for sites you intentionally do
not decrypt for legal, regulatory, business, or privacy reasons. For traffic you
choose not to decrypt,
create a policy-based decryption
exclusion.
If the technical reason for excluding a site from decryption is an incomplete
certificate chain, the
NGFW doesn’t automatically fix the chain
as a browser would. If you need to add a site to the SSL decryption exclusion
list, review the site to ensure it’s a legitimate business site, then download
the missing sub-CA certificates and
load and deploy them onto the
NGFW or an
NGFW or
Prisma Access management
interfaces.
After a server is added to the SSL decryption exclusion list, the NGFW
compares the server hostname in the decryption exclusion entry against both the
Server Name Indication (SNI) in the client hello message and the Common Name (CN) in
the server certificate. If either the SNI or CN matches the entry, the NGFW does not decrypt the traffic.
Exclude a Server from Decryption for Technical Reasons (Strata Cloud Manager)
Add servers to the Global Decryption Exclusions list to exclude them from decryption
for technical, business, regulatory, personal, or other reasons.
Log in to
Strata Cloud Manager.
Navigate to the Global Decryption Exclusions settings.
Add an entry to the
Custom Exclusions list.
Click the
+ (plus icon).
Enter the
Hostname of the website or application
you want to exclude from decryption. The hostname is
case-sensitive.
Make sure that the hostname is unique for each entry. If the
hostname of a predefined exclusion matches the hostname of a
custom entry, the custom entry takes precedence.
You can
use
wildcards to exclude multiple hostnames associated
with a domain. The
NGFW does not decrypt the
sessions if the server presents a Common Name (CN) that matches
the domain.
(
Optional) Enter a
Description.
-
Exclude a Server from Decryption for Technical Reasons (PAN-OS)
Log in to the web interface.
Navigate to the SSL Decryption Exclusions list.
Add a new decryption exclusion, or select an existing
custom entry to modify.
Enter the
hostname of the website or application
you want to exclude from decryption. The hostname is
case-sensitive.
Make sure that the hostname field is unique for each custom
entry. If a predefined exclusion matches a custom entry, the
custom entry takes precedence.
You can
use
wildcards to exclude multiple hostnames associated
with a domain. The
NGFW does not decrypt the
sessions if the server presents a Common Name (CN) that matches
the domain.
(
Optional) To share the exclusion across all virtual systems
in a multiple virtual system
NGFW, select
Shared.
Exclude the application from decryption.
In contrast, you can deselect this option to begin decrypting an
entry that was previously excluded from decryption.
Click
OK.
Commit your changes.