Product Limitations

Automatic Enablement of Anti-Bot Anti-Virus and Threat Emulation Blades

Zero Phishing

Policy Installation

  • In the first installation, you cannot install both the Access Control and Threat Prevention policies on the same gateway at the same time. You must install one and then the other.

Anti-Virus

IPS

  • Check Point does not support JA3 and JA4 profiling technologies.

Malware Prevention using IP and Port Indicators

  • Malware Prevention using IP and Port Indicators supports only IPv4 traffic.

  • Malware Prevention using IP and Port Indicators is disabled when the Security Gateway is not connected to the Internet.

Threat Emulation

  • Not defining the topology in the Security Gateway object may cause:

    • Internal files sent to the cloud (potential privacy concern).

    • ThreatCloud quota overuse.

    • Impact on performance, because more files are emulated than necessary.

  • Multiple file execution is not supported with executable files, or CPU-Level images.

  • Running a local Threat Emulation appliance as a StandAlone (both a Security Management Server and Security Gateway are installed on the same device) is not supported.

  • If the Anti-Virus blade is also enabled, there is an expected degradation in Threat Emulation performance of approximately 5-10%.

  • VSX and VSNext do not support local emulation.

  • VSNext does not support Threat Emulation archive scanning.

  • VSNext does not support using a Mail Transfer AgentClosed Feature on a Check Point Firewall that intercepts SMTP traffic and forwards it to the applicable inspection component. Acronym: MTA. for Threat Emulation.

  • Spark Firewall appliances and Threat Emulation appliances do not support Autonomous Threat Prevention.

Threat Extraction

  • Threat ExtractionClosed Software Blade on a Check Point Firewall that removes malicious content from files. Acronym: TEX. web support applies to web downloads, but not web uploads.

  • Supported file types for web are: Word, Excel, PowerPoint and PDF.

  • Threat Extraction supports these file types and extraction methods:

    Format

    Extensions

    Mail / Web / Both

    Supported Extraction Methods

    Adobe FDF

    fdf

    Both

    Extract/Convert to PDF

    Adobe PDF (all versions)

    pdf

    Both

    Extract/Convert to PDF

    Microsoft Docfile

    Microsoft Visio, Microsoft Project, and so on

    Mail

    Extract/Convert to PDF

    Microsoft Excel 2007 and above

    xlsx, xlsb, xlsm, xltx, xltm, xlam

    Both

    Extract/Convert to PDF

    Microsoft Excel 2007 Binary

    xlsb

    Both

    Extract/Convert to PDF

    Microsoft Excel 97 - 2003

    xls

    Both

    Extract/Convert to PDF

    Microsoft PowerPoint 2007 and above

    pptx, pptm, potx, potm, ppam, ppsx, ppsm

    Both

    Extract/Convert to PDF

    Microsoft PowerPoint 97 - 2003

    ppt, pps, pot, ppa

    Both

    Extract/Convert to PDF

    Microsoft Word 2007 and above

    docx, docm, dotx, dotm

    Both

    Extract/Convert to PDF

    Microsoft Word 97 - 2003

    doc, dot

    Both

    Extract/Convert to PDF

    Rich Text Format

    rtf

    Both

    Extract/Convert to PDF

    Compressed graphic Format JPEG

    jpeg,jpg,jpe,jfif

    Mail

    Extract/Convert to PDF

    Multi Picture Format File

    mpo

    Mail

    Convert to PDF

    Ichitaro word proccessing application

    jtd

    Mail

    Convert to PDF

    Hanword

    hwp

    Mail

    Convert to PDF

    Graphics interchange Format

    gif

    Mail

    Extract/Convert to PDF

    Tagged Image File Format

    tif,tiff

    Mail

    Extract/Convert to PDF

    Portable Network Graphics

    png

    Mail

    Extract/Convert to PDF

    Bitmap image file

    bmp

    Mail

    Extract/Convert to PDF

    Device independent Bitmap file

    dib

    Mail

    Convert to PDF

    Encapsulated Postscript file

    eps

    Mail

    Convert to PDF

    adobe Photoshop Document

    psd

    Mail

    Convert to PDF

    Targa Graphic

    tga

    Mail

    Convert to PDF

    Paintbrush bitmap image file

    pcx

    Mail

    Convert to PDF

    DICOM image

    dcm

    Mail

    Convert to PDF

    JavaScript File

    js

    Mail

    Convert to PDF

    Extensible Markup Language

    xml

    Mail

    Convert to PDF

    Plain Text file

    txt

    Mail

    Convert to PDF

    Hypertext Markup Language

    html

    Mail

    Convert to PDF

  • In a cluster, Threat Extraction is only supported in High Availability mode.

Traditional Anti-Virus

VSX and VSNext do not support Traditional Anti-Virus.

Anti-Spam

Autonomous Threat Prevention

  • Spark Firewall appliances and Threat Emulation appliances do not support Autonomous Threat Prevention.

  • Autonomous Threat Prevention does not support MTA. To manage a Security Gateway as an MTA, use Custom Threat Prevention.

  • The Global Domain does not support Autonomous Threat Prevention. Other Domains support it.

MTA

ICAP

  • ICAP is not supported in Autonomous Threat Prevention, it is supported only in Custom Threat Prevention mode.

ICAP Client

ICAP Server

  • ICAP Server supports Anti-Virus deep-scan, but does not support any additional functionality, such as MD5 hash, URL reputation, and signature-based protection

  • ICAP Server functionality is not supported in ClusterXL Load Sharing mode

  • ICAP Client does not support ClusterXLLoad Sharing mode.

  • You cannot create exceptions for an ICAP rule.

  • Traditional VSX does not support ICAP Server..

  • Scalable Platforms do not support ICAP Server.

  • When using ICAP Server,in Threat Emulation > General > Protected Scope, Threat Emulation scans all files, regardless of the option you select.

SSH DPI

SSH Deep Inspection supports only these blades:

UserCheck

When processing a file over HTTP, UserCheck cannot send messages to the browser after the download started:

  • For newly identified malicious files, the UserCheck Agent is required to display the UserCheck notification.

  • For files already known to be malicious by Threat Emulation, the UserCheck messages can be displayed in the browser.

The SMTP protocol does not provide a user interface for displaying UserCheck messages:

  • For the Anti-Virus, IPS and Threat Emulation blades - The UserCheck agent is supported only when a client uses SMTP to send an email through the SMTP server.

  • Sending UserCheck notifications through email is not supported for Anti-Virus, IPS and Threat Emulation.

  • For the Threat Emulation and Anti-Virus blades - To provide user-friendly notifications over email, configure the Security Gateway as a Mail Transfer Agent - When a malicious attachment is detected, it is replaced with a text file.

Monitoring Threat Prevention

The number of packet captures that the Security Gateway can send to the Log ServerClosed Dedicated Check Point server that runs Check Point software to store and process logs. does not exceed 25 per second.

HTTPS Inspection

  • CRL validation is not supported in pure IPv6 environments (when IPv4 addresses are not configured on the Security Gateway's interfaces).

  • In the HTTPS Inspection policy, when selecting the same action that already appears in the Action column, the Security Management Server records it as a change within the SmartConsole session.

    • The Security Gateways supports HTTP/3 inspection only when it runs in the User Space Firewall (USFW) mode, which is the default in versions R82 and higher.

    • The Security Gateway downgrades HTTP/3 traffic to an earlier HTTP version when it operates in the kernel mode firewall.

      For information about the User Space Firewall (USFW) mode, see the Release Notes for your version and sk167052.

    • The Security Gateway drops HTTP/3 traffic when the Threat Prevention "Deep Inspection" mode is enabled.

    • Chromium-based web browsers allow HTTP/3 traffic only if the HTTPS Inspection certificate is signed by a trusted CA from the Chromium trust list.

    • Chromium-based web browsers do not allow adding certificates for HTTP/3 traffic to the browser's trusted store. See sk111754.

    • Inspection of QUIC traffic over a proxy is not supported.

    • Protocols that rely on QUIC, except HTTP/3, will be downgraded to an earlier HTTP version.