Compliance overview

5 mins

V6 ProV6 MSP

Compliance Overview

We have completely re-written the compliance engine to be more modular and flexible. The new engine is based on the following principles:

1. A policy definition is a collection of rules.
2. The rules and how to apply them are defined in a JSON file.
3. There is a detailed help file in the app on how to design and implement the rules.
4. A policy assignment is an assignment of a policy definition to a Scope of category, device or Tag.
5. A policy assignment is an assignment of a policy definition given Scopes available commands/ configs.
6. A policy compliance is an output of the latest check of the policy assignment.
7. A policy compliance jobs are configured in Scheduled Tasks and are either run manually from the UI or at the configured interval.
8. Write a Policy Definition first, then create a Policy Assignment. Then create a Scheduled Task to run the compliance check.
9. The compliance check is run on the devices latest downloaded config for the scope/ command selected in the assignment. The compliance engine does not connect to devices at any time. It only uses the latest downloaded config to run compliance checks.