Compliance Reporting
Audit and verify your network for configuration compliance.
Last updated
Was this helpful?
NSO 6.5
Audit and verify your network for configuration compliance.
Last updated
Was this helpful?
When the network configuration is broken, there is a need to gather information and verify the network. NSO has numerous functions to show different aspects of such a network configuration verification. However, to simplify this task, compliance reporting can assemble information using a selection of these NSO functions and present the resulting information in one report. This report aims to answer two fundamental questions:
Who has done what?
Is the network correctly configured?
What defines a correctly configured network? Where is the authoritative configuration kept? Naturally, NSO, with the configurations stored in CDB, is the authority. Checking the live devices against the NSO-stored device configuration is a fundamental part of compliance reporting. Compliance reporting can also be based on one or a number of stored templates which the live devices are compared against. The compliance reports can also be a combination of both approaches.
Compliance reporting can be configured to check the current situation, check historical events, or both. To assemble historical events, rollback files are used. Therefore this functionality must be enabled in NSO before report execution, otherwise, the history view cannot be presented.
The reports are stored in a SQLite database file and can be exported to plain text, HTML or DocBook XML format. The report results can be re-exported to a new format at any time. The DocBook XML format allows you to use the report in further post-processing, such as creating a PDF using Apache FOP and your own custom styling. Every consecutive run of the report is stored in the same SQLite database. This allows for comparing the report results over time and one such comparison is available in the Web UI. The previous behavior before NSO 6.5 of getting one SQLite file per report run is available by setting common-db under the report definition to false.
It is possible to create several named compliance report definitions. Each named report defines the devices, services, and/or templates that should be part of the network configuration verification.
Let us walk through a simple compliance report definition. This example is based on the example. For the details of the included services and devices in this example, see the README file.
Each report definition has a name and can specify device and service checks. Device checks are further classified into sync and configuration checks. Device sync checks verify the in-sync status of the devices included in the report, while device configuration checks verify individual device configuration against a compliance template (see ).
For device checks, you can select the devices to be checked in four different ways:
all-devices - Check all defined devices.
device-group - Specified list of device groups.
device - Specified list of devices.
select-devices - Specified by an XPath expression.
Consider the following example report definition named gold-check:
This report definition, when executed, checks whether all devices known to NSO are in sync.
For such a check, the behavior of the verification can be specified:
To request a check-sync action to verify that the device is currently in sync. This behavior is controlled by the leaf current-out-of-sync (default true).
To scan the commit log (i.e. rollback files) for changes on the devices and report these. This behavior is controlled by the leaf historic-changes (default true).
For the example gold-check, you can also use service checks. This type of check verifies if the specified service instances are in sync, that is if the network devices contain configuration as defined by these services. You can select the services to be checked in four different ways:
all-services - Check all known service instances.
service - Specified list of service instances.
select-services - Specified list of service instances through an XPath expression.
service-type - Specified list of service types.
For service checks, the verification behavior can be specified as well:
To request a check-sync action to verify that the service is currently in sync. This behavior is controlled by the leaf current-out-of-sync (default true).
To scan the commit log (i.e. rollback files) for changes on the services and report these. This behavior is controlled by the leaf historic-changes (default true).
In the example report, you might choose the default behavior and check all instances of the l3vpn service:
Compliance reporting is a read-only operation. When running a compliance report, the result is stored in a file located in a sub-directory compliance-reports under the NSO state directory. NSO has operational data for managing this report storage which makes it possible to list existing reports.
Here is an example of such a report listing:
There is also a remove action to remove report results (and the corresponding file):
When running the report, there are a number of parameters that can be specified with the specific run action.
The parameters that are possible to specify for a report run action are:
title: The title in the resulting report.
from: The date and time from which the report should start the information gathering. If not set, the oldest available information is implied.
to: The date and time when the information gathering should stop. If not set, the current date and time are implied. If set, no new check-syncs of devices and/or services will be attempted.
outformat: One of xml, html, text, or sqlite. If xml is specified, the report will formatted using the DocBook schema.
We will request a report run with a title and formatted as text.
In the above command, the report was run without a from or a to argument. This implies that historical information gathering will be based on all available information. This includes information gathered from rollback files.
When a from argument is supplied to a compliance report run action, this implies that only historical information younger than the from date and time is checked.
When a to argument is supplied, this implies that historical information will be gathered for all logged information up to the date and time of the to argument.
The from and a to arguments can be combined to specify a fixed historic time interval.
When a compliance report is run, the action will respond with a flag indicating if any discrepancies were found. Also, it reports how many devices and services have been verified in total by the report.
Below is an example of a compliance report result (in text format):
Often, each device will have a somewhat different configuration, such as its own set of IP addresses, which makes checking against a static template impossible. For this reason, NSO supports compliance templates.
These templates are similar to but separate from, device templates. With compliance templates, you use regular expressions to check compliance, instead of simple fixed values. You can also define and reference variables that get their values when a report is run. All selected devices are then checked against the compliance template and the differences (if any) are reported as a compliance violation.
You can create a compliance template from scratch. For example, to check that the router uses only internal DNS servers from the 10.0.0.0/8 range, you might create a compliance template such as:
Here, the value of the /sys/dns/server must start with 10., followed by any string (the regular expression .+). Since a dot has a special meaning with regular expressions (any character), it must be escaped with a backslash to match only the actual dot character. But note the required multiple escaping (\\\\) in this case.
As these expressions can be non-trivial to construct, the templates have a check command that allows you to quickly check compliance for a set of devices, which is a great development aid.
To simplify template creation, NSO features the /compliance/create-template action that can initiate a compliance template from a set of device configurations or an existing device template. The resulting template can be used as-is or as a starting point for further refinement. For example:
By providing a list of device configuration paths, the create-template action can find common structural patterns in the device configurations and create a compliance template based on it.
The algorithm works by traversing the data depth-first, keeping track of the rate of occurrence of configuration nodes, and any values that compare equal. Values that do not compare equal are made into regex match-all expressions. For example:
The action takes a number of arguments to control how the resulting template looks:
path - A list of XPath 1.0 expressions pointing into /devices/device/config to create the template from. The template is only created from the paths that are common in the node-set.
match-rate - Device configuration is included in the resulting template based on the rate of occurrence given by this setting.
exclude-service-config - Exclude configuration that is already under service management.
collapse-list-keys - Decides what lists to do matching on, either all, automatic (default), or those specified by the list-path parameter. The default is to find those lists that differ among the device configurations.
Finally, to use compliance templates in a report, reference them from device-check/template:
In addition to configuration, compliance templates can also check for operational data. This can be used, for example, to check device interface statuses and device software versions.
When running a check against a device, the result will show a violation if the status of the interface link is not up.
In some cases, it is insufficient to only check that the required configuration is present, as other configurations on the device can interfere with the desired functionality. For example, a service may configure a routing table entry for the 198.51.100.0/24 network. If someone also configures a more specific entry, say 198.51.100.0/28, that entry will take precedence and may interfere with the way the service requires the traffic to be routed. In effect, this additional configuration can render the service inoperable.
strict ChecksTo help operators ensure there is no such extraneous configuration on the managed devices, the compliance reporting feature supports the so-called strict mode. This mode not only checks whether the required configuration is present but also reports any configuration present on the device that is not part of the template.
You can configure this mode in the report definition, when specifying the device template to check against, for example:
Consider the following template and device configuration:
The device will be compliant with a regular template check. When using strict, all unexpected configuration will be shown in the diff.
strict Sub-Tree TagIn the previous example, the strict check shows interfaces that are not mentioned explicitly in the template. This is because strict is applied to the entire tree, including everything under interface. In order to only have strict on certain parts of the tree, a tag can be used.
After adding the strict tag to interface GigabitEthernet, running the check will result in a strict check against everything below GigabitEthernet.
allow-empty TagA compliance template can be used on many different devices. The configuration on the devices, however, is not always identical. The following template checks that interfaces are set to be reachable.
The device in this example only has a GigabitEthernet interface which will result in a violation.
In this case, we are only interested in interfaces that are actually configured on the device. This is where the allow-empty tag comes in. By setting this tag on each interface, the check will only be run if there are interfaces configured of that type.
With this tag, the device will no longer have any violations.
It will still result in violations if the configuration is incorrect, but not if it's empty.
absent TagIn order to ensure that configuration does not exist on a device, the absent tag can be used.
This template will result in a violation if service finger is configured on the device.
You can also use the web UI to define compliance reports. See the section for more information.
Services are the preferred way to manage device configuration in NSO as they provide numerous benefits (see in Development). However, on your journey to full automation, perhaps you only use NSO to configure a subset of all the services (configuration) on the devices. In this case, you can still perform generic configuration validation on other parts with the help of device configuration checks.
This feature is opt-in and requires the NEDs to be re-compiled with the --ncs-with-operational-compliance flag. Instructions on how to re-compile a NED is included in each NED package.