Network Configuration Rollback and Version Control
Every change is a version. Every version is a rollback point. ConnectMyAssets tracks the complete lifecycle of every configuration change across your entire fleet: who changed it, what changed, and a one-click path back to any previous state in seconds.
- ✓One-click rollback to any previous configuration version
- ✓Full change attribution: CLI, API, workflow, or unauthorized
- ✓Pre-rollback diff preview before any change is applied
- ✓Approval workflows for sensitive devices and environments
- ✓Immutable audit trail for NIS2, DORA, ISO 27001
- ✓Scheduled rollback or immediate emergency rollback
Backup Stores. Version Control Governs.
Most teams have a configuration backup solution. Very few have version control. The difference is governance. A backup tells you what the config looked like at a given point. Version control tells you who changed it, why, whether it was authorized, and gives you a safe, audited, pre-approved path back. When a firewall rule change causes an outage at 03:00, you do not want to paste a config from a text file over SSH. You want one click, a diff preview, and confirmation that the device is running the right config, with a log entry proving what happened. That is what rollback and version control provides.
The Complete Configuration Change Lifecycle
From change detection to rollback confirmation, every step is tracked, auditable, and under your control.
One-Click Rollback to Any Version
Select any version from the configuration history, review the diff, confirm, and ConnectMyAssets queues the target configuration on the appliance. The device connects to the CMA appliance on its next polling cycle and fetches the target configuration, applying it within seconds. No CLI, no copy-paste, no risk of introducing new typos during a stressful incident. The rollback is treated as a new version entry, with full logging, so the entire sequence is traceable in your audit trail.
Full Change Attribution
Every version in the history knows exactly who created it: a direct CLI session, an API call, a ConnectMyAssets workflow, or an unauthorized out-of-band change. Each entry is timestamped and carries the change reason if provided. When an incident occurs, you can immediately identify who made the change, from where, and at what time, without having to cross-reference logs from multiple systems.
Pre-Rollback Diff Preview
Before confirming a rollback, ConnectMyAssets shows you the exact lines that will be added, removed, or modified on the device. A rollback is not a blind restore: it is a controlled change with a full preview. You can see whether the target version contains the fix you need, without accidentally reverting unrelated improvements made since that version. Review, confirm, and execute with full visibility.
Approval Workflow
For critical devices or environments, rollbacks can require approval before execution. An operator proposes the rollback, a team lead or security manager reviews the diff and approves or rejects it. This enforces separation of duties: the person who identifies the problem is not the same person who authorizes the fix in production. Approval decisions are logged with the approver identity and timestamp.
Immutable Audit Trail
Every rollback is itself versioned and logged. The audit trail records what version was restored, who requested it, who approved it, when the device applied it, and whether the restore succeeded. This chain of custody is visible in the compliance dashboard and exportable for NIS2, DORA, and ISO 27001 audits. Because every rollback creates a new version entry, the history is never rewritten and always reconstructable.
Scheduled and Emergency Rollback
Need to revert a change during a maintenance window tonight? Schedule the rollback for 02:00 and let ConnectMyAssets execute it automatically. Dealing with an active outage right now? Execute an emergency rollback immediately from the incident view, no scheduling required. Both modes are available from the same interface, with the same diff preview and the same audit logging regardless of urgency.
How It Works
Change Happens (Planned or Unauthorized)
ConnectMyAssets automatically captures every configuration change as a new version. Whether the change came through an approved workflow, a direct CLI session by an engineer, or an unauthorized modification detected via syslog, the platform stores the full configuration snapshot, calculates the diff from the previous version, and records the source and timestamp. Every change becomes a version in the history immediately.
Compare and Decide
Open the version history for the affected device. Select any two versions to compare: the current running config versus an hour ago, or last week's known-good state versus today. The diff viewer highlights every line that was added, removed, or modified, with syntax highlighting for the device vendor. You can immediately identify which change broke something and which version you want to restore to.
Rollback in Seconds
Click "Rollback to this version", review the pre-rollback diff, and confirm. If an approval workflow is configured, the request is sent to the approver immediately. Once approved, or if no approval is required, ConnectMyAssets stages the target configuration on the appliance. The device connects to the CMA appliance on its next polling cycle, fetches the target configuration, and applies it. The running config is verified against the restored version. The rollback is logged as a new version entry, and your team is notified of the successful restore.
Related Platform Features
Frequently Asked Questions
Common questions about network configuration rollback and version control
Restore Any Device to Any State in Seconds
Stop treating rollbacks as risky manual operations. ConnectMyAssets turns every configuration backup into a governed rollback point with diff preview, approvals, and a full audit trail.