- Products
- Learn
- Local User Groups
- Partners
- More
The Great Exposure Reset
24 February 2026 @ 5pm CET / 11am EST
CheckMates Fest 2026
Watch Now!AI Security Masters
Hacking with AI: The Dark Side of Innovation
CheckMates Go:
CheckMates Fest
Check Point released v6.03 of it's Gaia HealthCheck Script.
Script author: Nathan Davieau (LinkedIn profile)
Whats new:
Whats missing:
Hi,
I found one issue with the new script.
In the reports, all "3." are truncated and color pink:

The issue is present with sk number, edition, title, ....
Someone can check this ?
For information:


Thanks ![]()
Thanks for your feedback.
Can you please check the encoding settings on your putty session (Under "Window --> Translation")? The latest version executes fine on my systems but I have known the script to display differently when different encoding is used.
My putty defaults to "ISO-8859-1:1998 (Latin-1, West Europe)" but "UTF-8" is also recommended.
Hi Nathan,
Sorry I get your message only today... Anyway, this issue is solved after upgrading to last R77.30 take.
I'm not really sure how and why, but solved !
Thank you for this script...
Any chance it can be modified to support either email directly or Job Scheduler/cron friendly?
When I leverage the Job Scheduler, it is currently reporting weird errors when emailed as part of the Job Scheduler output. We would love to use this great script for our daily SOC monitoring Runbook within our environment.
tput: No value for $TERM and no -T specified
tput: No value for $TERM and no -T specifiedtput: No value for $TERM and no -T specifiedtput: No value for $TERM and no -T specifiedtput: No value for $TERM and no -T specified.../home/admin/healthcheck.sh: line 1324: arp: command not found/home/admin/healthcheck.sh: line 1360: ifconfig: command not found../bin/dmiparse: line 19: dmidecode: command not found/home/admin/healthcheck.sh: line 3505: dmidecode: command not found
I do not currently have any plans to include cron/Job Scheduler or email functionality with this script.
I noticed that the SND/FW Worker Overlap Check contains a routine that says "If there are only two CPUs overlap is OK". I think the better way to handle this would be to result a warning message saying: You may want to consider to turn off CoreXL (as suggested by Tim Hall) or in case of Open Servers to license more CPU cores.
I sent an updated version to our SK team (should be up within a day or so) which changes the 2 core check status to Info instead of OK and provides additional information regarding disabling CoreXL if the RX Drops are high on any interface.
Thanks for your update.
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
| User | Count |
|---|---|
| 56 | |
| 44 | |
| 16 | |
| 14 | |
| 14 | |
| 11 | |
| 10 | |
| 10 | |
| 9 | |
| 8 |
Thu 12 Feb 2026 @ 05:00 PM (CET)
AI Security Masters Session 3: AI-Generated Malware - From Experimentation to Operational RealityFri 13 Feb 2026 @ 10:00 AM (CET)
CheckMates Live Netherlands - Sessie 43: Terugblik op de Check Point Sales Kick Off 2026Thu 19 Feb 2026 @ 03:00 PM (EST)
Americas Deep Dive: Check Point Management API Best PracticesThu 12 Feb 2026 @ 05:00 PM (CET)
AI Security Masters Session 3: AI-Generated Malware - From Experimentation to Operational RealityFri 13 Feb 2026 @ 10:00 AM (CET)
CheckMates Live Netherlands - Sessie 43: Terugblik op de Check Point Sales Kick Off 2026Thu 19 Feb 2026 @ 03:00 PM (EST)
Americas Deep Dive: Check Point Management API Best PracticesAbout CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY