- Products
- Learn
- Local User Groups
- Partners
- More
What's New in R82.10?
Register HereWhen the Agents Attack
A Live Look at Agentic Exposure Validation
AI Security Masters E8:
Claude Mythos: New Era in Cyber Security
CheckMates Go:
CheckMates Fest
Hi mates,
As our executives have requested it, I would like to gather some experience reports regarding the reliability of CP Geo IP data when using updatable objects.
Has anyone experienced complaints about incorrect country assignments for IP addresses? Or have the assignments generally been accurate?
Any experiences or feedback would be greatly appreciated.
thanks
Vince
I have couple customers. False positive can happen, if it happens you need to open TAC case. But I don't recall the last time I did that. The IP information comes from a third party. If you need to whitelist you have to do it yourself by making a bypass for the problematic IP. If you want it to be flagged correctly SR is needed. So yes it works, is it 100%, no but all extra tools can help in a better security
Make sure you do not use legacy geo protection.
Hey Vince,
I totally agree with @Lesley here. I also have not had many resports about false positives in the past (maybe 3 or 4), but opening TAC case usually takes care of it quickly.
maxmind.com is very reliable as far as those things.
Nobody has complained while my company has used updatable objects, so the geolocation is good enough for us. Currently dealing with a Cloudflare address showing up as Russian some of the time and USAian some of the time. Even two different views of exactly the same log entry seem to disagree on where it is. We only noticed it when proactively poking through geolocation drops recently.
I recommend building rules based on geolocations in a separate ordered layer. This makes it easier and safer to add exceptions should they be needed, since your normal firewall rules will still be applied to them.
We have not had any reports with outbound Geo Blocking being incorrect.
Inbound has been reliable in the terms of people going on vacation, reporting they cannot get logged in and the Geo Blocking accurately has picked up their vacation spot, which is blocked on purpose.
We have been using the updatable objects for a little over 3 years, no complaints.
I have couple customers. False positive can happen, if it happens you need to open TAC case. But I don't recall the last time I did that. The IP information comes from a third party. If you need to whitelist you have to do it yourself by making a bypass for the problematic IP. If you want it to be flagged correctly SR is needed. So yes it works, is it 100%, no but all extra tools can help in a better security
Make sure you do not use legacy geo protection.
Hey Vince,
I totally agree with @Lesley here. I also have not had many resports about false positives in the past (maybe 3 or 4), but opening TAC case usually takes care of it quickly.
maxmind.com is very reliable as far as those things.
Nobody has complained while my company has used updatable objects, so the geolocation is good enough for us. Currently dealing with a Cloudflare address showing up as Russian some of the time and USAian some of the time. Even two different views of exactly the same log entry seem to disagree on where it is. We only noticed it when proactively poking through geolocation drops recently.
I recommend building rules based on geolocations in a separate ordered layer. This makes it easier and safer to add exceptions should they be needed, since your normal firewall rules will still be applied to them.
We have not had any reports with outbound Geo Blocking being incorrect.
Inbound has been reliable in the terms of people going on vacation, reporting they cannot get logged in and the Geo Blocking accurately has picked up their vacation spot, which is blocked on purpose.
We have been using the updatable objects for a little over 3 years, no complaints.
Thanks all for your feedback. No complaints sounds good. We will talk bit more about that and decide.
Again, thanks all, much appreciated.
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
| User | Count |
|---|---|
| 12 | |
| 9 | |
| 8 | |
| 7 | |
| 6 | |
| 6 | |
| 5 | |
| 4 | |
| 3 | |
| 3 |
Tue 23 Jun 2026 @ 05:00 PM (CEST)
Under the Hood: Check Point Cloud Firewall | Securing all of your clouds: Art of the possibleThu 25 Jun 2026 @ 10:00 AM (PDT)
AI Security Masters E10: READY OR NOT: Securing the AI Enterprise 2/5 - AI Red TeamingThu 02 Jul 2026 @ 06:00 PM (CST)
Revolucionando la Seguridad con IA Generativa: Prevención Inteligente en Tiempo RealThu 09 Jul 2026 @ 11:00 AM (CEST)
The Cloud Architects Series: Check Point Edge Protection SD-WAN & SASETue 14 Jul 2026 @ 10:00 AM (PDT)
AI Security Masters E11: READY OR NOT: Securing the AI Enterprise 3/5 - AI Workforce SecurityTue 23 Jun 2026 @ 05:00 PM (CEST)
Under the Hood: Check Point Cloud Firewall | Securing all of your clouds: Art of the possibleThu 25 Jun 2026 @ 10:00 AM (PDT)
AI Security Masters E10: READY OR NOT: Securing the AI Enterprise 2/5 - AI Red TeamingTue 14 Jul 2026 @ 10:00 AM (PDT)
AI Security Masters E11: READY OR NOT: Securing the AI Enterprise 3/5 - AI Workforce SecurityThu 30 Jul 2026 @ 10:00 AM (PDT)
AI Security Masters E12: READY OR NOT: Securing the AI Enterprise 4/5 - AI GatewayThu 20 Aug 2026 @ 10:00 AM (PDT)
AI Security Masters E13: READY OR NOT: Securing the AI Ent 5/5 - AI Research & Threat LandscapeThu 02 Jul 2026 @ 06:00 PM (CST)
Revolucionando la Seguridad con IA Generativa: Prevención Inteligente en Tiempo RealAbout CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY