Per-gateway Secure Configuration Verification (SCV) policy not enforced for Remote Access VPN clients

Product

Remote Access VPN

Version

R81.20, R82, R82.10

Last Modified

2026-07-23

Symptoms

• The Management server does not enforce SCV checks that are defined in per-gateway local.scv files.
• When the same SCV configuration is placed only in the global file, SCV enforcement works correctly, and non-compliant clients are detected and handled as expected.
• On the Security Gateway, the directory $FWDIR/state/local/PS/ contains an SCV policy file (local.scv) only when the global $FWDIR/conf/local.scv is used. When a per-gateway file (for example, local.scv_firewall-01) exists on the Management Server, its content is not copied to $FWDIR/state/local/PS/local.scv during Desktop Policy installation.

Cause

The Management Server Compiles and distributes only the global file, instead of merging or compiling the per-gateway local.scv_ file and distributing its content to the relevant Security Gateway.

Solution

This problem was fixed. The fix is included in:

• Jumbo Hotfix Accumulator for R82.10 starting from Take 19
• Jumbo Hotfix Accumulator for R82 starting from Take 103
• Jumbo Hotfix Accumulator for R81.20 starting from Take 158

If you choose not to upgrade, Check Point can supply a Hotfix. Contact Check Point Support to get a Hotfix for this issue.

A Support Engineer will make sure the Hotfix is compatible with your environment before providing the Hotfix.

For faster resolution and verification, please collect CPinfo files from the Security Management Server and Security Gateways involved in the case.

Hotfix installation instructions:

Refer to sk168597 - How to install a Hotfix.

NOTE

This solution has been verified for the specific scenario, described by the combination of Product, Version and Symptoms. It may not work in other scenarios.

Article Properties

Access Level: General

Status: Approved by TAC

Date Created: 2026-03-31

Last Modified: 2026-07-23