> Source: [sk180476](https://support.checkpoint.com/results/sk/sk180476)

# sk180476 - Geo Policy rules enforced when the Geo Protection feature does not appear in SmartConsole

| Property | Value |
|----------|-------|
| Solution ID | sk180476 |
| Date Created | 2023-01-04 |
| Last Modified | 2023-01-11 |
| Technical Level | Advanced |
| Products | Security Gateway, Security Management Server |
| Versions | R81.20, R81.10 (EOS), R81.20, R81 (EOS), R81.10 (EOS), R81 (EOS) |
| OS | Gaia |

## Symptoms

- * Accept/Drop logs that match Geo Policy rules have the **Service** and **Access Role** fields empty.
* The same traffic matches Geo Policy Rules and other rules.
* Output of `#fw up_execute` (see [sk166732](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk166732)) on the Security Gateway shows a decision that is different than the log for a Geo Policy rule.

## Cause

Before an upgrade to versions R81 or higher, Geo Policy was active on the Security Gateway. Starting in R81, by default Geo Policy is hidden in SmartConsole. As a result, after the upgrade Geo Policy is active but hidden in SmartConsole.

## Solution

This solution requires authentication. Please log in to view the full solution.

---

# Agent Instructions

This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products.

## Navigating This Knowledge Base

- **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt)
- **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml)
- **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}`
- **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content