Creating SSL Reverse Proxy Profiles
Use the SSL Reverse Proxy Profiles page to configure the SSL reverse proxy to protect your SSL-enabled web servers against client-to-server attacks from malicious clients. This functions by loading the SSL private key onto the SRX Series device to protect your clients against threats from web servers that you do not control. For example, if an external user on the internet is trying to access a corporate web server, they initiate the HTTPS connection to the web server. The IPS policy which has the private key of the web server intercepts the traffic, inspects it for attacks, and if no attacks are present, it forwards it onto the destination web server.
Starting in Junos Space Security Director Release 21.2, SSL Reverse Proxy is supported for Logical Systems (LSYS) devices also.
To create an SSL reverse proxy profile:
- Select Configure > SSL Profiles> SSL Proxy Profiles.
The SSL Proxy Profiles page appears.
- Select Reverse Proxy from the Create list.
- Complete the configuration according to the guidelines provide in Table 1.
- Click OK.
An SSL reverse proxy profile is created that can be assigned to a firewall policy for advanced security options.
Table 1: Fields on the Create SSL Reverse Proxy Profile Page
Enter a unique string of alphanumeric characters, colons, periods, dashes, and underscores. No spaces are allowed; maximum length is 63 characters.
Enter a description for the SSL forward proxy profile; maximum length is 1024 characters.
Select a preferred cipher. Ciphers are divided into the following categories depending on their key strength.
Select the set of ciphers the SSH server can use to perform encryption and decryption functions. If this option is not configured, the server accepts any supported suite that is available.
The available custom ciphers are:
Select this option to enable flow trace for troubleshooting policy-related issues.
Specify the server certificate identifier.
Select the required SRX Series device from the list and assign the server certificate identifier.
Note: To view the SSL certificates in Security Director, select Devices>Security Devices, choose the relevant device, right-click the device or select Refresh Certificate from the More menu. Once the refresh certificate job is completed, you can see SSL certificates.
Make sure the device configuration is in sync with Security Director. If the device configuration is out of sync in security devices, resynchronize network and then proceed with refresh certificates.
Select addresses to create allowlists 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 mostly 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 allowlists.
Exempted URL Categories
Starting in Junos Space Security Director Release 16.2, you can select URL categories to create allowlists that bypass SSL forward proxy processing.
These URL categories are exempted during SSL inspection. Only the predefined URL categories can be selected for the exemption.
Select the Disable Session Resumption option if you do not want session resumption.
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-primary secret key and agreed-upon ciphers, can be cached for both the client and server.
Select this option to generate logs. You can choose to log all events, warnings, general information, errors, or different sessions (allowlisted, allowed, dropped, or ignored).
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.
Select one of the following options if a change in SSL parameters requires renegotiation:
When session resumption is enabled, session renegotiation is useful in the following situations: