- 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
I have an r80.40 cluster where a risk has been detected i.e. "Outgoing packets from Gateway towards any destination is enabled"
I did a little digging in and it seems this alert is being created as option "Accept outgoing packets originating from Gateway" in Global properties is enabled.
My query is : is it recommended to disable this option ? i read a few R80.40 documents and it seems i can use an updatable object for Checkpoint update services by creating a rule in ACL. is this a recommended approach ? any chance i break something if i disable this option from global properties.
Thanks
It is the easy option NOT to disable this - all CP services can be contacted by the GW. To see this as a risk points to severe restraints, but yes, you can disable the default and use sk131852 for the settings from sk106251.
It is the easy option NOT to disable this - all CP services can be contacted by the GW. To see this as a risk points to severe restraints, but yes, you can disable the default and use sk131852 for the settings from sk106251.
Thanks for the reply..i went through these SKs and i m comfortable with enabling Checkpoint updatable object for GWs.. my only worry is what other traffic this will impact..i mean i don't want to enable access to checkpoint cloud but in the process break anything else like stop control connection traffic which could break the cluster or connection with mgmt server
This is a valid concern. Implied rule allowing GW to send any outgoing traffic it needs to send out. This option is enabled by default, and is it fact recommended by Check Point. This rule covers all outgoingGW connectivity, not only for Check Point services, but for other needs: DNS, certificate validation in case of HTTPSi, and more.
For the management connections specifically, there is another implied rule "Allow control connections", this is also enabled by default and recommended.
i guess i will go back and leave it as it is as it is a recommendation..any document i can present to support this statement ?
thanks
sk43401 discourages disabling implied rules.
I totally agree with @G_W_Albrecht . Also, if you actually read what it says in the help section, it pretty much boils down to the same thing he said.
Accepts all packets from connections that originate at the Check Point Security Gateway.
Allow Security Gateways to access Check Point online services.
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
| User | Count |
|---|---|
| 28 | |
| 8 | |
| 7 | |
| 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 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