Network change management tools: backup, detection and approval — OC Security Audit
Configuration backup and change tools

Network change management tools: backup, detection and approval

Configuration backup, change detection and change tickets are three different tools. Together they show what changed, when, who approved it and how to roll it back.

A backup shows what changed. A change ticket shows why. — OC Security Audit
What and why

A backup shows what changed. A change ticket shows why.

Auditors often ask for both. We help you connect the configuration diff to the approved request and the updated documentation.

Your switch backups do not cover your cloud — OC Security Audit
The cloud gap

Your switch backups do not cover your cloud

Device configuration tools stop at routers, switches and firewalls. Cloud network and identity settings need a record of their own.

25+ yearsIT & cybersecurity experience
Certified expertsCISSP · C|CISO · Microsoft · Cisco
Southern CaliforniaLocal and on-site, based in Irvine
NationwideRemote documentation & audits
Start here

What network change management tools actually do

Network change management tools fall into three layers. Configuration backup tools copy router, switch and firewall configurations on a schedule and show the difference between versions. Change detection tools collect settings across many systems and flag what moved. ITSM and PSA change modules hold the request, risk, approval and rollback plan.

None of the three is complete alone. A backup without a ticket shows a change nobody can explain. A ticket without a backup describes a change nobody can verify. The documentation then has to be updated so the next engineer sees the network as it is now.

OC Security Audit is vendor-neutral and does not resell any tool on this page. We review and document how your tools work together, on-site from Irvine across Orange County and Southern California, and remotely nationwide.

Two engineers with laptops checking configuration backups in a data center
Tools by layer

Network change management tools compared by layer

Descriptions come from each project, vendor or a third-party reviewer as of November 2026. No prices: they depend on device counts and contract terms.

LayerToolWhat it does
Configuration backup and driftUnimusOn-premises network configuration management (NCM) that backs up router, switch and firewall configurations.
Configuration backup and driftOxidizedOpen-source (Apache 2.0) network device configuration backup tool, described by its authors as a RANCID replacement. Supports over 130 operating system types and can commit every change to a Git repository.
Configuration backup and driftRANCIDMonitors a device’s configuration, including software and hardware, keeps change history in CVS, Subversion or Git and emails differences to a mailing list.
Configuration backup and driftrConfigNetwork configuration management for multi-vendor environments: automatic backups, change tracking and recovery of earlier versions. Offers an open-source Core edition and commercial tiers.
Configuration backup and driftSolarWinds NCM, ManageEngine Network Configuration ManagerCommercial network configuration managers that back up router, switch and firewall configurations.
Configuration backup and driftBackBoxAutomates backups, recovery, upgrades and patching for network devices, with support for more than 180 vendors.
Change detection across systemsLiongardKeeps up to 18 months of time-stamped configuration change history.
ITSM change moduleServiceNow, Jira Service Management, Freshservice, ManageEngine ServiceDesk Plus, HaloITSM, SysAidIT service management platforms with change management modules, where the request, risk, approval and implementation are recorded.
MSP PSAHaloPSA, Autotask PSA, ConnectWise PSA and similarProfessional services automation for MSPs: service desk tickets, technician time and invoicing. Change tickets often live here when an MSP runs the network.

Listing a tool here is not an endorsement. For documentation platforms, IPAM and discovery tools, see IT documentation software compared.

What each layer answers

Three questions, three kinds of tool

An auditor or an incident review will ask all three. Each layer answers one.

01

What changed?

Configuration backup and drift tools answer this with a line-by-line diff and a timestamp. They also give you a known-good configuration to restore after a failed change or a hardware swap.

02

Was it expected?

Change detection compares current settings with the last snapshot and flags differences. An unexpected difference is either an undocumented change or something worse, and both need a look.

03

Who approved it and why?

The ITSM or PSA change record holds the business reason, risk, approver, test plan and rollback steps. This is the record PCI DSS 1.2.2, ISO 27001 A 8.32 and SOC 2 CC8.1 expect; see the framework mapping.

The cloud gap

Device configuration backups do not capture cloud settings

This is a common gap when an environment is part on-premises and part cloud.

Device-level tools such as SolarWinds NCM, ManageEngine NCM, BackBox, Oxidized, Unimus, rConfig and RANCID back up router, switch and firewall configurations. As ControlMonkey notes, they do not capture cloud network settings such as VPCs or IAM policies. Azure virtual networks and NSGs, AWS security groups and Microsoft 365 Conditional Access policies all change outside those tools.

For Microsoft 365, Microsoft365DSC, an open-source Microsoft project, exports tenant configuration and compares two exports to show the delta. For Azure and AWS, the settings need their own dated record and their own change tickets. Our cloud documentation page covers what to record for Microsoft 365, Entra ID, Azure and AWS.

How it fits together

One change, three records, one trail

The link between records is a shared change ID that appears in the ticket, the backup note and the documentation history.

Request

Ticket with reason, risk and rollback plan

Approve

Named approver, dated, before work starts

Implement

Engineer makes the change in the window

Capture

Backup tool records the before and after diff

Update

Diagram, IP plan or rule register edited

Close

Ticket links the diff and the updated record

Sample

A firewall change traced across all three layers

SAMPLE · Harborview Dental Group (fictional company) · illustrative data
Change ID
CHG-0145
Organization
Harborview Dental Group, second office
Request
Allow second-office PCs (10.21.10.0/24) to reach the imaging vendor’s cloud service on TCP 443
Approved by
Practice administrator, 2026-10-08
Rollback
Remove rule FW-S2-R047 and restore the 2026-10-08 backup
LayerRecordEvidence
Change ticketCHG-0145, closed 2026-10-09Reason, risk, approval, test result
Configuration backupFW-S2-01, 2026-10-09 22:14 snapshotDiff: one rule added, no other lines changed
DocumentationFirewall rule-justification register, row FW-S2-R047Owner, business reason, review date 2027-04-09

A single change ID ties the three records together. The firewall configuration documentation page shows the full rule register.

Selection guide

Questions to ask before you choose change tools

The right answer depends on your devices, who makes changes and where your network lives.

  • Does the backup tool support every firewall, switch, router and wireless controller model you run?
  • Is it on-premises, cloud-hosted or both, and where are the stored configurations kept?
  • Are stored configurations encrypted, and who can read them? Configurations can contain secrets.
  • Does it alert on changes made outside an approved window?
  • Can it show a side-by-side diff and restore an earlier version?
  • Does the change ticket system require approval before work starts, and record the approver?
  • Can a ticket link to the configuration diff and the updated documentation?
  • Who owns the tools and the history if your MSP changes?
  • What covers cloud settings that device tools cannot see?
  • How long is history kept, and does that meet your retention needs?
How we help

We review and document the change process, not just the tools

OC Security Audit does not run your change tools or make changes on your systems. In the read-only IT documentation audit we review whether backups run, whether tickets carry approvals and whether documentation follows each change, and you get a change-process gap list.

In the IT Documentation Build we deliver a change-log template linked to your backup tool and ticket system. Each package is $3,500 fixed, one-time; see IT documentation pricing. For device-level reviews, see our firewall security audit and Cisco configuration backup service. Hands-on setup can go to our implementation partner, IT Perfection.

Engineers reviewing change records on a tablet in a server aisle
Related

Where to go next

IT change management

The change process itself: request, risk, approval, test, rollback and before-and-after records.

IT documentation software

Documentation hubs, IPAM and discovery tools compared by layer.

Ali Hassani, CISO, OC Security Audit
CISO-led

Guided by Ali Hassani, CISO

Certified CISO (C|CISO) and CISSP with 25+ years in IT, cybersecurity, compliance and infrastructure, and dozens of Microsoft and Cisco certifications, including MCSE, MCITP, MCSA Security, CCNP and CCNA. Ali checks the trail from change ticket to configuration diff to updated diagram, the same path an auditor follows.

FAQ

Questions about network change management tools

Is a configuration backup tool enough for change management?

No. It records what changed but not who approved it or why. Pair it with a change ticket that names the approver, the reason and the rollback plan.

Can open-source tools like Oxidized or RANCID meet audit needs?

They can provide configuration history. You are responsible for hosting, securing and backing up the server they run on, and for keeping the ticket and documentation side in step.

Do we need an ITSM platform if we are a small office?

Not necessarily. A simple change log with request, approval, test and rollback fields can work if it is kept consistently. Our change-log template is built for that.

Our MSP makes our network changes. How do we see the records?

Ask for read access to the change tickets and the configuration history for your devices, and confirm in writing that the history belongs to you.

Will you install or configure these tools for us?

No. We document and audit; we do not administer client systems. IT Perfection or your own IT team can handle installation and setup.

Implementation partner

OC Security Audit documents and audits; it stays independent of the administration of your systems. If you want hands-on work, IT Perfection can fix what the documentation uncovers and keep the records current as part of managed IT.

IT Perfection managed IT
Sources

Sources and references

  1. Unimus (TrustRadius)
  2. Oxidized README (GitHub)
  3. RANCID (Shrubbery Networks)
  4. rConfig (rConfig)
  5. BackBox (BackBox)
  6. Network configuration management and the cloud (ControlMonkey)
  7. Audit readiness (Liongard)
  8. ITSM ticketing tools (SupportBee)
  9. Best PSA software for MSPs (Channel Insider)
  10. What is Microsoft365DSC (Microsoft)

Unimus, Oxidized, RANCID, rConfig, SolarWinds, ManageEngine, BackBox, Liongard, ServiceNow, Jira Service Management, Atlassian, Freshservice, HaloITSM, HaloPSA, SysAid, Autotask, ConnectWise, Microsoft 365, Azure, AWS and Microsoft365DSC are trademarks of their respective owners. OC Security Audit is independent and not affiliated with or endorsed by any vendor named on this page.

Three engineers documenting network devices on a laptop in a data center

Make every network change traceable

We review how your backups, tickets and documentation connect, then show you the gaps. Schedule a consultation.

Irvine, Orange County and Southern California on-site; remote nationwide. Fixed one-time price: $3,500.