Gaia sends syslog to no remote server
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
The box's OS logs are lost with it and can be altered by whoever controls it.
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 the Gaia Portal, open System Management > System Logging and add a remote syslog server.
- Run save config in clish, or the change is lost at the next reboot.
Command line
Check Point mgmt_cli and Gaia clish
add syslog log-remote-address <syslog-server> level infosave config
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
show syslog allValues to fill in1
- <syslog-server>
- The remote syslog server address
Before you type it2
- Written from the Check Point Management API reference and Gaia clish syntax, not yet run on a device. Read each line before typing it.
- Type in clish on each Gaia gateway or cluster member.
How to confirm the fix
- Confirm the box's messages arrive at the syslog server.
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.