All Configuration Changes History Report

The All Configuration Changes History report in Site24x7's Network Configuration Manager (NCM) gives administrators a consolidated view of every configuration version captured across monitored network devices. For each recorded version, the report shows whether it applies to the device's startup or running configuration, the version number, the type of change, and the date it was captured. Use this report to track authorized configuration updates, detect unauthorized modifications, and maintain a reliable change history for audit and compliance purposes.

Use cases

• Track all configuration changes made to network devices across your infrastructure.
• Identify unauthorized configuration modifications that may indicate a security or operational risk.
• Maintain a complete, timestamped change log for compliance, audit trails, and change management.
• Plan configuration rollbacks by reviewing the version history before restoring a prior state.

Generating the report

1. Log in to your Site24x7 account.
2. Navigate to Reports > NCM Device > Configuration Change History Report.
3. The report loads with all recorded configuration versions listed by default.
4. Use the Group by drop-down menu to organize results by configuration type (for example, select Type to separate Startup and Running configurations).
5. Click Add Filters to narrow results by device name, version number, change type, or capture date.
6. Click any sortable column header to sort records in ascending or descending order.
7. Click Share This to export the report as a CSV or PDF file, email it, or schedule it to be generated at regular intervals.

Report columns

The report displays the following columns for each configuration record.

Best practices

• Group by Type to check for startup-running conflicts: Compare the Startup and Running groups to identify devices where the running configuration has not been saved to startup. A reboot on such a device would revert to an earlier configuration state.
• Review unauthorized changes immediately: Investigate changes and determine whether a rollback is required if the Change Type column shows an unexpected value for a device you did not intend to modify.
• Don't ignore version numbering: Use version numbers to track change frequency. A rapidly incrementing version number for a single device may indicate automated or uncontrolled configuration changes that warrant investigation.
• Cross-reference with the Operations History report: Use the Operations History report alongside this report to confirm that a configuration change was accompanied by a corresponding backup or push operation.
• Schedule exports for your change management process: Use the Share This option to deliver regular configuration change exports to your change management team, ensuring every modification is documented and reviewed.

Related articles

• NCM reports
• Startup-running conflict report
• Operations History report
• Firmware Version History report