Policy Object: Decryption Profile
Network Security

Policy Object: Decryption Profile

Table of Contents

Policy Object: Decryption Profile

Define traffic for your configuration to decrypt and the type of decryption you want to perform
Where Can I Use This?
What Do I Need?
  • NGFW (Cloud Managed)
  • NGFW (PAN-OS & Panorama Managed)
  • Prisma Access (Managed by Strata Cloud Manager)
  • Prisma Access (Managed by Panorama)
Check for any license or role requirements for the products you're using.
A decryption profile allows you to perform checks on both decrypted traffic and SSL traffic that you
to exclude from decryption. (If a server breaks SSL decryption technically due to certificate pinning or other reasons, add the server to the Decryption Exclusion list.) Depending on your needs, create Decryption profiles to:
  • Block sessions based on certificate status, including blocking sessions with expired certificates, untrusted issuers, unknown certificate status, certificate status check timeouts, and certificate extensions.
  • Block sessions with unsupported versions and cipher suites, and that require using client authentication.
  • Block sessions if the resources to perform decryption are not available or if a hardware security module isn't available to sign certificates.
  • Define the protocol versions and key exchange, encryption, and authentication algorithms allowed for SSL Forward Proxy and SSL Inbound Inspection traffic in the SSL Protocol Settings.
Don’t weaken the main Decryption profile that you apply to most sites to accommodate weaker sites. Instead, create one or more separate Decryption profiles for sites that you need to support but that don’t support strong ciphers and algorithms. You can also create different Decryption profiles for different URL categories to fine-tune security vs. performance for traffic that contains no sensitive material; however, you should always decrypt and inspect all the traffic you can.
After you create a decryption profile, attach it to a decryption policy rule; your configuration then enforces the decryption profile settings on traffic that matches the decryption security rule.
Your configuration includes a default decryption profile that you can use to enforce the basic recommended protocol versions and cipher suites for decrypted traffic.
Avoid supporting weak protocols or algorithms because they contain known vulnerabilities that attackers can exploit. If you must allow a weaker protocol or algorithm to support a key partner or contractor who uses legacy systems with weak protocols, create a separate Decryption profile for the exception and attach it to a Decryption security rule that applies the profile only to the relevant traffic (for example, the source IP address of the partner). Don’t allow the weak protocol for all traffic.

Create a Decryption Profile

Recommended For You