Configure and Deploy SSL Proxy Policy in CSO
SSL proxy is enabled as an application service within a security policy. You specify the traffic that you want the SSL proxy enabled on as match criteria and then specify the SSL proxy profile to be applied to the traffic. For more information, seeSSL Forward Proxy Overview in the CSO Customer Portal User Guide (available on the CSO Documentation page).
Explanation of Procedure
The following is the workflow to configure and deploy an intent-based SSL forward proxy policy in CSO:
For examples of how SSL proxy policy intents are applied, see Understanding How SSL Proxy Policy Intents Are Applied in the CSO Customer Portal User Guide (available on the CSO Documentation page).
Import a Certificate
If you want to use the SSL proxy feature in CSO, you must import at least one root certificate for a tenant. The certificate can then be installed in one or more sites.
To import a certificate:
After importing a certificate, you can use it when you add an SSL proxy profile.
Setting |
Guideline |
---|---|
Certificate Name |
Enter the certificate name, which must be a unique string of alphanumeric characters and some special characters (_ -). No spaces are allowed and the maximum length is 32 characters. |
Certificate Type |
Select an option to specify whether the certificate that you are importing is a root certificate (Root CA) or a trusted certificate (Trusted CA). |
Passphrase |
Enter the passphrase to protect the private key or key pair of the Privacy-Enhanced Mail (PEM) certificate file. |
Description |
Enter a description for the certificate. |
Certificate Content |
Select whether you want to import the certificate content from a file or if you want to paste the certificate content. Note:
|
File Path for Certificate |
To import the certificate content from a file, click Browse. In the File Upload dialog that appears, select the certificate file and click Open. The filename of the file that you uploaded is displayed. |
Paste Certificate Content |
To paste the certificate content directly from a file, open the certificate file in a text editor, copy the certificate content, and paste it in the text box. |
The following is an example of root certificate content.
-----BEGIN PRIVATE KEY----- AbcXyz123AbcXyz123AbcXyz123AbcXyz123AbcXyz123AbcXyz123AbcXyz123A AbcXyz123AbcXyz123AbcXyz123AbcXyz123AbcXyz123AbcXyz123AbcXyz123A AbcXyz123AbcXyz123AbcXyz123AbcXyz123AbcXyz123AbcXyz123AbcXyz123A AbcXyz123AbcXyz123AbcXyz123AbcXyz123AbcXyz123AbcXyz123AbcXyz123A AbcXyz123AbcXyz123AbcXyz123AbcXyz123AbcXyz123AbcXyz123AbcXyz123A AbcXyz123AbcXyz123AbcXyz123AbcXyz123AbcXyz123AbcXyz123AbcXyz123A -----END PRIVATE KEY----- -----BEGIN CERTIFICATE----- DefQrs456DefQrs456DefQrs456DefQrs456DefQrs456DefQrs456DefQrs456A DefQrs456DefQrs456DefQrs456DefQrs456DefQrs456DefQrs456DefQrs456A DefQrs456DefQrs456DefQrs456DefQrs456DefQrs456DefQrs456DefQrs456A DefQrs456DefQrs456DefQrs456DefQrs456DefQrs456DefQrs456DefQrs456A DefQrs456DefQrs456DefQrs456DefQrs456DefQrs456DefQrs456DefQrs456A DefQrs456DefQrs456DefQrs456DefQrs456DefQrs456DefQrs456DefQrs456A DefQrs456DefQrs456DefQrs456DefQrs456DefQrs456DefQrs456DefQrs456A DefQrs456DefQrs456DefQrs456DefQrs456DefQrs456DefQrs456DefQrs456A DefQrs456DefQrs456DefQrs456DefQrs456DefQrs456DefQrs456DefQrs456A -----END CERTIFICATE-----
Install a Certificate
After you import a certificate into CSO, you can install the certificates on one or more sites.
To install a certificate:
Add SSL Forward Proxy Profiles
To add an SSL forward proxy profile:
Ensure that you have a root certificate imported for the tenant before you add an SSL forward proxy profile. You can import SSL certificates (root and trusted) from the Certificates page (Administration > Certificate Management > Certificates) and associate the certificates with SSL forward proxy profiles.
Setting |
Guideline |
---|---|
General Information |
|
Name |
Enter a unique name for the profile, which can contain alphanumeric characters, hyphens, and underscores. No spaces are allowed and the maximum length is 63 characters. |
Description |
Enter a description for the profile. The maximum length is 255 characters. |
Preferred Cipher |
Select a preferred cipher, which enables you to define an SSL cipher that can be used with acceptable key strength:
|
Custom Ciphers |
If you specified a custom preferred cipher, you can define a custom cipher list by selecting one or more ciphers that the SSH server can use to perform encryption and decryption functions:
|
Flow Trace |
Click the toggle button to enable flow tracing to enable the troubleshooting of policy-related issues. Flow tracing is disabled by default. |
Root Certificate |
Select a root certificate from the list or click Add Root Certificate to import a root certificate. In a public key infrastructure (PKI) hierarchy, the root certificate authority (CA) is at the top of the trust path. |
Trusted Certificate Authorities |
Choose whether you want to add all trusted certificates present on the device (All) or select specific trusted certificates (Select Specific). Before establishing a secure connection, the SSL proxy checks CA certificates to verify signatures on server certificates. If you chose to add selected trusted certificates, the existing trusted certificates are displayed. Select one or more certificates by clicking the check boxes, and click the > icon. The selected certificates are displayed in the column on the right. Optionally, click Add Trusted Certificates to import a trusted certificate. See Import a Certificate. Note:
|
Exempted Addresses |
Exempted addresses include addresses that you want to exempt from undergoing SSL proxy processing. To specify exempted addressees, select one or more addresses in the left column and click the > icon to confirm your selection. The selected addresses are then displayed in the right column. These addresses are used to create allow lists that bypass SSL forward proxy processing. Because SSL encryption and decryption are complicated and expensive procedures, network administrators can selectively bypass SSL proxy processing for some sessions. Such sessions typically include connections and transactions with trusted servers or domains with which network administrators are very familiar. There are also legal requirements to exempt financial and banking sites. Such exemptions are achieved by configuring the IP addresses or domain names of the servers under allow lists. Note:
You can also add addresses by clicking Add New Address. For more information, see Creating Addresses or Address Groups in the CSO Customer Portal User Guide (available at the CSO Documentation page). |
Exempted URL Categories |
Select one or more previously defined URL categories in the left column and click the > icon to confirm your selection. The selected addresses are then displayed in the right column. These URL categories are used to create allow lists that bypass SSL forward proxy processing. The selected URL categories are exempted during SSL inspection. |
Actions |
|
Server Auth Failure |
Click the toggle button to enable CSO to ignore errors encountered during the server certificate verification process, such as CA signature verification failure, self-signed certificates, and certificate expiry. This toggle button is disabled by default, which means that server authentication errors are not ignored. We do not recommend that you ignore authentication errors because it results in websites not being authenticated at all. However, you can use this option to effectively identify the root cause for dropped SSL sessions. |
Session Resumption |
Click the toggle button to enable session resumption. Session resumption is disabled by default. To improve throughput and still maintain an appropriate level of security, SSL session resumption provides a session-caching mechanism so that session information, such as the pre-master secret key and agreed-upon ciphers, can be cached for both the client and server. |
Logging |
Select one or more events to be logged. You can choose to log all events, warnings, general information, errors, or different sessions (allowed, dropped, or ignored). By default, no events are logged. |
Renegotiation |
Select one of the following options if a change in SSL parameters requires renegotiation:
After a session is created and SSL tunnel transport has been established, a change in SSL parameters requires renegotiation. SSL forward proxy supports both secure (RFC 5746) and nonsecure (TLS v1.0 and SSL v3) renegotiation. When session resumption is enabled, session renegotiation is useful in the following situations:
|
Add SSL Proxy Policy Intents
An SSL proxy policy intent enables you to configure an SSL proxy between source and destination endpoints by associating the latter with an SSL proxy profile. You can add an SSL proxy policy intent inline on the SSL Proxy Policy page.
To add an SSL proxy policy intent:
Setting |
Guideline |
---|---|
[Name] |
Enter the name of the SSL proxy policy intent in the first text box. If you do not enter a name, the system-generated name is used. The name that you enter must begin with an alphanumeric character and can contain alphanumeric characters and some special characters (- _). The maximum length is 63 characters. |
[Description] |
Enter the description of the SSL proxy policy intent in the second text box. |
Source |
Select one or more of the following source endpoints:
The default source for an SSL proxy policy intent is All Sites. If you don’t add a source, then the default is used. Note:
A source IP address value of Any signifies any IP address from any site. |
Destination |
Select one or more of the following destination endpoints:
The default destination for an SSL proxy policy intent is Internet. If you don’t add a destination, then the default is used. Note:
A destination IP address value of Any signifies traffic going to the Internet (any address). Traffic within sites (internal traffic) is not covered by the destination IP address value of Any. If you want to cover traffic between two sites, ensure that the sites are included in both the source and destination endpoints. |
SSL Proxy Profile |
Specify an SSL proxy profile to associate with the SSL proxy policy intent in one of the following ways:
|
Deploy an SSL Proxy Policy
After you add one or more SSL proxy policy intents, you must deploy the SSL proxy policy.
To deploy an SSL proxy policy: