Submit a ticketCall us

ebook60.pngHow to be a Cisco® ASA ace

Our eBook, Thou Shalt Not Pass…I Think?! can help you overcome the challenges of monitoring and managing Cisco ASA firewalls. This eBook is a great read if you’ve been frustrated with monitoring firewalls, managing ACL configs, and troubleshooting VPN connections.

Get your free eBook.

Home > Success Center > Network Configuration Manager (NCM) > NCM 7.7 Administrator Guide > Policy reports

Policy reports

Created by Caroline Juszczak, last modified by Anthony.Rinaldi_ret on Oct 03, 2016

Views: 857 Votes: 3 Revisions: 5

Policy reports help ensure that device configurations conform to both internal business practices and federal regulations, such as the Sarbanes-Oxley Act (SOX), Health Insurance Portability and Accountability (HIPAA), and Computer Inventory of Survey Plans (CISP). You might also want to use the Payment Care Industry (PCI) data security policies, and Defense Information Systems Agency Security Technical Implementation Guide (DISA STIG) reports to monitor compliance.

For more information about generating DISA STIG policy reports, see Configuring DISA STIG reports.

Policy reports scan configuration files and report any discovered rule violations. For example, a rule may require that configurations do not include the read-only community string "public." You can run a report on your configuration files, and then display any configurations that violate the rule. Your policy report includes the line number where the violation occurred in the listed violations. Several example reports, policies, and rules are included with SolarWinds Network Configuration Manager.

If you decide to create policy reports, understand Rules that define the criteria, such as pattern strings, applied in Policies used by NCM to determine compliance.

Create a policy report

The NCM predefined reports may not fit your exact needs for monitoring compliance of a particular device. You can create a policy report and select policies available in NCM or create your own policies and add them to the report.

  1. Click My Dashboards > Configs > Compliance.
  2. Click Manage Policy Reports.
  3. Click Add New Report.
  4. Name the report, and enter a description.
  5. Select settings for Save in Folder and Display Settings.
  6. Select policies from folders under All Policies, and click Add. If your policy is not listed, see Create a policy.
  7. Click Submit.

Schedule a policy report

  1. Click My Dashboards > Configs > Jobs.
  2. Click Create New Job.
  3. Name the job, and select Generate a Policy Report from Job Type.
  4. Select the Schedule Type. If you are creating an Advanced schedule, use the five fields to create an appropriate cron expression.
  5. Add a comment if this job relates to a business rule, and click Next.
  6. On the Choose Nodes tab, click Next.
  7. Select an email notification option, and click Next. If you click Email Results, the default settings are populated. These settings can be overridden in each job.
  8. Select the policy report to generate as part of the job.
  9. If you want to suppress notifications when no violations are found, select Send Notification Only When There Are Policy Violations.
  10. Click Next.
  11. Review the settings for the job, and click Finish.

Remediate a policy report

  1. Click My Dashboards > Configs > Compliance.
  2. Click a report in the list to view it.
  3. Click a rule or violation icon to display the Violation Details.
  4. Click View Config to see the config file for the node.
  5. Click a Management option to execute a remediation script on this node or all nodes in violation.
  6. In the Execute {ReportName} Remediation Script resource, enter or modify the script so that it includes commands that will be accepted by your device.
  7. To review or modify the nodes against which your script will run, click Select Nodes.
  8. Click Execute Script.

Export a policy report to THWACK

  1. Click My Dashboards > Configs > Compliance.
  2. Click Manage Policy Reports.
  3. Select a report, and click Export to thwack.
  4. If prompted, enter your user name and password, and then Log In.

Export a policy report as a file

  1. Click My Dashboards > Configs > Compliance.
  2. Click Manage Policy Reports.
  3. Select a report, and click Export as File.
  4. Verify that a pop-up blocker does not prevent the file from being downloaded.
  5. Download the file to a local folder.

Edit a policy report

  1. Click My Dashboards > Configs > Compliance.
  2. Click Manage Policy Reports.
  3. Select a report, and click Edit.
  4. Edit the appropriate values.
  5. Click Submit.

Delete a policy report

  1. Click My Dashboards > Configs > Compliance.
  2. Click Manage Policy Reports.
  3. Select a report, and click Delete.
  4. Click Yes.

Configure DISA STIG compliance reports

SolarWinds NCM provides for compliance checks of your devices with DISA standards. The Defense Information Systems Agency Security Technical Implementation Guides (DISA STIG) reports are available in your NCM installation. To run the reports that specify the appropriate policies for your devices, make sure that you have first defined the node "Device_Type" in custom properties for your device type.

For example, for Cisco devices, specify the Device_Type and OS in custom properties with the following options:

Device Types:


OS types supported:


Likewise, for F5 devices, specify the Device_Type in custom properties.

Create a DISA STIG dashboard

You can set up a dashboard specifically to monitor compliance. To create a DISA STIG compliance dashboard, see the complete details in How to Create a DISA STIG Dashboard on THWACK.

Enable the policy cache

  1. Click Settings > All Settings.
  2. Under Product Specific Settings, click NCM Settings.
  3. Under Advanced, click Advanced Settings.
  4. Under Cache Settings, select Enable Config and Policy Caches.
  5. Click Submit.

Manually refresh the policy cache

  1. Click My Dashboards > Configs > Compliance.
  2. Click Update All.

When you run a policy report or a scheduled job from SolarWinds NCM, the data returned is a snapshot of current policy compliance and does not rely on the policy cache. 


Last modified