rConfig - New Compliance Policy Experience

5 mins V7 Pro

We’ve completely revamped the compliance engine in V7 to make it more modular, flexible, and user-friendly. Here’s a quick breakdown of the key updates and how to use the new policy definition and compliance workflow:

Key Principles of the New Compliance Engine:

1. Policy Definition: A policy is now a collection of rules, giving you complete control over how compliance is defined.
2. Policy-Based Rules: The rules, and how they are applied, are defined in an easy-to-edit custom rCondig Policy file, making the system flexible and customizable to your needs.
3. In-App Help: Detailed help is available directly in the app, guiding you through the process of designing and implementing your own rules.

New and Improved User Experience:

• Policy Assignment: Assign a policy definition to a Scope (which could be a category, device, or tag) to control how compliance is checked.
• Flexible Scopes: Policy assignments are based on the available scopes, commands, and configurations—tailoring your compliance checks to your specific needs.
• Compliance Checks: Once assigned, the compliance output will show the latest results of your policy check.

Scheduled Tasks and Manual Checks:

• Compliance jobs can be configured in Scheduled Tasks, allowing for manual runs via the UI or automatic checks at specified intervals.
• Step-by-Step:
  1. Write your Policy Definition.
  2. Create a Policy Assignment.
  3. Set up a Scheduled Task to run compliance checks at your preferred times.

No Direct Device Connection:

The compliance engine checks the latest downloaded config from your devices but never connects directly to them. This ensures the system remains secure while performing compliance checks on the most recent configuration data.

By focusing on flexibility and ease of use, V7 Pro’s new compliance engine gives you more control while streamlining the overall experience for both seasoned pros and new users alike.

Watch the Webinar: