- Products
- Learn
- Local User Groups
- Partners
- More
What’s New in Device Diagnostics?
Dec 2nd @ 5pm CET / 11am EST
AI Security Masters
Security in the Pace of AI:
From Threat to Force Multiplier
CPX is Back!
Join us in Las Vegas, Vienna, and/or Bangkok!
Check Point Named a Leader
The Forrester Wave:
Enterprise Firewall Solutions, Q4 2026
What’s New in Agentic Network Orchestration
CheckMates Go:
Fun Ding
Config Point, also called Unified Configuration, shown as Advanced Configuration in Gaia Portal, and keeps Check Point tuning parameters in one database on the gateway.
It replaces hand-editing files such as fwkern.conf and simkern.conf from Expert mode.
Config Point is part of the plan by Check Point to get admins out of Expert mode (to be deprecated).
Their stated aim is to remove the need for Expert mode, not Expert mode itself, which is still available, for now anyway.
Config Point offers:
Clish, Gaia Portal or the Gaia API can be used. All three routes read and write the same values.
There is a fourth one but that requires Expert mode; confp_cli
|
Route |
View |
Change |
Role feature |
Use it for |
|
Gaia Portal |
System Management > Advanced Configuration |
Edit, Save, Revert |
sysconfig |
Browsing, one-off changes, the Pending view |
|
Gaia Clish / gClish |
show param |
set param |
param |
Day-to-day admin and SSH scripts |
|
Gaia API |
show-param |
set-param |
expert_api_param |
Automation, including mgmt_cli --context gaia_api |
|
Expert mode |
confp_cli get |
confp_cli set |
(needs Expert) |
Avoid. Dropped from the R82.20 guide |
By default adminRole can edit and monitorRole can view.
The command names changed between releases. Administrator need to write scripts specific for the version run (when comparing R82, R82.10 and R82.20).
|
Release |
Clish |
Gaia API |
|
R82 |
show/set global-param |
show-global-params / set-global-params |
|
R82.10 |
show/set param |
show-param / set-param |
|
R82.20 |
show/set param, plus export param / import param listed in the on-box introduction |
show-param / set-param |
The on-box introduction (links below) lists export param and import param, but the R82.20 Admin Guide does not document them yet.
The on-box API reference also says set-param works on “R82+”, although the R82 guide documents only set-global-params.
It is recommended to test on your version.
The reference documentation can be found is on the gateway or management server:
https://<gateway IP>/param_docs/
and
https://<gateway>/gaia_docs/#web/set-param
The Gaia API Reference has a few examples but the best reference are:
https://<gateway IP>/param_docs/#/introduction
and
the R82.20 Gaia Admin Guide:
https://sc1.checkpoint.com/documents/latest/GaiaAPIs/#web/set-param~v2%20
In that page the link at the top (https://sc1.checkpoint.com/param_docs/) returns Not Found so you need to use the /param_docs link against you local Gaia machine, or click Configuration Reference in the Gaia Portal > System Management > Advanced Configuration
https://<gateway IP>/param_docs/
The page is built from the schemas installed on that gateway, so it always matches the version and Jumbo you are running.
Pick a category on the left (All Parameters), filter by name or path, and click a row to see:
To search from Clish, use wildcards:
Offline copy:
/config_point/#/all_parametrs <-- Click Export CSV (top right) to download unified_configuration_all_parameters.csv
In the CSV file you will find all the parameter data.
You can check the current value, make the change with a comment, then check again.
Changes take effect immediately.
The example below turns off log suppression while you troubleshoot (firewall.ipv4.tp.logs.logsup_none - Reference: sk115876 - Some fields are missing from IPS or Threat Prevention logs).
Example for R82.20:
lock database override show param path firewall.ipv4.tp.logs.logsup_none set param path firewall.ipv4.tp.logs.logsup_none param-value true comment "Troubleshooting: log suppression off - revert after case closed" show param path firewall.ipv4.tp.logs.logsup_none format json verbose-level 3 set param path firewall.ipv4.tp.logs.logsup_none use-default true show param path firewall.ipv4.tp.logs.logsup_none
show param path firewall.ipv4.tp.logs.logsup_none -------------------------------------------------------------------------------------------------------------------- Name Value Pending-value Pending Default -------------------------------------------------------------------------------------------------------------------- firewall.ipv4.tp.logs.logsup_none False - - False -------------------------------------------------------------------------------------------------------------------- set param path firewall.ipv4.tp.logs.logsup_none param-value true comment "Troubleshooting: log suppression off - revert after case closed" { "param-list": [ { "name": "firewall.ipv4.tp.logs.logsup_none", "comments": "Troubleshooting: log suppression off - revert after case closed", "description": "Disable log suppression.", "default_value": false, "last-modified": { "user": "admin", "time": "17:42:04", "date": "20-11-2026", "iso8601": "2026-11-20T17:42:04", "posix": 1795196524.0, "prev-value": false }, "virtual-system-id": 0, "current_value": true, "new_value": true, "old_value": { "value": false, "pending_value": "n/a" }, "pending": { "pending_value": "n/a", "action": "n/a" }, "value_changed": true } ], "matched": 1, "changed_count": 1, "pending_count": 0, "sp_members": "n/a" } show param path firewall.ipv4.tp.logs.logsup_none -------------------------------------------------------------------------------------------------------------------- Name Value Pending-value Pending Default -------------------------------------------------------------------------------------------------------------------- firewall.ipv4.tp.logs.logsup_none True - - False -------------------------------------------------------------------------------------------------------------------- show param path firewall.ipv4.tp.logs.logsup_none format json verbose-level 3 { "param-list": [ { "name": "firewall.ipv4.tp.logs.logsup_none", "comments": "Troubleshooting: log suppression off - revert after case closed", "description": "Disable log suppression.", "default_value": false, "last-modified": { "user": "admin", "time": "17:42:04", "date": "20-11-2026", "iso8601": "2026-11-20T17:42:04", "posix": 1795196524.0, "prev-value": false }, "virtual-system-id": 0, "current_value": true, "pending": { "pending_value": "n/a", "action": "n/a" } } ] } set param path firewall.ipv4.tp.logs.logsup_none use-default true { "param-list": [ { "name": "firewall.ipv4.tp.logs.logsup_none", "comments": "Troubleshooting: log suppression off - revert after case closed", "description": "Disable log suppression.", "default_value": false, "last-modified": { "user": "admin", "time": "17:42:06", "date": "20-11-2026", "iso8601": "2026-11-20T17:42:06", "posix": 1795196526.0, "prev-value": true }, "virtual-system-id": 0, "current_value": false, "new_value": false, "old_value": { "value": true, "pending_value": "n/a" }, "pending": { "pending_value": "n/a", "action": "n/a" }, "value_changed": true } ], "matched": 1, "changed_count": 1, "pending_count": 0, "sp_members": "n/a" } show param path firewall.ipv4.tp.logs.logsup_none -------------------------------------------------------------------------------------------------------------------- Name Value Pending-value Pending Default -------------------------------------------------------------------------------------------------------------------- firewall.ipv4.tp.logs.logsup_none False - - False --------------------------------------------------------------------------------------------------------------------
Command Options:
|
Option |
Effect |
|
dry-run true |
Checks the change without saving it |
|
volatile true |
Applies the value until the next reboot, then the old value returns |
|
use-default true |
Puts the parameter back to its default |
|
comment "…" |
Up to 256 characters, shown in Portal and in show param |
|
key <path> key-value <v> |
Changes one field inside a structured parameter |
|
use-regex true |
Lets the path include * |
You do not need save config. set param writes to the database as soon as it runs.
Through the Gaia API with mgmt_cli:
One call can change several parameters. The API field names differ from Clish, and the format is: param-path, value and comments.
mgmt_cli -m x.x.x.x -u admin \ set param \ param-list.1.param-path "firewall.ipv4.tp.logs.logsup_none" \ param-list.1.value true \ param-list.1.comments "Troubleshooting: log suppression off" \ param-list.2.param-path "firewall.ipv4.connection.fw_allow_simultaneous_ping" \ param-list.2.use-default true \ --context gaia_api --version 1.9 --format json
The call runs as a task. Add --sync false to get back only a task-id, then poll it with show-task.
The result lists, for each parameter, the current value, the default, any pending value and its required action, and who last changed it.
Request-level options are virtual-system-id, dry-run and use-regex.
Check which version your gateway’s gaia_docs shows before scripting.
To undo a change:
run set param path <path> use-default true, or in Portal use Revert > Revert to default value / Revert to last saved value.
Comparing R82.10 and R82.10
To find a parameter on either release, search by its name with a wildcard:
show param path firewall*fw_assert_on.
Differences between R82.10 and R82.10 at a glance:
|
Item |
R82.10 Take 40 |
R82.20 Take 14 |
|
Number of parameters |
572 |
6,935 |
|
Path style |
firewall.ipv4.infra.debug.* |
firewall.ipv4.debug.*. Paths changed. |
|
show param table |
Includes Description and Comments |
No Description or Comments columns |
|
Wildcards in show param path |
* in the path; use-regex rejected |
Same |
|
set param options |
comment, key, param-value, use-default, volatile, use-regex |
Same, plus input-format |
|
dry-run in Clish |
Rejected |
Rejected, although the guide lists it |
|
dry-run in the Gaia API |
API calls fail |
Works |
|
Clear a comment |
Not possible ("" rejected) |
Not possible |
|
filter-by with-comments |
Only admin-changed parameters |
Also many built-in parameters that ship with comments |
|
export param / import param |
Present |
Present; export wrote 112 entries |
|
Gaia API show-param / set-param |
Fail on the gateway (server errors) |
Work in versions 1.9 and 2 |
|
Gaia API port |
Gaia Portal port |
Same |
|
fw ctl set -f |
Writes to the database, comment "fw ctl set" |
Same; does not write fwkern.conf |
|
fwkern.conf |
Not present |
Created by hand: its value won at boot, and the line was commented out |
|
Example parameter logsup_none |
Not present |
firewall.ipv4.tp.logs.logsup_none |
The same parameter has a different full path on R82.10 and R82.20, so any script, note or SK reference that uses a full path breaks after an upgrade.
R82.20 mostly drops the infra level and regroups some parameters under new headings.
|
Parameter |
R82.10 path |
R82.20 path |
|
conn_stats_alpha_shift |
firewall.ipv4.infra.conn_stats.conn_stats_alpha_shift |
firewall.ipv4.connection.conn_stats.conn_stats_alpha_shift |
|
fw_assert_on |
firewall.ipv4.infra.debug.assertion.fw_assert_on |
firewall.ipv4.debug.assertion.fw_assert_on |
|
cplock_enable_statistics |
securexl.ipv4.infra.locks.cplock_enable_statistics |
securexl.ipv4.locks.cplock_enable_statistics |
|
memory parameters |
firewall.ipv4.infra.memory.* |
firewall.ipv4.memory.* |
|
SIP parameters |
firewall.ipv4.infra.voip.sip.* |
firewall.ipv4.voip.sip.* |
Examples:
These parameters exist on R82.20 Take 14
The SKs come from the parameter's own data.fw ctl get int can be used to confirm the kernel value where relevant.
|
Situation |
Parameter |
SK |
|---|---|---|
|
Remote Access VPN under password guessing: lockout threshold, delay and penalty |
|
sk180271 |
|
Monitoring tool sends parallel pings to the same host and some are dropped |
|
sk26874 |
|
SIP provider sends many re-INVITEs and calls drop |
|
sk116144 |
|
SIP trunk sends an empty Contact header |
|
sk119512 |
|
Asymmetric routing during a migration drops out-of-state TCP. Allow it temporarily while you fix routing |
|
sk117374 |
|
Logs flooded with out-of-state UDP drops |
|
sk103084 |
|
Applications should get a TCP reset rather than a silent drop for non-SYN first packets |
|
– |
|
Site-to-site VPN peer behind NAT that uses Link Selection |
|
sk180956 |
|
IPS or Threat Prevention logs are suppressed while you investigate |
|
sk115876, sk108423 |
|
Cluster: only the active member should send logs |
|
– |
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
| User | Count |
|---|---|
| 30 | |
| 8 | |
| 7 | |
| 5 | |
| 5 | |
| 4 | |
| 4 | |
| 4 | |
| 3 | |
| 3 |
Tue 24 Nov 2026 @ 01:30 PM (GMT)
La nueva realidad de los ataques DDoS: autonomía, escala y el futuro de la defensaThu 26 Nov 2026 @ 10:00 AM (CET)
The Cloud Architects Series: Cloud Security State in 2026 – Lessons Learned and a Look AheadWed 02 Dec 2026 @ 03:30 PM (GMT)
The New DDoS Reality: Autonomy, Scale, and the Future of DefenseThu 03 Dec 2026 @ 11:00 AM (EST)
Under the Hood: Check Point Cloud Firewall for Nutanix - How to Secure your AI WorkloadsTue 24 Nov 2026 @ 01:30 PM (GMT)
La nueva realidad de los ataques DDoS: autonomía, escala y el futuro de la defensaWed 02 Dec 2026 @ 03:30 PM (GMT)
The New DDoS Reality: Autonomy, Scale, and the Future of DefenseThu 03 Dec 2026 @ 11:00 AM (EST)
Under the Hood: Check Point Cloud Firewall for Nutanix - How to Secure your AI WorkloadsAbout CheckMates
Learn Check Point
Advanced Learning
WE SECURE YOUR AI TRANSFORMATION