Configuring ICAP Client in Gateway mode

Important - In a ClusterClosed Two or more Security Gateways that work together in a redundant configuration - High Availability, or Load Sharing., you must configure all the Cluster Members in the same way.

Procedure:

  1. Connect to the command line on the Security GatewayClosed Dedicated Check Point server that runs Check Point software to inspect traffic and enforce Security Policies for connected network resources..

  2. Log in to the Expert mode.

  3. Follow the instructions in the ICAP user-disclaimer:

    [Expert@GW:0]# IcapDisclaimer.sh

    If you agreed to the ICAP user-disclaimer, continue to the next step.

  4. Backup the default ICAP ClientClosed The ICAP Client functionality in your Security Gateway or Cluster (in versions R80.40 and higher) enables it to interact with an ICAP Server responses (see RFC 3507), modify their content, and block the matched HTTP connections. configuration file:

    cp -v $FWDIR/conf/icap_client_blade_configuration.C{,_BKP}

  5. Configure the ICAP Client parameters:

    vi $FWDIR/conf/icap_client_blade_configuration.C

    For details, see these sections:

  6. Save the changes in the file and exit the editor.

  7. To inspect the HTTPS traffic with the ICAP Client, you must:

    1. Enable the HTTPS InspectionClosed Feature on a Security Gateway that inspects traffic encrypted by the Secure Sockets Layer (SSL) protocol for malware or suspicious patterns. Synonym: SSL Inspection. Acronyms: HTTPSI, HTTPSi. in the Security Gateway object.

    2. Configure the HTTPS Inspection Rule BaseClosed All rules configured in a given Security Policy. Synonym: Rulebase..

    For details, see HTTPS Inspection.

  8. Install the Access Control Policy on the Security Gateway:

    Note - If one of the ICAP configuration parameters is not configured correctly, SmartConsole shows an error with the name of the applicable parameter.