The Compliance Audit tool allows you to create standards and tests used to compare with configured devices . By completing a Compliance Audit, prior to submission, approval, and sending changes to a device, you are able to:  

  • Standardize and validate deployed configurations in the network

  • Find and fix variations in the network

  • Define a compliance standard

  • Apply a standard check against any existing device config file

  • Report variations from the compliance comparison

A compliance standard consists of filters and tests. Filters allow you to define what type of device the standard is used for. A test sets up the pre-conditions and check patterns in the standard.

  • Preconditions specify config commands that must be present before the test is run.

  • Check Patterns is the actual expression that is searched for in the config, and the remedy for the variation.

Based on these details, any standard should follow the rules detailed in the table below.




A standard must contain at least one managed device class.


A test can have multiple steps and each step can have a Begin Withand End With pre-condition, and must contain at least one check pattern.

A Compliance Audit can be launched from a Network, View, Site, Workspace, any of the Editors, or from the Schedule Manager.