Cisco Secure Access for Government Help

PDF

Cisco Secure Access for Government Help

Manage Traffic Decryption

Want to summarize with AI?

Log in

Describes managing traffic decryption. Decryption is used for various purposes in Secure Access. You will configure decryption when you configure those features.



Internet Access Features Requiring Decryption

The following features require decryption or do not work effectively on encrypted traffic:

  • Intrusion prevention (IPS) for traffic to internet destinations.

    Traffic must be decrypted in order to inspect HTTPS traffic for known threats and behaviors.

  • Web security (configured in security profiles).

    Decryption is required for inspection by the security and acceptable use features.

  • File inspection and analysis and enforcement of file type controls. For more information, see Manage File Inspection and File Analysis and Manage File Type Control.

  • Destinations that are derived from SAML configurations.

  • Remote browser isolation (RBI)—If you choose Isolate as the rule action in an internet access rule, affected traffic must be decrypted. Enable decryption in the security profile that you choose for that rule.

  • Displaying block and warning notifications to end users. When a destination triggers a warning page, users can only access that destination by clicking the link in the warning notification. For more information, see

Sites that use HTTP rather than HTTPS do not require decryption to benefit from the functionality listed above. However, most sites use HTTPS. Enforcement based on threat categories never requires decryption.


Internet Traffic That Should Not Be Decrypted

Certain traffic should not be decrypted for various reasons:

Traffic that should not be decrypted How to Configure, and More Information
Traffic to confidential internet destinations, based on laws, regulations, or policy See Important Information About Do Not Decrypt Lists.
Sites with pinned certificates (for IPS) See Global Settings for Access Rules.
Sites with pinned certificates (for web security features)

N/A

Microsoft 365 applications See Global Settings for Access Rules.
Trusted files

See Advanced settings in the Security Controls section of each internet access rule.

This feature is sometimes called "Protected file bypass."


Decryption in Private Access Rules

Decryption is required for Intrusion prevention (IPS) for traffic to private destinations. Traffic must be decrypted in order to inspect it for known threats and behaviors.

Traffic to private resources will be decrypted for inspection by the IPS feature only if decryption is enabled for that resource and the required certificate is present.

Traffic to private destinations that are not configured as private resources (that is, traffic to destinations that you type directly into an access rule) is not decrypted.

You will configure decryption for private resources when you configure the private resource.

See Add a Private Resource.


Decryption Settings


Decryption Requires Certificates


Decryption Logging


Troubleshooting Decryption


Important Information About Do Not Decrypt Lists

Traffic that is not decrypted cannot be effectively inspected for threats.

However, in order to comply with confidentiality regulations in some locations, certain traffic should not be decrypted. You can use Do Not Decrypt lists to specify these destinations.

Do Not Decrypt lists apply only to destinations in internet access rules, and they are used for both web security and intrusion prevention (IPS) features.

Currently, IPS profiles and security profiles support Do Not Decrypt lists differently:

  • All IPS profiles use a single Do Not Decrypt list.

  • Each security profile can use any Do Not Decrypt list.

  • The types of destinations that you can specify for IPS and web features are different. See the applicable sections below.


Do Not Decrypt List for IPS

Destinations on the system-provided Do Not Decrypt list are not decrypted for inspection by the intrusion prevention (IPS) feature.

All IPS profiles use the system-provided Do Not Decrypt list that ships with Secure Access. You can add destinations to this list.

To configure this list, navigate to Secure > Settings > Do Not Decrypt Lists.

Note
About decryption in private access rules

Do not use the system-provided Do Not Decrypt list for private destinations. Instead, you can configure a private resource and not enable decryption for that resource. See Add Private Resources.


Do Not Decrypt Lists for Web

When a Do Not Decrypt list is associated with a security profile, destinations on the list will not be decrypted by the security and acceptable use features enabled in that profile.

Initially, the default Do Not Decrypt List for security profiles is the same system-provided Do Not Decrypt List that is used for IPS. You can either use this single list for both IPS and security security features, or you can create additional do-not-decrypt lists for use in security profiles. If you want to specify applications as destinations for web security features, create a custom Do Not Decrypt list and specify that list in the security profile. See Add a Do Not Decrypt List for Security Profiles.


Differences Between IPS and Web Destination Types

The types of destinations that you can choose not to decrypt is different for IPS and web security features:

Applications Sites that belong to specified Content Categories Domains

IPS

No Yes Yes

Web

Yes Yes Yes

The System-Provided Do Not Decrypt List

The system-provided Do Not Decrypt list is the only list used by the IPS feature. The same list is the default list used by the web security features. The system-provided Do Not Decrypt list does not include the ability to specify applications; this option is available only in custom lists.

Initially, this list is empty. Add the destinations that are important to your organization.


Limitation: Do Not Decrypt Based on Content Category

While web site categorization is updated continuously, it is not possible to categorize all web sites on the internet, and some sites may be categorized incorrectly. Therefore, if you choose not to decrypt traffic based on content category, it is possible that traffic to sites that should not be decrypted may be decrypted, and traffic that should be decrypted may not be decrypted.

This limitation is not unique to Cisco.


Add a Do Not Decrypt List for Security Profiles

Decrypting traffic to certain destinations may be prohibited by regional privacy regulations.

Create a custom Do Not Decrypt list to specify destinations that will not be decrypted by the security and acceptable use features in a security profile. HTTPS traffic to these destinations cannot be properly inspected for threats when traffic is not decrypted.

If you need to specify a Do Not Decrypt address for IPS profiles, edit the system-provided Do Not Decrypt List.

Before you begin

Procedure

  1. Navigate to Secure > Settings > Do Not Decrypt Lists and click Add.


    The Do Not Decrypt Lists interface.
  2. Give your list a good descriptive List Name.


    The List Name interface.
  3. Add content categories, applications, and domains that will be exempt from decryption:

    1. Click Add, select Categories to be exempt from HTTPS inspection and then click Close.
      The Add Content Categories interface.
    2. Click Add, select Categories to be exempt from HTTPS inspection and then click Close.
      The Add Content Categories interface.
    3. Click Add, select Applications to be exempt from decryption and then click Close.
      The Add Applications interface.
  4. Click Save.

    Your new Do Not Decrypt List is saved to Secure Access and available for selection when adding Security profiles to the Access policy.