Loading...
Loading...
SCV checks that are defined in per-gateway `local.scv` files on the Security Management Server are not enforced.;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.
Due to a code logic issue in the Security Management Server’s Desktop Policy / SCV compilation process, per-gateway SCV definition files are not processed and propagated correctly during policy installation. Instead of merging or compiling the per-gateway `local.scv_<gateway_name>` file and distributing its content to the relevant Security Gateway, the Management Server Compiles and distributes only the global file.
Click on a version to see all relevant bugs
Check Point Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.