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

# sk185051 - VPN Compliance Best Practice ID VPN106 becomes poor after changing the VPN Encryption from IKEv1 to IKEv2

| Property | Value |
|----------|-------|
| Solution ID | sk185051 |
| Date Created | 2026-06-10 |
| Last Modified | 2026-06-22 |
| Technical Level | Advanced |
| Products | Security Management Server, Multi-Domain Security Management Server |
| Versions | R82.10, R82, R81.20, R82.10, R81.20, R82 |
| OS | Gaia |

## Symptoms

- VPN Compliance Best Practice ID VPN106 becomes poor after changing the VPN Encryption from IKEv1 to IKEv2.

## Cause

An issue in the `$FWDIR/conf/grc_conditions3.xml` file.

## 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