Cisco Configuration Backup: Every Device, Saved and Redacted
Configuration backup

Cisco Configuration Backup: Every Device, Saved and Redacted

If a switch died tonight, could you rebuild it tomorrow? The audit saves every running configuration and tells you which changes were never saved.

25+ yearsIT & cybersecurity experience
Certified expertsCISSP · C|CISO · Microsoft · Cisco
Southern CaliforniaLocal and on-site, based in Irvine
NationwideRemote audits & advisory
Schedule a consultation
Page 2 of 11 in the Cisco Network Security Audit series · Start at page 1

Why the backup comes first

A Cisco device runs from its running configuration but boots from its startup configuration. When someone makes a change and never saves it, the next power cut quietly undoes it. Many networks also have no copy of the configuration anywhere off the device. The first thing the audit does is fix that: one dated backup of every device, taken read-only.

Two network engineers checking a Cisco switch configuration backup in a server room

What we save for every device

Running configuration

show running-config as the device runs right now, saved as a dated text file per device.

Startup configuration

show startup-config, what the device will load after a reboot, saved alongside it.

Saved or not

Running and startup are compared. Any difference becomes a finding: changes that will be lost at the next reload.

Redacted copy

A second copy with passwords, secrets, keys and SNMP communities removed, safe to send to an MSP or auditor.

Inventory

Model, serial number, software version, uptime and modules from show version and show inventory.

Coverage log

Every command sent, whether it worked, and which checks became Manual review when a command was not supported.

What the collector sends, and what it never sends

Sample session · IOS / IOS XE (subset)
terminal length 0
show version
show running-config
show startup-config
show inventory
show ip interface brief
show cdp neighbors detail
show lldp neighbors detail
show vlan brief
show ntp status
show ip ssh

Refused before it leaves the laptop

A command guard accepts only show, dir, terminal paging commands and a bare enable. It refuses configure, write, copy, reload, clear, debug, delete, erase, install and boot, chained commands and redirects.

The collector does not even import the library functions that push configuration. A separate verification script scans the code and replays the session log to prove it.

How backups are handled

CopyContainsWhere it goes
Full backupEverything, including password hashes, keys and SNMP communitiesHanded to you for your secure store; never in the shared report
Redacted backupThe full configuration with secrets replacedIncluded with the technical report; safe to share with your MSP
Session evidenceRaw command output in replay formatKept so the reports can be rebuilt without logging in again

Device passwords are passed to the collector in memory only and are never written to disk.

From the sample report

Sample · Calloway Bend Logistics (fictional company) · illustrative data
Check
Configuration saved (management plane)
Finding
3 devices have unsaved changes; the core switch differs by 41 lines
Severity
Medium
Evidence
Running and startup configurations differ on CBL-CORE-01, CBL-ACC-02 and CBL-FW-01. On CBL-CORE-01 the new VLAN 40 and its ACL exist only in memory.
Fix
Review the differences, then copy running-config startup-config (or write memory), and turn on archive so every save is also copied off the device.

Questions about configuration backups

Do you copy files off our devices?

No. Nothing is copied with copy or TFTP. We read the configuration on screen with show commands and save that output on our side.

Will we get the full backups?

Yes. The full backups are yours. Because they contain password hashes and keys, they are delivered separately from the report, and the report itself includes only redacted copies.

Can we keep doing this after the audit?

Yes. The how-to guide shows how to turn on automatic archiving on IOS and IOS XE, and the audit can be repeated as a follow-up comparison.

Get a backup of every Cisco device

One read-only session, every configuration saved, every unsaved change flagged. $3,500 fixed for the full audit.

Read-only audit. No changes to your devices. Irvine, Orange County and Southern California on-site; remote nationwide.