Gateway logs kept only on the gateway
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
Logs kept only on the gateway are lost with it and can be altered by whoever controls it, and nothing correlates them with other devices.
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 > Logs and select Send gateway logs and alerts to server, naming the management or log server, with a backup server where one exists.
- Publish, then install the policy on the gateways that use it.
Command line
Check Point mgmt_cli and Gaia clish
mgmt_cli login > id.txtmgmt_cli set simple-gateway name "<gateway>" send-logs-to-server.1 "<log-server>" save-logs-locally false -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 in2
- <gateway>
- The gateway or cluster object to change
- <log-server>
- The management or log server that collects the gateway's logs
Before you type it4
- 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.
How to confirm the fix
- Confirm the gateway's logs appear in Logs & Monitor on the server after the install.
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 Logging and Integrations
See it on your own firewall
One complete analysis of one firewall costs nothing. A card is required and nothing is charged.