Thursday, March 31, 2016

SSL -Https inspection

Best Practices - HTTPS Inspection
Solution
This article outlines some recommendations and best practices for easy HTTPS Inspection deployment and usage to help avoid common configuration issues.
Note: To benefit from the latest improvements in security, performance and stability, Check Point always recommends to upgrade to the most recent version (upgrade Security Gateway / upgrade Cluster / upgrade VSX / upgrade 600 appliance / upgrade 1100 appliance / upgrade Security Management Server / upgrade Multi-Domain Security Management Server / upgrade SmartConsole).

Table of Contents:
  1. Introduction
    1. HTTPS Inspection - Inbound vs. Outbound
    2. Gradual Deployment
    3. Initial configuration
  2. Best Practices
    1. Configuring certificates
    2. Creating the HTTPS Inspection Rule Base
    3. Internet connection
  3. Additional Information
    1. Perfect Forward Secrecy Cipher Suites
    2. Mobile Applications
    3. Update Services
    4. Categorized HTTPS vs. HTTPS Inspection
  4. Performance
  5. Debug
    1. Notes
    2. WSTLSD daemon (SSL handshake)
    3. HTTPS Inspection related issues
    4. HTTPS Inspection rulebase matching
  6. Related documentation
  7. Related solutions
  8. Revision history

(I) Introduction

HTTPS Internet traffic uses the SSL (Secure Sockets Layer) protocol and is encrypted to give data privacy and integrity. However, HTTPS traffic has a possible security risk and can hide illegal user activity and malicious traffic. With HTTPS Inspection, the Security Gateway can inspect the traffic that is encrypted by HTTPS.
The Security Gateway uses certificates and becomes an intermediary between the client computer and the secure web site. All data is kept private in HTTPS Inspection logs. Only administrators with HTTPS Inspection permissions can see all the fields in a log.
HTTPS ratio of internet traffic is constantly growing. However, malicious attacks, dangerous web activity and data loss can hide away from the inspection of the Security Gateway under the SSL layer.
Therefore it is recommended to enable HTTPS Inspection to improve security. By enabling HTTPS Inspection, the Security Gateway will inspect the encrypted parts of the HTTPS traffic.
The HTTPS Inspection Rule Base is a set of rules used to define which HTTPS traffic will be inspected by the Security Gateway. The inspection will be performed by all the Software Blades that support HTTPS Inspection:
  • Application Control
  • URL Filtering
  • IPS
  • DLP
  • Anti-Virus
  • Anti-Bot

(I-1) Introduction: HTTPS Inspection - Inbound vs. Outbound

  • Inbound HTTPS Inspection protects internal servers (for example, data centers and web servers) from malicious attacks coming from the Internet.
    Inbound connections are HTTPS connections that start from an external client and connect to an internal server in the DMZ or the network. The Security Gateway compares the HTTPS request to the HTTPS Inspection Rule Base. If the request does not match a rule, the packet is not decrypted.
    If the request matches an inspection rule, the Security Gateway uses the certificate for the internal server to create a HTTPS connection with the external client. The Security Gateway creates a new HTTPS connection with the internal server. Since the Security Gateway has a secure connection with the external client, it can decrypt the HTTPS traffic. The decrypted traffic is inspected according to the policy.
    Flow on Security Gateway:
    1. Intercept the request.
    2. Use the server's original certificate and private key to initiate an SSL connection with the client.
    3. Create and establishes a new SSL connection with the web server.
    4. Using the two SSL connections:
      1. Decrypt the encrypted data from the client.
      2. Inspect the clear text content for all blades set in the policy.
      3. Encrypt the data again to keep client privacy as the data travels to the destination server behind the Security Gateway.

  • Outbound HTTPS Inspection protects internal users and perimeter servers from malicious attacks coming from the Internet on connections originated from inside the organization.
    Outbound connections are HTTPS connections that start from an internal client and connect to the Internet. The Security Gateway compares the HTTPS request to the HTTPS Inspection Rule Base. If the request does not match a rule, the packet is not decrypted.
    If the request matches an inspection rule, the Security Gateway makes sure that the certificate from the server (in the Internet) is valid. The Security Gateway creates a new certificate and uses it for a new HTTPS connection to the server. There are two HTTPS connections, one to the internal client and one to the server. It can then decrypt and inspect the packets according to the Security Gateway and other Rule Bases. The packets are encrypted again and sent to the destination.
    Flow on Security Gateway:
    1. Intercept the request.
    2. Establish a secure connection to the requested web site and validate the site server's certificate.
    3. Create a new SSL certificate for the communication between the Security Gateway and the client, send the client the new certificate and continue the SSL negotiation with it.
    4. Using the two SSL connections:
      1. Decrypt the encrypted data from the client.
      2. Inspect the clear text content for all blades set in the Policy.
      3. Inspect the traffic coming from the web site into the organization.
      4. Encrypt the data again to keep client privacy as the data travels to the destination web server resource.


(I-2) Introduction: Gradual Deployment

When first enabling HTTPS Inspection, it is recommended to use a gradual approach. Starting with few Security Gateways and networks, and expanding from there to cover all Security Gateways and networks. Do this by configuring the HTTPS Inspection rulebase to inspect a single subnet or few subnets. HTTPS Inspection can be enabled on a single Security Gateway at first, and then expanded to additional Security Gateways.

(I-3) Introduction: Initial configuration

Refer to Application Control and URL Filtering Administration Guide (R75.20, R75.40, R75.40VS, R76, R77) - Chapter "Managing Application Control and URL Filtering" - "HTTPS Inspection".

(II) Best Practices

(II-1) Best Practices: Configuring certificates

  1. Using the entire certificate chain for configuring inspection of incoming traffic
    When importing an internal server's certificate for incoming traffic inspection, it is necessary to include all the intermediate CAs of the chain in the *.p12 file. Inclusion of only the server certificate may cause some browsers to warn about untrusted sites, since some browsers are unable to fetch and validate the complete certificate chain.

  2. CA creation/import - Using a CA certificate for HTTPS Inspection of outgoing traffic
    When importing an external certificate in SmartDashboard on the blade's tab - "Advanced" - "HTTPS Inspection" - "Gateways" - "Import Certificate from file...", it is imperative to use a CA certificate, so that this certificate can be used to sign certificates generated by Security Gateway for outgoing traffic inspection.
    Importing a non-CA certificate will result in client browsers refusing the connection.

    Notes:
    • The administrator may generate a CA certificate from the Security Gateway properties - "HTTPS Inspection".
      That CA certificate will be used to sign the certificates generated by Security Gateway.
    • The best practice would be:
      • 1) deploy this certificate on the entire organization (usually through GPO for Windows domain)
      • 2) export a CA certificate from an existing CA of the organization
      • 3) sign a new CA certificate from an existing CA of the organization
    • For fastest deployment, the order should be (because computers should probably already use the organization CA):
      • 3) sign a new CA certificate from an existing CA of the organization
      • 2) export a CA certificate from an existing CA of the organization
      • 1) deploy this certificate on the entire organization (usually through GPO for Windows domain)
      OR
      • 2) export a CA certificate from an existing CA of the organization
      • 3) sign a new CA certificate from an existing CA of the organization
      • 1) deploy this certificate on the entire organization (usually through GPO for Windows domain)
    • For best security, the order should be:
      • 3) sign a new CA certificate from an existing CA of the organization
      • 1) deploy this certificate on the entire organization (usually through GPO for Windows domain)
      • 2) export a CA certificate from an existing CA of the organization
  3. Making sure all intermediate certificates in the chain are signed with SHA-256 to avoid browser warnings
    For both incoming and outgoing inspection, validate that all intermediate certificates in the chain are signed with SHA-256 (or higher) algorithm.
    Otherwise, browsers may warn (either by icon next to the URL, or in other ways) that the connection is not secure enough.
    This limitation applies only to intermediate certificates in the chain, and not to root CAs.

(II-2) Best Practices: Creating the HTTPS Inspection Rule Base

  1. What to Inspect
    It is highly recommended to inspect HTTPS traffic from desktop browsers (Outbound HTTPS Inspection).
    Users may choose to bypass certain categories due to privacy considerations.
    Non-browser HTTPS applications tend to trust their own root CA store and not to trust the certificate generated by the Security Gateway (examples: Google Drive, DropBox).
    In addition, non-browser HTTPS applications may use non-standard SSL and therefore cannot be inspected by the Security Gateway.
    These limitations are not specific to Check Point.
    It is possible to bypass these connections by Server IP address (when available), Client IP address (if there are few clients using these applications), or user identity.
    In cases the server uses standard SSL, bypass according to Category/URL can also be used.
  2. Inspection of sites with a multi-category certificate
    HTTPS Inspection bypass decisions are based on the server's certificate.
    It is important to note that there are servers that issue a single certificate for several domains from different categories (Search Engines / Portals, Media Sharing, etc.).
    For example, see the Google certificate below:

    Without SSL decryption, there is no way for the Security Gateway to know the underlying URL and easily categorize the connection.
    Yet, in order to enable bypass rules of HTTPS Inspection, it is necessary to determine the site's category without SSL decryption - site category is resolved according to the FQDN of server's certificate.
    This is a trade-off between usability, connectivity and security, since there are sites that offer many services behind a single certificate, thus sharing the same FQDN among multiple categories.
    Therefore, the Site Category is determined by the certificate FQDN and the IP address, which presented the certificate, and should take into account the entire list of servers, which will be bypassed/inspected.
    Every connection to servers, which display such a multi-purpose certificate, will be categorized in the same way - the rulebase decision to inspect or bypass a connection will be made according to the category matched to the FQDN of the certificate.
    Let us examine the following rulebase:
    Since YouTube and Google Search present the same certificate - the connections to both sites will be matched as if they are both categorized as "Search Engines" - the bypass rule of YouTube will be ignored.
    Therefore, users should take into account that in certain cases, the connections will be matched according to the category of the FQDN.

(II-3) Best Practices: Internet connection

Make sure the Security Gateway is connected to the Internet, either directly or through a proxy. Proxy can be defined in the Security Gateway properties, or in the Global Properties.
If there is no Internet connection, then CRL fetch and intermediate CA fetch will fail (this will be logged). The inspection will take place; however, URL-based or Category-based bypassing will not work.
Untrusted certificates and lack of CRLs can be configured as reasons to drop the connection:
Note: Checking the box "Log connections of clients that have not installed the CA certificate" will log connections of clients that have not installed the CA certificate, however it will also log other cases of dropped connections. It is recommended to clear this box.

Note about Bridge interfaces: In order for inspection to work properly, CRL validation is required. Therefore the Security Gateway must have an Internet connection in addition to the bridge interfaces.

(III) Additional Information

(III-1) Additional Information: Perfect Forward Secrecy Cipher Suites

  • Perfect Forward Secrecy (PFS) - introduction
    Perfect Forward Secrecy (PFS) is a key agreement method that saves the need of transferring shared secrets on the wire, thus guaranteeing secrecy in the future, even if the traffic is recorded in the present.
    PFS is widely used in TLS and IKE/IPsec.
  • Perfect Forward Secrecy (PFS) - ECDHE
    Diffie-Hellman (DH) has been the traditional PFS algorithm.
    Elliptic curve Diffie-Hellman (ECDH) is a modern PFS algorithm based on Elliptic Curve computations. Same security level of Diffie-Hellman is achieved with much shorter keys in ECDH, so performance is much better.
    ECDHE is a protocol that uses Ephemeral ECDH keys.
    Some Web servers only accept PFS ciphers (DHE, ECDHE).
    ECDHE is fully supported in these versions of Security Gateway (ID 01418393):
    For Security Gateways R77.20 and lower, connections to such web servers will fail without a log. An example of such a web server is tumblr.com.
    If you encounter such issue, then Contact Check Point Support to get a Hotfix from sk104717 (Issue ID 01418393).
    A Support Engineer will make sure the Hotfix is compatible with your environment before providing the Hotfix.
    For faster resolution and verification, please collect CPinfo files from the Security Management Server and Security Gateways involved in the case.
Refer to:
Note: Some web servers do not accept any of the Security Gateway's proposals. Connections to such web servers will fail without a log. If you encounter such issue, thencontact Check Point Support for assistance.

(III-2) Additional Information: Mobile Applications

Mobile Applications (non-browser clients) and Mobile browsers do not work well with HTTPS Inspection. These clients cannot be forced to trust the Security Gateway's Certificate Authority (CA).
Some applications produce warnings, and others simply block the traffic.
It is recommended to either restrict mobile applications traffic for better security, or to create bypass rules for traffic originating from mobile devices (according to Wi-Fi Access Point's IP address, for example).

(III-3) Additional Information: Update Services

Update services (such as Microsoft updates) are implicitly bypassed in the HTTPS Inspection rulebase.

(III-4) Additional Information: Categorized HTTPS vs. HTTPS Inspection

Starting in R76, "Categorize HTTPS sites" feature (in combination with URL Filtering) lets you categorize a HTTPS site without activating HTTPS inspection to determine the content of the traffic, based on the FQDN of the server's certificate (SmartDashboard - go to "Application & URL Filtering" tab - in the left pane, go to "Advanced" - go to "Engine Settings" - in the "URL Filtering" section, check the box "Categorize HTTPS sites").
"Categorize HTTPS sites" feature does not perform inspection on the traffic. Policy, based upon the categorized inspection, should take into account that the confidence level is lower than that of HTTPS Inspection.
When the "Categorize HTTPS sites" option is enabled:
  1. The server's certificate is detected and validated
  2. If the server is trusted, then the DN is extracted from the certificate
  3. The DN is used to categorize the site
The Categorize HTTPS sites option does not run if:
  • HTTPS Inspection is enabled
  • There is a proxy between the destination site and the Security Gateway (or the Security Gateway functions as a proxy)

(IV) Performance

HTTPS Inspection creates additional load on Security Gateway's CPU due to these reasons:
  • SSL termination, encrypt/decrypt and active TCP termination that consume CPU resources (Note: The SSL handshake rate was significantly improved in R77.30 - refer to sk103081 and to sk104717).
  • Additional traffic is inspected by the security blades.
It is possible to approximate the effect of HTTPS Inspection activation under the following disclaimers:
  1. Representing a typical, outbound configuration (low or none inbound HTTPS Inspection traffic) with 36% HTTPS.
  2. Using R77.30 with either NGTP (Firewall, IPS, Application Control, URL Filtering, Anti-Virus, and Anti-Bot), or NGFW (Firewall, IPS and Application Control) software blades for inspection.
  3. Data Center scenario requires specific modeling.
The rational is that under the disclaimers written above, the impact on required Security Power (SPU) is 60% to 100% higher depending on the enabled software blades (the more blades are already enabled, the smaller the additional impact of HTTPS Inspection will be).
Therefore, when enabling HTTPS Inspection in an existing configuration, the CPU utilization on Security Gateway is expected to increase:
  • by factor of 1.6 for NGTP configuration
  • by factor of 2 for NGFW configuration
For Check Point Partners: refer to sk108757 - How to estimate the performance impact of HTTPS Inspection using the Appliance Sizing Tool.

(V) Debug

(V-1) Debug: Notes

  • Always schedule a maintenance window to run any debug.
  • Contact Check Point Support to get exact debug instructions specific to your case.
  • In cluster environment, debug must be collected on all members of the cluster.
  • To decrease the load on Security Gateway's CPU, the kernel debug can be started only on specific CoreXL FW Instances only.
    The safest way to do so is by starting the kernel debug on CoreXL FW Instance 0:
    # fw ctl debug 0
    # fw ctl debug -buf 32000
    # fw ctl debug -m MODULE + FLAGS
    # fw -i 0 ctl kdebug -T -f > /var/log/debug.txt
  • Refer to Kernel Debug flags (R75.40VS, R76, R77, R77.10, R77.20, R77.30)

(V-2) Debug: WSTLSD daemon

WSTLSD daemon handles SSL handshake for HTTPS Inspected connections.
Refer to sk105559 - How to debug WSTLSD daemon.

(V-3) Debug: HTTPS Inspection related issues

Important Note: This kernel debug can cause very high load on Security Gateway's CPU. Schedule a maintenance window.
  1. Prepare the debug:
    [Expert@HostName:0]# fw ctl debug 0
    [Expert@HostName:0]# fw ctl debug -buf 32000
    [Expert@HostName:0]# fw ctl debug -m fw + conn drop cptls
  2. Verify the debug:
    [Expert@HostName:0]# fw ctl debug -m fw
    Output should show debugging buffer size 32000KB and all the debugging options enabled in the previous step.
  3. Start the debug:
    [Expert@HostName:0]# fw ctl kdebug -T -f > /var/log/debug.txt
  4. Capture the involved traffic:
    Refer to sk30583 - What is FW Monitor?.
    It might also be required to capture the traffic with TCPdump.
  5. Replicate the issue:
    Make sure the issue was replicated.
    Collect all the relevant screenshots / logs that show the issue.
  6. Stop the debug:
    Press CTRL+C and run
    [Expert@HostName:0]# fw ctl debug 0
  7. Collect these files:
    • /var/log/debug.txt
    • /var/log/messages*
    • traffic capture(s)
    • CPinfo file from the involved Security Gateway(s) / Cluster members
    • CPinfo file from the involved Security Management Server / Domain Management Server

(V-4) Debug: HTTPS Inspection rulebase matching

Important Note: This kernel debug can cause very high load on Security Gateway's CPU. Schedule a maintenance window.
  1. Prepare the debug:
    [Expert@HostName:0]# fw ctl debug 0
    [Expert@HostName:0]# fw ctl debug -buf 32000
    [Expert@HostName:0]# fw ctl debug -m fw + conn drop
    [Expert@HostName:0]# fw ctl debug -m NRB all
    [Expert@HostName:0]# fw ctl debug -m WS + connection info module pkt_dump policy session spii ssl_insp vs
  2. Verify the debug:
    [Expert@HostName:0]# fw ctl debug -m fw
    [Expert@HostName:0]# fw ctl debug -m NRB
    [Expert@HostName:0]# fw ctl debug -m WS
    Output should show debugging buffer size 32000KB and all the debugging options enabled in the previous step.
  3. Start the debug:
    [Expert@HostName:0]# fw ctl kdebug -T -f > /var/log/debug.txt
  4. Capture the involved traffic:
    Refer to sk30583 - What is FW Monitor?.
    It might also be required to capture the traffic with TCPdump.
  5. Replicate the issue:
    Make sure the issue was replicated.
    Collect all the relevant screenshots / logs that show the issue.
  6. Stop the debug:
    Press CTRL+C and run
    [Expert@HostName:0]# fw ctl debug 0
  7. Collect these files:
    • /var/log/debug.txt
    • /var/log/messages*
    • traffic capture(s)
    • CPinfo file from the involved Security Gateway(s) / Cluster members
    • CPinfo file from the involved Security Management Server / Domain Management Server

  • Firewall Administration Guide (R75.20, R75.40, R75.40VS, R76, R77) - Chapter "Defining an Internet Access Policy" - "HTTPS Inspection"
  • Application Control and URL Filtering Administration Guide (R75.20, R75.40, R75.40VS, R76, R77) - Chapter "Managing Application Control and URL Filtering" - "HTTPS Inspection"
  • Data Loss Prevention Administration Guide (R75.20, R75.40, R75.40VS, R76, R77) - Chapter "Installation and Configuration" - "HTTPS Inspection"
  • IPS Administration Guide (R75.20, R75.40, R75.40VS, R76, R77) - Chapter "Monitoring Traffic" - "HTTPS Inspection"
  • Threat Prevention Administration Guide (R76, R77) - Chapter "Using Threat Prevention with HTTPS Traffic"
  • Anti-Bot and Anti-Virus Administration Guide (R75.40, R75.40VS) - Chapter "Managing Anti-Bot and Anti-Virus" - "HTTPS Inspection"

Note: These articles require "Advanced" access level or higer.

Using Threat Prevention with HTTPS Traffic

In This Section:
HTTPS Inspection
HTTP Inspection on Non-Standard Ports
You can use the HTTPS Inspection feature to unencrypt traffic and let Threat Prevention Software Blades give protections against advanced threats, bots, and other malware.

HTTPS Inspection

You can enable HTTPS traffic inspection on Security Gateways to inspect traffic that is encrypted by the Secure Sockets Layer (SSL) protocol. SSL secures communication between internet browser clients and web servers. It supplies data privacy and integrity by encrypting the traffic, based on standard encryption ciphers.
However, SSL has a potential security gap. It can hide illegal user activity and malicious traffic from the content inspection of Security Gateways. One example of a threat is when an employee uses HTTPS (SSL based) to connect from the corporate network to internet web servers. Security Gateways without HTTPS Inspection are unaware of the content passed through the SSL encrypted tunnel. This makes the company vulnerable to security attacks and sensitive data leakage.
The SSL protocol is widely implemented in public resources that include: banking, web mail, user forums, and corporate web resources.
There are two types of HTTPS inspection:
  • Inbound HTTPS inspection - To protect internal servers from malicious requests originating from the internet or an external network.
  • Outbound HTTPS inspection - To protect an organization from malicious traffic being sent by an internal client to a destination outside of the organization.
The Security Gateway acts as an intermediary between the client computer and the secure web site. The Security Gateway behaves as the client with the server and as the server with the client using certificates.
All data is kept private in HTTPS Inspection logs. This is controlled by administrator permissions. Only administrators with HTTPS Inspection permissions can see all the fields in a log. Without these permissions, some data is hidden.

How it Operates

In outbound HTTPS inspection, when a client in the organization initiates an HTTPS connection to a secure site, the Security Gateway:
  1. Intercepts the request.
  2. Establishes a secure connection to the requested web site and validates the site server certificate.
  3. Creates a new SSL certificate for the communication between the Security Gateway and the client, sends the client the new certificate and continues the SSL negotiation with it.
  4. Using the two SSL connections:
    1. It decrypts the encrypted data from the client.
    2. Inspects the clear text content for all blades set in the Policy.
    3. Encrypts the data again to keep client privacy as the data travels to the destination web server resource.
In inbound HTTPS inspection, when a client outside of the organization initiates an HTTPS connection to a server behind the organization's gateway, the Security Gateway:
  1. Intercepts the request.
  2. Uses the server's original certificate and private key to initiate an SSL connection with the client.
  3. Creates and establishes a new SSL connection with the web server.
  4. Using the two SSL connections:
    1. It decrypts the encrypted data from the client.
    2. Inspects the clear text content for all blades set in the policy.
    3. Encrypts the data again to keep client privacy as the data travels to the destination server behind the gateway.

Configuring Outbound HTTPS Inspection

To enable outbound HTTPS traffic inspection, you must do these steps:
  • Set the Security Gateway for HTTPS Inspection.
  • Generate a CA certificate on the Security Management Server or import a CA certificate already deployed in your organization.
    • If you created a CA certificate, you must deploy it in the Trusted Root Certification Authorities Certificate Store on the client computers. This lets the client computers trust all certificates signed by this certificate.
  • Generate an HTTPS inspection policy by defining relevant rules in the HTTPS inspection Rule Base.
  • Configure the conditions for dropping traffic from a web site server.
    When required, you can update the trusted CA list in the Security Gateway.

Enabling HTTPS Inspection

You must enable HTTPS inspection on each Security Gateway. From Security Gateway > HTTPS Inspection > Step 3, select Enable HTTPS Inspection.
The first time you enable HTTPS inspection on one of the Security Gateways, you must create an outbound CA certificate for HTTPS inspection or import a CA certificate already deployed in your organization. This outbound certificate is used by all Security Gateways managed on the Security Management Server.

Creating an Outbound CA Certificate

The outbound CA certificate is saved with a P12 file extension and uses a password to encrypt the private key of the file. The Security Gateways use this password to sign certificates for the sites accessed. You must keep the password as it also used by other Security Management Servers that import the CA certificate to decrypt the file.
After you create an outbound CA certificate, you must export it so it can be distributed to clients. If you do not deploy the generated outbound CA certificate on clients, users will receive SSL error messages in their browsers when connecting to HTTPS sites. You can configure a troubleshooting option that logs suchconnections.
After you create the outbound CA certificate, a certificate object named Outbound Certificate is created. Use this in rules that inspect outbound HTTPS traffic in the HTTPS inspection Rule Base.
To create an outbound CA certificate:
  1. In SmartDashboard, right-click the Security Gateway object and select Edit.
    The Gateway Properties window opens.
  2. In the navigation tree, select HTTPS Inspection.
  3. In the HTTPS Inspection page, click Create.
  4. Enter the necessary information:
    • Issued by (DN) - Enter the domain name of your organization.
    • Private key password - Enter the password that is used to encrypt the private key of the CA certificate.
    • Retype private key password - Retype the password.
    • Valid from - Select the date range for which the CA certificate is valid.
  5. Click OK.
  6. Export and deploy the CA certificate.

Exporting a Certificate from the Security Management Server

If you use more than one Security Management Server in your organization, you must first export the CA certificate using the export_https_cert CLI command from the Security Management Server on which it was created before you can import it to other Security Management Servers.
Command syntax:
export_https_cert [-local] | [-s server] [-f certificate file name under FWDIR/tmp][-help]
To export the CA certificate:
On the Security Management Server, run this command:
$FWDIR/bin/export_https_cert -local -f [certificate file name under FWDIR/tmp]
Example
$FWDIR/bin/export_https_cert -local -f mycompany.p12

Exporting and Deploying the Generated CA

To prevent users from getting warnings about the generated CA certificates that HTTPS inspection uses, install the generated CA certificate used by HTTPS inspection as a trusted CA. You can distribute the CA with different distribution mechanisms such as Windows GPO. This adds the generated CA to the trusted root certificates repository on client computers.
When users do standard updates, the generated CA will be in the CA list and they will not receive browser certificate warnings.
To distribute a certificate with a GPO:
  1. From the HTTPS Inspection window of the Security Gateway, click Export certificate.
    Or
    From the HTTPS Inspection > Gateways pane in a supported blade, click Export.
  2. Save the CA certificate file.
  3. Use the Group Policy Management Console to add the certificate to the Trusted Root Certification Authorities certificate store.
  4. Push the Policy to the client computers in the organization.
    Note - Make sure that the CA certificate is pushed to the client computer organizational unit.
  5. Test the distribution by browsing to an HTTPS site from one of the clients and verifying that the CA certificate shows the name you entered for the CA certificate that you created in the Issued by field.

Deploying Certificates by Using Group Policy

You can use this procedure to deploy a certificate to multiple client machines by using Active Directory Domain Services and a Group Policy object (GPO). A GPO can contain multiple configuration options, and is applied to all computers that are within the scope of the GPO.
Membership in the local Administrators group, or equivalent, is necessary to complete this procedure.
To deploy a certificate using Group Policy:
  1. Open the Group Policy Management Console.
  2. Find an existing GPO or create a new GPO to contain the certificate settings. Make sure the GPO is associated with the domain, site, or organization unit whose users you want affected by the policy.
  3. Right-click the GPO and select Edit.
    The Group Policy Management Editor opens and shows the current contents of the policy object.
  4. Open Computer Configuration > Policies > Windows Settings > Security Settings > Public Key Policies > Trusted Publishers.
  5. Click Action > Import.
  6. Do the instructions in the Certificate Import Wizard to find and import the certificate you exported from SmartDashboard.
  7. In the navigation pane, click Trusted Root Certification Authorities and repeat steps 5-6 to install a copy of the certificate to that store.

Importing an Outbound CA Certificate

You can import a CA certificate that is already deployed in your organization or import a CA certificate created on one Security Management Server to use on another Security Management Server.
Note - It is recommended that you use private CA Certificates.
For each Security Management Server that has Security Gateways enabled with HTTPS inspection, you must:
  • Import the CA certificate.
  • Enter the password the Security Management Server uses to decrypt the CA certificate file and sign the certificates for users. This password is only used when you import the certificate to a new Security Management Server.
To import a CA certificate:
  1. If the CA certificate was created on another Security Management Server, export the certificate from the Security Management Server on which it was created.
  2. In SmartDashboard, right-click a Security Gateway object, select Edit > HTTPS Inspection >Import
    Or
    From the HTTPS Inspection > Gateways pane of a supported blade, click the arrow next to Create Certificate and select Import certificate from file.
    The Import Outbound Certificate window opens.
  3. Browse to the certificate file.
  4. Enter the private key password.
  5. Click OK.
  6. If the CA certificate was created on another Security Management Server, deploy it to clients.

Configuring Inbound HTTPS Inspection

To enable inbound HTTPS traffic inspection:
  1. Set the Security Gateway for HTTPS Inspection. From Security Gateway > HTTPS Inspection >Step 3, select Enable HTTPS Inspection.
  2. Import server certificates for servers behind the organization Security Gateways.
  3. Generate an HTTPS inspection policy. Define relevant rules in the HTTPS inspection Rule Base.
  4. Configure the relevant server certificate in the HTTPS inspection Rule Base.

Server Certificates

When a client from outside the organization initiates an HTTPS connection to an internal server, the Security Gateway intercepts the traffic. The Security Gateway inspects the inbound traffic and creates a new HTTPS connection from the gateway to the internal server. To allow seamless HTTPS inspection, the Security Gateway must use the original server certificate and private key.
To enable inbound HTTPS inspection:
  1. Add the server certificates to the Security Gateway. This creates a server certificate object.
  2. Add the server certificate object to the Certificate column in the HTTPS Inspection Policy, to enforce it in rules.
The Server Certificates window in SmartDashboard has these options:
  • Add - Import a new server certificate. Enter a name for the server certificate, optional comment and import the P12 certificate file.
  • Delete - Delete a previously added server certificate. This option does not delete the server certificate option. It only removes it from the Server Certificate list.
  • Search - Enter a key word to search for a server certificate in the list.

Adding a Server Certificate

When you import a server certificate, enter the same password that was entered to protect the private key of the certificate on the server. The Security Gateway uses this certificate and the private key for SSL connections to the internal servers.
After you import a server certificate (with a P12 file extension) to the Security Gateway, make sure you add the object to the HTTPS Inspection Policy.
Do this procedure for all servers that receive connection requests from clients outside of the organization.
To add a server certificate:
  1. In SmartDashboard, open HTTPS Inspection > Server Certificates.
  2. Click Add.
    The Import Certificate window opens.
  3. Enter a Certificate name and a Description (optional).
  4. Browse to the certificate file.
  5. Enter the Private key password.
  6. Click OK.
The Successful Import window opens the first time you import a server certificate. It shows you where to add the object in the HTTPS Inspection Rule Base. Click Don't show this again if you do not want to see the window each time you import a server certificate and Close.

The HTTPS Inspection Policy

The HTTPS inspection policy determines which traffic is inspected. The primary component of the policy is the Rule Base. The rules use the categories defined in the Application Database, network objects and custom objects (if defined).
The HTTPS Rule Base lets you inspect the traffic on other network blades. The blades that HTTPS can operate on are based on the blade contracts and licenses in your organization and can include:
  • Application Control
  • URL Filtering
  • IPS
  • DLP
  • Threat Prevention
If you enable Identity Awareness on your Security Gateways, you can also use Access Role objects as the source in a rule. This lets you easily make rules for individuals or different groups of users.
To access the HTTPS inspection Rule Base:
In SmartDashboard, open the Policy page from the specified blade tab:
  • For Application Control and URL Filtering, Anti-Bot, Anti-Virus, and IPS - Select Advanced > HTTPS Inspection > Policy.
  • For DLP - Select Additional Settings > HTTPS Inspection > Policy.

Predefined Rule

When you enable HTTPS inspection, a predefined rule is added to the HTTPS Rule Base. This rule defines that all HTTPS and HTTPS proxy traffic from any source to the internet is inspected on all blades enabled in the Blade column. By default, there are no logs.

Parts of the Rule

The columns of a rule define the traffic that it matches and if that traffic is inspected or bypassed. When traffic is bypassed or if there is no rule match, the traffic continues to be examined by other blades in the Security Gateway.
Number (No.)
The sequence of rules is important because the first rule that matches is applied.
For example, if the predefined rule inspects all HTTPS traffic from any category and the next rule bypasses traffic from a specified category, the first rule that inspects the traffic is applied.
Name
Give the rule a descriptive name. The name can include spaces.
Double-click in the Name column of the rule to add or change a name.
Source
The source is where the traffic originates. The default is Any.
Important - A rule that blocks traffic, with the Source and Destination parameters defined asAny, also blocks traffic to and from the Captive Portal.
Put your mouse in the column and a plus sign shows. Click the plus sign to open the list of network objects and select one or multiple sources. The source can be an Access Role object, which you can define when Identity Awareness is enabled.
Destination
Choose the destination for the traffic. The default is the Internet, which includes all traffic with the destination of DMZ or external. If you delete the destination value, the rule changes to Any, which applies to traffic going to all destinations
Important - A rule that blocks traffic, with the Source and Destination parameters defined asAny, also blocks traffic to and from the Captive Portal.
To choose other destinations, put your mouse in the column and a plus sign shows. Click the plus sign to open the list of network objects and select one or multiple destinations.
Services
By default, HTTPS traffic on port 443 and HTTP and HTTPS proxy on port 8080 is inspected. You can include more services and ports in the inspection by adding them to the services list.
To select other HTTPS/HTTP services, put your mouse in the column and a plus sign shows. Click the plus sign to open the list of services and select a service. Other services, such as SSH are not supported.
Site Category
The Site Category column contains the categories for sites and applications that users browse to and you choose to include. One rule can include multiple categories of different types.
Important -
  • A valid URL Filtering blade contract and license are necessary on the relevant Security Gateways to use the Site Category column.
  • To perform categorization correctly, a single connection to a site must be inspected in some cases regardless of the HTTPS inspection policy. This maps the IP address of a site to the relevant domain name.
You can also include custom applications, sites, and hosts. You can select a custom defined application or site object with the Custom button or create a new host or site with the New button at the bottom of the page.
To add site categories to a rule:
Put your mouse in the column and a plus sign shows. Click the plus sign to open the Category viewer. For each category, the viewer shows a description and if there are applications or sites related with it.
  • To filter the Available list by categories or custom-defined sites, click the specified button in the toolbar of the viewer. The Available list opens in the left column and then you can add items to the rule.
  • To add a category object to the rule, click the checkbox in the Available list.
  • To see the details of category without adding it to the rule, click the name of the item in the Available list.
  • You can only select a category to add to the rule from the Available list.
  • If a category is already in a rule, it will not show in the Category viewer.
  • If you know the name of a category, you can search for it. The results will show in the Available list.
  • You can add a new host site with the New button.
Adding a New Host Site
You can create a new host site object to use in the HTTPS Rule Base if there is no corresponding existing category. Only the domain name part or hosts part of the URL is supported.
To create a new host site:
  1. Click the plus icon in the Site Category column.
  2. In the Category viewer, select New.
    The Hosts/Sites window opens.
  3. Enter a name for the host site.
  4. Set a color for the host site icon (optional).
  5. Enter a comment for the host site (optional).
  6. In Hosts List, enter a valid URL and click Add.
  7. If you used a regular expression in the URL, click Hosts are defined as regular expressions.
  8. Click OK.
    The new host site is added to the Selected list and can be added to the Rule Base.
Action
The action is what is done to the traffic. Click in the column to see the options and select one to add to the rule.
  • Inspect - The traffic is inspected on the blades set in the Blades column.
  • Bypass - The traffic of source and destination traffic in rules that include the bypass action are not decrypted and inspected. You can bypass HTTPS inspection for all Check Point objects. This is recommended for Anti-Bot, Anti-Virus, URL Filtering, and IPS updates. Other HTTPS protections that already operate on traffic will continue to work even when the HTTPS traffic is not decrypted for inspection.
Track
Choose if the traffic is logged in SmartView Tracker or if it triggers other notifications. Click in the column and the options open. The options include:
  • None - Does not record the event
  • Log - Records the event details in SmartView Tracker. This option is useful for obtaining general information on your network traffic. There is one or more log for each session depending on the suppression option.
  • Alert - Logs the event and executes a command, such as display a popup window, send an email alert or an SNMP trap alert, or run a user-defined script as defined in Policy > Global Properties >Log and Alert > Alert Commands
  • Mail - Sends an email to the administrator, or runs the mail alert script defined in Policy > Global Properties > Log and Alert > Alert Commands
  • SNMP Trap - Sends a SNMP alert to the SNMP GUI, or runs the script defined in Policy > Global Properties > Log and Alert > Alert Commands
  • User Defined Alert - Sends one of three possible customized alerts. The alerts are defined by the scripts specified in Policy > Global Properties > Log and Alert > Alert Commands
Blade
Choose the blades that will inspect the traffic. Click in the column and the options open. The options include:
  • Anti-Bot
  • Anti-Virus
  • Application Control
  • Data Loss Prevention
  • IPS
  • URL Filtering
Important - The blade options you see are based on the blade contracts and licenses in your organization.
Install On
Choose which Security Gateways the rule will be installed on. The default is All, which means all Security Gateways that have HTTPS inspection enabled. Put your mouse in the column and a plus sign shows. Click the plus sign to open the list of available Security Gateways and select.
Certificate
Choose the certificate that is applicable to the rule. The Security Gateway uses the selected certificate for communication between the Security Gateway and the client.
  • For outbound HTTPS inspection - choose the Outbound Certificate object (default) that reflects the CA certificate you created/imported and deployed on the client machines in your organization.
  • For inbound HTTPS inspection - choose the server certificate applicable to the rule. Put your mouse in the column and a plus sign shows. Click the plus sign to open the list of available server certificates and select one. When there is a match to a rule, the Security Gateway uses the selected server certificate to communicate with the source client. You can create server certificates fromHTTPS Inspection > Server Certificates > Add.

Bypassing HTTPS Inspection for Software Update Services

Check Point dynamically updates a list of approved domain names of services from which content is always allowed. This option makes sure that Check Point updates or other 3rd party software updates are not blocked. For example, updates from Microsoft, Java, and Adobe.
To bypass HTTPS inspection for software updates:
  1. In the HTTPS Inspection > Policy pane, select Bypass HTTPS Inspection of traffic to well know software update services (list is dynamically updated). This option is selected by default.
  2. Click list to see the list of approved domain names.

Enhanced HTTPS Inspection Bypass

Enhanced HTTPS Inspection Bypass lets the gateway bypass traffic to servers that require client certificate authentication and bypass non-browser applications.
This feature is supported on R77.30 and higher gateways.
To enable enhanced HTTPS inspection:
  1. In the $FWDIR/boot/modules/fwkern.conf file on the gateway, add:
    enhanced_ssl_inspection=1
  2. Reboot.
You can configure this feature without changing the configuration file, but it does not survive reboot:
In expert mode, run: fw ctl set int enhanced_ssl_inspection 1

Gateways Pane

The Gateways pane lists the gateways with HTTPS Inspection enabled. Select a gateway and click Edit to edit the gateway properties. You can also search, add and remove Security Gateways from here.
For each gateway, you see the gateway name, IP address and comments.
In the CA Certificate section, you can renew the certificate validity date range if necessary and export it for distribution to the organization client machines.
If the Security Management Server managing the selected Security Gateway does not have a generated CA certificate installed on it, you can add it with Import certificate from file.
  • You can import a CA certificate already deployed in your organization.
  • You can import a CA certificate from another Security Management Server. Before you can import it, you must first export it from the Security Management Server on which it was created.

Adding Trusted CAs for Outbound HTTPS Inspection

When a client initiates an HTTPS connection to a web site server, the Security Gateway intercepts the connection. The Security Gateway inspects the traffic and creates a new HTTPS connection from the Security Gateway to the designated server.
When the Security Gateway establishes a secure connection (an SSL tunnel) to the designated web site, it must validate the site server certificate.
HTTPS Inspection comes with a preconfigured list of trusted CAs. This list is updated by Check Point when necessary and is automatically downloaded to the Security Gateway. The system is configured by default to notify you when a Trusted CA update file is ready to be installed. The notification in SmartDashboard shows as a pop-up notification or in the Trusted CAs window in the Automatic Updates section. After you install the update, make sure to install the policy. You can choose to disable the automatic update option and manually update the Trusted CA list.
If the Security Gateway receives a non-trusted server certificate from a site, by default the user gets a self-signed certificate and not the generated certificate. A page notifies the user that there is a problem with the website security certificate, but lets the user continue to the website.
You can change the default setting to block untrusted server certificates.
The trusted CA list is based on the Microsoft Root Certificate Program.

Automatically Updating the Trusted CA List and Certificate Blacklist

Updates for the trusted CA list and Certificate Blacklist will be published from time to time on the Check Point web site. They are automatically downloaded to the Security Management Server by default. When you are sent a notification that there is an update available, install it and do the procedure. The first notification is shown in a popup balloon once and then in the notification line under HTTPS Inspection >Trusted CAs. You can disable automatic updates if necessary.
To update the Trusted CA list and Certificate Blacklist:
  1. In SmartDashboard, select HTTPS Inspection > Trusted CAs.
  2. In the Automatic Updates section, click Install Now.
    You see the certificates that will be added or removed to the lists and the validity date range of the certificates added to the Trusted CA list.
  3. Click Proceed to confirm the update.
    The certificates will be added or removed respectively from the lists.
  4. Install the Policy.
To disable automatic updates:
  1. In SmartDashboard, select HTTPS Inspection > Trusted CAs.
  2. In the Automatic Updates section, clear the Notify when a Trusted CA and Blacklist update file is available for installation checkbox.

Manually Updating a Trusted CA

To add a trusted CA manually to the Security Gateway, you must export the necessary certificate from a non-trusted web site and then import it into SmartDashboard.
To export a CA certificate to add to the Trusted CAs list:
  1. Temporarily disable HTTPS inspection on the Security Gateway.
  2. Install the security policy.
  3. Browse to the site to get the certificate issued by the CA.
  4. Go to the Certification Path of the certificate.
  5. Select the root certificate (the top most certificate in the list).
  6. In Internet Explorer and Chrome:
    1. Click View Certificate.
    2. From the Details tab, click Copy to File.
    3. Follow the wizard steps.
  7. In Firefox, export the certificate.
To import a CA certificate to the Trusted CAs list:
  1. In SmartDashboard, open HTTPS Inspection > Trusted CAs.
  2. Click Actions > Import certificate, browse to the location of the saved certificate and click Open.
    The certificate is added to the trusted CAs list.
  3. Install the security policy on Security Gateways enabled with HTTPS Inspection.

Saving a CA Certificate

You can save a selected certificate in the trusted CAs list to the local file system.
To export a CA certificate:
  1. In SmartDashboard, open HTTPS Inspection > Trusted CAs.
  2. Click Actions > Export to file.
  3. Browse to a location, enter a file name and click Save.
    A CER file is created.

HTTPS Validation

Server Validation

When a Security Gateway receives an untrusted certificate from a web site server, the settings in this section define when to drop the connection.
Untrusted server certificate
When selected, traffic from a site with an untrusted server certificate is immediately dropped. The user gets an error page that states that the browser cannot display the webpage.
When cleared, a self-signed certificate shows on the client machine when there is traffic from an untrusted server. The user is notified that there is a problem with the website's security certificate, but lets the user continue to the website (default).
Revoked server certificate (validate CRL)
When selected, the Security Gateway validates that each server site certificate is not in the Certificate Revocation List (CRL) (default).
If the CRL cannot be reached, the certificate is considered trusted (this is the default configuration). An HTTPS Inspection log is issued that indicates that the CRL could not be reached. This setting can be changed with GuiDBedit. Select Other > SSL Inspection > general_confs_obj and change the attributedrop_if_crl_cannot_be_reached from false to true.
To validate the CRL, the Security Gateway must have access to the internet. For example, if a proxy server is used in the organizational environment, you must configure the proxy for the Security Gateway.
To configure the proxy:
  1. From the Firewall tab, double-click the Security Gateway that requires proxy configuration.
  2. Select Topology > Proxy.
  3. Select Use custom proxy settings for this network object and Use proxy server and enter the proxy IP address.
  4. Optionally, you can use the default proxy settings.
  5. Click OK.
When cleared, the Security Gateway does not check for revocations of server site certificates.
Important - Make sure that there is a rule in the Rule Base that allows outgoing HTTP from the Security Gateway.
Expired server certificate
  • When selected, the Security Gateway drops the connection if the server certificate has expired.
  • When cleared, the Security Gateway creates a certificate with the expired date. The user can continue to the website (default).
Track validation errors
Choose if the server validation traffic is logged in SmartView Tracker or if it triggers other notifications. The options include:
  • None - Does not record the event.
  • Log - Records the event details in SmartView Tracker
  • Alert - Logs the event and executes a command, such as shows a popup window, send an email alert or an SNMP trap alert, or run a user-defined script as defined in Policy > Global Properties > Log and Alert > Alert Commands
  • Mail - Sends an email to the administrator, or runs the mail alert script defined in Policy > Global Properties > Log and Alert > Alert Commands
  • SNMP Trap - Sends an SNMP alert to the SNMP GUI, or runs the script defined in Policy > Global Properties > Log and Alert > Alert Commands
  • User Defined Alert - Sends one of three possible customized alerts. The alerts are defined by the scripts specified in Policy > Global Properties > Log and Alert > Alert Commands
Automatically retrieve intermediate CA certificates
  • When selected, intermediate CA certificates issued by trusted root CA certificates that are not part of the certificate chain are automatically retrieved using the information on the certificate (default).
  • When cleared, a web server certificate signed by an intermediate CA and not sent as part of the certificate chain, is considered untrusted.

Certificate Blacklisting

You can create a list of certificates that are blocked. Traffic from servers using the certificates in the blacklist will be dropped. If a certificate in the blacklist is also in the Trusted CAs list, the blacklist setting overrides the Trusted CAs list.
  • Add - Lets you add a certificate. Enter the certificate serial number (in hexadecimal format HH:HH) and a comment that describes the certificate.
  • Edit - Lets you change a certificate in the blacklist.
  • Remove - lets you delete a certificate in the blacklist.
  • Search - Lets you search for a certificate in the blacklist.
  • Track dropped traffic
Choose if the dropped traffic is logged in SmartView Tracker or if it triggers other notifications. The options include:
  • None - Does not record the event.
  • Log - Records the event details in SmartView Tracker
  • Alert - Logs the event and executes a command, such as shows a popup window, send an email alert or an SNMP trap alert, or run a user-defined script as defined in Policy > Global Properties > Log and Alert > Alert Commands
  • Mail - Sends an email to the administrator, or runs the mail alert script defined in Policy > Global Properties > Log and Alert > Alert Commands
  • SNMP Trap - Sends an SNMP alert to the SNMP GUI, or runs the script defined in Policy > Global Properties > Log and Alert > Alert Commands
  • User Defined Alert - Sends one of three possible customized alerts. The alerts are defined by the scripts specified in Policy > Global Properties > Log and Alert > Alert Commands

Troubleshooting

Secure connections between a client and server with no traffic create logs in SmartView Tracker labeled as "Client has not installed CA certificate". This can happen when an application or client browser fails to validate the server certificate. Possible reasons include:
  • The generated CA was not deployed on clients.
  • The DN in the certificate does not match the actual URL (for example, when you browse to https://www.gmail.com, the DN in the certificate states mail.google.com).
  • Applications (such as Firefox and anti-viruses) that use an internal trusted CA list (other than Windows). Adding the CA certificate to the Windows repository does not solve the problem.
The option in the HTTPS Validation pane:
Log connections of clients that have not installed the CA certificate
  • When selected, logs are recorded for secure connections between a client and server with no traffic in SmartView Tracker (default). Logs are recorded only when a server certificate is trusted by the Security Gateway. If the server certificate is untrusted, a self-signed certificate is created and always results in a log labeled as "Client has not installed CA certificate".
  • When cleared, logs are not recorded for secure connections without traffic that can be caused by not installing the CA certificate on clients or one of the above mentioned reasons.

HTTP/HTTPS Proxy

You can configure a gateway to be an HTTP/HTTPS proxy. When it is a proxy, the gateway becomes an intermediary between two hosts that communicate with each other. It does not allow a direct connection between the two hosts.
Each successful connection creates two different connections:
  • One connection between the client in the organization and the proxy.
  • One connection between the proxy and the actual destination.
Proxy Modes
Two proxy modes are supported:
  • Transparent - All HTTP traffic on specified ports and interfaces is intercepted and sent to a proxy. No configuration is required on the clients.
  • Non Transparent - All HTTP/HTTPS traffic on specified ports and interfaces directed to the gateway is sent to a proxy. Configuration of the proxy address and port is required on client machines.
Access Control
You can configure one of these options for forwarding HTTP requests:
  • All Internal Interfaces - HTTP/HTTPS traffic from all internal interfaces is forwarded by proxy.
  • Specific Interfaces - HTTP/HTTPS traffic from interfaces specified in the list is forwarded by proxy.
Ports
By default, traffic is forwarded only on port 8080. You can add or edit ports as required.
Advanced
By default, the HTTP header contains the Via proxy related header. You can remove this header with theAdvanced option.
You can also use the Advanced option to configure the X-Forward-For header that contains the IP address of the client machine. It is not added by default because it reveals the internal client IP.
Logging
The Security Gateway opens two connections, but only the Firewall blade can log both connections. Other blades show only the connection between the client and the gateway. The Destination field of the log only shows the gateway and not the actual destination server. The Resource field shows the actual destination.
To configure a Security Gateway to be an HTTP/HTTPS proxy:
  1. From the General Properties window of a Security Gateway object, select HTTP/HTTPS Proxyfrom the tree.
  2. Select Use this gateway as a HTTP/HTTPS Proxy.
  3. Select the Transparent or Non Transparent proxy mode.
    Note - If you select Non Transparent mode, make sure to configure the clients to work with the proxy.
  4. Select to forward HTTP requests from one of these options:
    • All Internal Interfaces
    • Specific Interfaces - Click the plus sign to add specified interfaces or the minus sign to remove an interface.
  5. To enter more ports on which to forward traffic, select Add.
  6. To include the actual source IP address in the HTTP header, select Advanced > X-Forward-For header (original client source IP address).
    The X-Forward-For header must be configured if traffic will be forwarded to Identity Awareness Security Gateways that require this information for user identification.
  7. Click OK.

Security Gateway Portals

The Security Gateway runs a number of web-based portals over HTTPS:
  • Mobile web access portal
  • SecurePlatform WebUI
  • Gaia WebUI
  • Identity Awareness (Captive Portal)
  • DLP portal
  • SSL Network Extender portal
  • UserCheck portal
  • Endpoint Security portals (CCC)
All of these portals can resolve HTTPS hosts to IPv4 and IPv6 addresses over port 443.
These portals (and HTTPS inspection) support the latest versions of the TLS protocol. In addition to SSLv3 and TLS 1.0 (RFC 2246), the Security Gateway supports:
  • TLS 1.1 (RFC 4346)
  • TLS 1.2 (RFC 5246)
Support for TLS 1.1 and TLS 1.2 is enabled by default but can be disabled in SmartDashboard (for web-based portals) or GuiDBedit (for HTTPS Inspection).
To configure TLS protocol support for portals:
  1. In SmartDashboard, open Global Properties > SmartDashboard Customization.
  2. In the Advanced Configuration section, click Configure.
    The Advanced Configuration window opens.
  3. On the Portal Properties page, set minimum and maximum versions for SSL and TLS protocols.
To Configure TLS Protocol Support for HTTPS inspection:
  1. In GuiDBedit, on the Tables tab, select Other > ssl_inspection.
  2. In the Objects column, select general_confs_obj.
  3. In the Fields column, select the minimum and maximum TLS version values in these fields:
    • ssl_max_ver (default = TLS 1.2)
    • ssl_min_ver (default = SSLv3)

HTTPS Inspection in SmartView Tracker

Logs from HTTPS Inspection are shown in SmartView Tracker. There are two types of predefined queries for HTTPS Inspection logs in SmartView Tracker:
  • HTTPS Inspection queries
  • Blade queries - HTTPS Inspection can be applied to these blades:
    • Application Control
    • URL Filtering
    • IPS
    • DLP
    • Anti-Virus
    • Anti-Bot
To open SmartView Tracker:
  • From the SmartDashboard toolbar, click SmartConsole> SmartView Tracker.
  • With SmartDashboard active, press Control +Shift +T.

HTTPS Inspection Queries

These are the predefined queries in Predefined > Network Security Blades > HTTPS Inspection.
  • All - Shows all HTTPS traffic that matched the HTTPS Inspection policy and was configured to be logged.
  • HTTPS Validations - Shows traffic with connection problems. The Action values are rejected ordetected. The actions are determined by the SSL validation settings for HTTPS Inspection.
    HTTPS Validation values are:
    • Untrusted Server Certificate
    • Server Certificate Expired
    • Revoked Certificate or Invalid CRL
    • SSL Protocol Error (general SSL protocol problems)

Blade Queries

When applying HTTPS Inspection to a specified blade:
  • There is an HTTPS Inspection predefined query for each of the blades that can operate with HTTPS Inspection. The query shows all traffic of the specified blade that passed through HTTPS inspection.
  • The log in the blade queries includes an HTTP Inspection field. The field value can be inspect or bypass. If the traffic did not go through HTTPS inspection, the field does not show in the log.

Permissions for HTTPS Logs

An administrator must have HTTPS inspection permissions to see classified data in HTTPS inspected traffic.
To set permissions for an administrator in a new profile:
  1. In the Users and Administrators tree, select an administrator > Edit.
  2. In the Administrator Properties > General Properties page in the Permissions Profile field, click New.
  3. In the Permissions Profile Properties window:
    • Enter a Name for the profile.
    • Select Customized and click Edit.
    The Permissions Profile Custom Properties window opens.
  4. In the Monitoring and Logging tab, select HTTPS Inspection logs for permission to see the classified information in the HTTPS Inspection logs.
  5. Click OK on all of the open windows.
To edit an existing permissions profile:
  1. From the SmartDashboard toolbar, select Manage > Permissions Profiles.
  2. Select a profile and click Edit.
  3. Follow the instructions above from step 3.

HTTPS Inspection in SmartEvent

Events from HTTPS Inspection are shown in SmartEvent. There are two types of predefined queries for HTTPS Inspection events in SmartEvent:
  • HTTPS Inspection queries for HTTPS validations
  • Blade queries - HTTPS Inspection can be applied to these blades:
    • Application Control
    • URL Filtering
    • IPS
    • DLP
    • Anti-Virus
To open SmartEvent:
  • From the SmartDashboard toolbar, click SmartConsole > SmartEvent.
  • With SmartDashboard active, press Control +Shift +A.

Event Analysis in SmartEvent

SmartEvent supplies advanced analysis tools with filtering, charts, reporting, statistics, and more, of all events that pass through enabled Security Gateways. SmartEvent shows all HTTPS Inspection events.
You can filter the HTTPS Inspection information for fast monitoring on HTTPS Inspection traffic.
  • Real-time and history graphs of HTTPS Inspection traffic.
  • Graphical incident timelines for fast data retrieval.
  • Easily configured custom views to quickly view specified queries.
  • Incident management workflow.
SmartEvent shows information for all Software Blades in the environment.

Viewing Information in SmartEvent

There are two types of predefined queries for HTTPS Inspection events in SmartEvent:
  • HTTPS Inspection queries
  • Blade queries
HTTPS Inspection Queries
  • Go to Events > Predefined > HTTPS Inspection > HTTPS Validation to show the SSL validation events that occurred.
  • The Details and Summary tabs in the event record show if the traffic was detected or rejected due to SSL Validation settings.
Blade Queries
  • There is an HTTPS Inspection predefined query for each of the blades that can operate with HTTPS Inspection. The query shows all traffic of the specified blade that passed through HTTPS inspection.
  • The Summary tab in the event record in the blade queries includes an HTTPS Inspection field. The field value can be inspect or bypass. If the traffic did not go through HTTPS inspection, the field does not show in the event record.

HTTP Inspection on Non-Standard Ports

Applications that use HTTP normally send the HTTP traffic on TCP port 80. Some applications send HTTP traffic on other ports also. You can configure some Software Blades to only inspect HTTP traffic on port 80, or to also inspect HTTP traffic on non-standard ports.

When selected, the Anti-Bot and Anti-Virus policy inspects all HTTP traffic, even if it is sent using nonstandard ports. This option is selected by default. You can configure this option in the Threat Prevention tab > Advanced pane.




(VIII) Revision history

DateDescription
31 Jan 2016
  • "Best Practices" section - "(II-1) - B) CA creation/import" - added relevant steps for best practice, fastest deployment, and best security
10 Dec 2015
  • "Related solutions" section - added related solutions
18 Nov 2015
  • "Performance" section - added related solution (for Check Point Partners)
13 Nov 2015
  • "Related solutions" section - added related solutions
12 Nov 2015
  • First release of this article
Give us Feedback
Please rate this document
[1=Worst,5=Best]
Comment 
Posted by at