HTTPS inspection off with content blades on
At a glance
Base severity
Area
Platform
Evidence level
Benchmark reference
Reads the export, not the device
ConfigProof reads a configuration export. This control is evaluated against the objects in that file, and it reports what the file says. It does not connect to the device and sees no traffic, so a finding here describes the configuration, not what the firewall is doing right now.
Why it matters
Most web traffic is encrypted. Without HTTPS inspection these blades see only the server name, not the content or the file they are meant to inspect.
How to fix it
Web interface
The steps below are written for the web interface. A finding raised on your own export carries the same steps with your object names filled in.
- In SmartConsole, open the gateway object > HTTPS Inspection, create or import the outbound CA certificate, and select Enable HTTPS Inspection.
- Deploy the CA certificate to the clients, add an HTTPS inspection policy with bypass for privacy categories, and install the policy.
Command line
Check Point mgmt_cli and Gaia clish
mgmt_cli login > id.txtmgmt_cli set simple-gateway name "<gateway>" enable-https-inspection true -s id.txtmgmt_cli publish -s id.txtmgmt_cli logout -s id.txt
An example. Values in angle brackets are yours to supply; a finding on your own export fills in the names it read. Nothing here installs a policy. Publish, review, then install the policy on your gateways yourself; Gaia changes need save config.
Read it back
mgmt_cli show simple-gateway name "<gateway>"Values to fill in1
- <gateway>
- The gateway or cluster object to change
Before you type it5
- Written from the Check Point Management API reference and Gaia clish syntax, not yet run on a device. Read each line before typing it.
- Run on the management server, or add -m with the server and -u with an administrator to each call; publish makes the change visible to other sessions.
- Install the policy on the affected gateways after reviewing the published change.
- For a cluster, use set simple-cluster with the cluster object's name instead of set simple-gateway.
- Create or import the outbound CA certificate and deploy it to the clients before enabling inspection.
How to confirm the fix
- Confirm clients trust the CA certificate before inspecting their traffic.
Limits
- No limitation is recorded for this control beyond the one that applies to all of them: it reads a configuration export.
Compliance references
No benchmark recommendation is mapped to this control in this version.
More in Security Profiles
- CKP-SEC-023Internet-facing gateway with no Threat Prevention blade
- CKP-SEC-024Threat Prevention blade on and no Threat Prevention policy installed
- CKP-SEC-025Threat profile only detects high confidence protections
- CKP-SEC-027Threat profile leaves protections inactive
- CKP-SEC-029Application Control or URL Filtering on and no layer uses it
- CKP-LIC-001Blade is enabled and no valid license backs it
- CKP-LIC-002License ends within 31 to 90 days
- CKP-LIC-003Device runs on an evaluation license
See it on your own firewall
One complete analysis of one firewall costs nothing. A card is required and nothing is charged.