Planning for Compliance Rules

Before you define and assign compliance rules, do these planning steps:

1. Identify the applications, files, registry keys, and process names that are required or not permitted on endpoint computers.

2. Collect all information and Remediation files necessary for user compliance. Use this information when you create Remediation objects to use in compliance rules.

   Compliance Check Point Software Blade on a Management Server to view and apply the Security Best Practices to the managed Security Gateways. This Software Blade includes a library of Check Point-defined Security Best Practices to use as a baseline for good Security Gateway and Policy configuration. rules can prevent users from accessing required network resources when they are not compliant. Think about how to make it easy for users to become compliant.

3. Make sure that the Firewall rules gives access to Remediation resources. For example, sites from which service packs or Anti-virus updates can be downloaded.

   Note - In Windows 7, make sure the Interactive Service Detection service is running. This is necessary for Remediation files (running with system credentials) that must interact with the user.

4. Define rule Set of traffic parameters and other conditions in a Rule Base (Security Policy) that cause specified actions to be taken for a communication session. alerts and login policies to enforce the rules after deployment.