- 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
There are quite a few "weak" ciphers that are enabled on the gateways and I'm looking to disable them, which I can do this with the cipher_util tool on each gateway.
My query is, is there a way to do this from the management, such that the config remains following an upgrade, or is it something that you have to remember to do every time you upgrade or rebuild?
This is primarily for the SSLVPN portal, as these weak ciphers are being listed as available by a vulnerability scan.
You can make the settings on one gateway and copy the necessary configuration files to the other gateways.
See: https://support.checkpoint.com/results/sk/sk126613
Note that we include support for new ciphers in every release, so it should probably be re-generated versus simply blindly copied on an upgrade.
Does this recreation apply just to version upgrades (eg R81.10 -> R81.20) or to Jumbo's too?
Is there a way to disable them from the CLI? (thinking I could create a script to do this)
Not sure these files are updated on a JHF upgrade.
cipher_util is a CLI tool.
However, I assume you mean a non-interactive CLI tool, which I don't believe we have currently.
You may also find the following SK quite helpful to track down all the places weak ciphers might be used; it details the precise steps to completely banish 3DES from being used anywhere on a Check Point firewall, and there are quite a few places to change: sk113114: Check Point response to CVE-2016-2183 (Sweet32)
In case it is not obvious after reading that SK, 3DES is an absolute no-go in today's world from both a security and performance perspective, as 3DES is easily 2-3 times slower than AES. 3DES was hurriedly rolled out in a bit of a panic back in the day when it was realized that DES 56-bit was not secure enough anymore, due mainly to Moore's Law.
Same question came up once with one of customers I was helping with and TAC confirmed it has to be done manually. Not sure if that changed, as this was 3 years ago.
Andy
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
| User | Count |
|---|---|
| 28 | |
| 8 | |
| 5 | |
| 5 | |
| 5 | |
| 4 | |
| 4 | |
| 4 | |
| 4 | |
| 3 |
Tue 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 DefenseTue 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 DefenseAbout CheckMates
Learn Check Point
Advanced Learning
WE SECURE YOUR AI TRANSFORMATION