- Products
- Learn
- Local User Groups
- Partners
- More
The Great Exposure Reset
24 February 2026 @ 5pm CET / 11am EST
AI Security Masters E4:
Introducing Cyata - Securing the Agenic AI Era
AI Security Masters E3:
AI-Generated Malware
CheckMates Go:
CheckMates Fest
Hi,
This evening I upgraded one of our FW's to R82 from R81.20
All went well, but then I noticed it was getting an odd message about couldn't contact Checkpoint and could not then find updates.
After various head scratching I looked in the logs and for some reason the Geo Policy now thinks my IP address is registered in BGR which is on our risk database, so blocked.
Long story short I have had to add an exception in the policy, but what on earth would cause this, and is there a reasonable fix or do i just leave me exception in place?
Thanks
Wayne - confused 🙂
Here is what I always do with all customers.
Create whatever country exceptions you need on the top of the rulebase, then just below that, add all other countries as source (group them so it looks nicer), then dst as any, service any, action block, install policy, thats it. And you can also delete old legacy geo policy.
Andy
Hey Wayne,
I hate assuming things, but let me take a wild guess...did you by any chance have old legacy geo policy in place? If so, this behavior would not surprise me. Since R80.20, updatable objects are recommended to use for geo blocking.
Andy
Hi Andy,
Yes I use the old Geo policy, I checked my IP on MaxMind and that says UK based.
Still a bit confused?
Cheers
Wayne
Please refer to https://support.checkpoint.com/results/sk/sk126172 and use Updatable Objects instead of the Geo Policy.
Hi Tal,
I will try converting to UO and see what happens
Cheers
Wayne
Quick question, if I do use UO for Geo policy, what is the best way to have exceptions?
Here is what I always do with all customers.
Create whatever country exceptions you need on the top of the rulebase, then just below that, add all other countries as source (group them so it looks nicer), then dst as any, service any, action block, install policy, thats it. And you can also delete old legacy geo policy.
Andy
I get it, but I had seen it happen many times before with old geo policy, specially in new versions. As @Tal_Paz-Fridman suggested, that sk is best to follow.
Andy
Thanks to both of you !!
Forgot to add something else, though this obviously will not apply to everyone out there, but I want to mention it to you Wayne. While back, I was working with a hospital and we determined they were having bunch of issues due to geo policy, until we addeed Israel and Japan as exceptions. Mind you, that should be easy to tell from the logs if you ever encounter such an issue.
Best,
Andy
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
| User | Count |
|---|---|
| 27 | |
| 18 | |
| 10 | |
| 9 | |
| 7 | |
| 7 | |
| 6 | |
| 6 | |
| 5 | |
| 4 |
Mon 23 Feb 2026 @ 11:00 AM (EST)
Latest updates on Quantum Spark including R82 features and Spark Management zero touch - AMERTue 24 Feb 2026 @ 10:00 AM (CET)
Latest updates on Quantum Spark including R82 features and Spark Management zero touch - EMEATue 24 Feb 2026 @ 11:00 AM (EST)
Under The Hood: CloudGuard Network Security for Azure Virtual WANMon 23 Feb 2026 @ 11:00 AM (EST)
Latest updates on Quantum Spark including R82 features and Spark Management zero touch - AMERTue 24 Feb 2026 @ 10:00 AM (CET)
Latest updates on Quantum Spark including R82 features and Spark Management zero touch - EMEATue 24 Feb 2026 @ 11:00 AM (EST)
Under The Hood: CloudGuard Network Security for Azure Virtual WANThu 26 Feb 2026 @ 05:00 PM (CET)
AI Security Masters Session 4: Introducing Cyata, Securing the Agentic AI EraFri 06 Mar 2026 @ 08:00 AM (COT)
Check Point R82 Hands‑On Bootcamp – Comunidad DOJO PanamáAbout CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY