- Products
- Learn
- Local User Groups
- Partners
- More
AI Security Masters E7:
How CPR Broke ChatGPT's Isolation and What It Means for You
Blueprint Architecture for Securing
The AI Factory & AI Data Center
Call For Papers
Your Expertise. Our Stage
Good, Better, Best:
Prioritizing Defenses Against Credential Abuse
Ink Dragon: A Major Nation-State Campaign
Watch HereCheckMates Go:
CheckMates Fest
While trying to install policy to our Gateway cluster, we received the following failure message:
Come to find out during the 7/30 URLF/App Ctrl automagic update, the Anonymizer object was updated and now has the icmp-proto included which appears to be causing the installation failure.
Is the inclusion of icmp-proto in the Anonymizer intentional or accidental?
Also, if it was intentional, is it permanent?
Thank You,
Albert
The images you embedded didn't come across.
In any case, I recommend engaging with the TAC as I can't imagine this change was intentional.
Hi,
The issue has been resolved earlier today with the latest online update package.
Please make sure the Security Management server is updated and push policy.
Thanks...
--Mor
.
Thanks, Mor.
I ran the manual Management update and the Anonymizer is back to its original state and I should not run into the same issue when I install policy this evening to my R77.30 cluster.
Thanks, again.
Albert
Hmm... I see the ICMP in the Anonymizer, but in and by itself it does not cause any issues:


The issue is only related to setups with R80.10 managing R77.X or earlier GWs..
Understood. Did the latest update remove the ICMP Proto from Anonymizers, or is it still present and some-kind of background logic was embedded to differentiate installation targets?
The latest update removed the ICMP service from the category (two categories were affected - Critical Risk & Anonymizers).
We're working with the relevant groups to explore alternative vehicle for delivering this change to the field.
Thanks! Seeing same thing after manual update: ICMP is removed from two categories.
Still seeing similar issue for icmp_request,. traffic is being dropped due its falls under other category as well.
Database already updated manually and it doesn't has the icmp serivces listed under Anonymizer and Critical risk.
it consider icmp request as - application name : DET (Data Exfiltration Toolkit - ICMP Mode)

Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
| User | Count |
|---|---|
| 66 | |
| 19 | |
| 13 | |
| 12 | |
| 11 | |
| 9 | |
| 9 | |
| 7 | |
| 7 | |
| 7 |
Tue 28 Apr 2026 @ 06:00 PM (IDT)
Under the Hood: Securing your GenAI-enabled Web Applications with Check Point WAFThu 30 Apr 2026 @ 03:00 PM (PDT)
Hillsboro, OR: Securing The AI Transformation and Exposure ManagementTue 28 Apr 2026 @ 06:00 PM (IDT)
Under the Hood: Securing your GenAI-enabled Web Applications with Check Point WAFTue 12 May 2026 @ 10:00 AM (CEST)
The Cloud Architects Series: Check Point Cloud Firewall delivered as a serviceThu 30 Apr 2026 @ 03:00 PM (PDT)
Hillsboro, OR: Securing The AI Transformation and Exposure ManagementAbout CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY