Prove a network device can be rebuilt from a known-good configuration

Source facts: known-good material supports secure device restoration

CISA’s Disable Cisco Smart Install Feature (CM0014) is a countermeasure for a specific legacy Cisco provisioning feature, not a general network-backup standard. CISA says Smart Install can be abused to access, copy, or poison startup configuration files or modify Cisco IOS. When administrators determine that a device was abused, the guidance says to isolate it and restore its image and configuration to a secure state; that may include a known-good configuration backup, a factory reset, and current vendor patches. It also says to preserve a tampered configuration or other evidence during investigation.

NIST SP 800-128 describes baselines, change control, configuration monitoring, and the preservation of approved configuration information. CISA’s communications-infrastructure hardening guidance emphasizes secure management, centralized logging, visibility, backups, and preparation for recovery from unauthorized change.

A text export alone may not recreate the device. Recovery can depend on compatible hardware, bootloader and firmware, feature licenses, certificates and private keys, secret values omitted from exports, identity services, routing neighbors, controller state, cloud entitlements, cabling, upstream configuration, time, DNS, and vendor-specific restore behavior. A successful command import also does not prove that production services or security controls work.

DSE recommendation: test a full device recovery package

Choose representative critical devices and prove the rebuild in an isolated environment or approved maintenance exercise. Treat every discovered dependency as a corrective action, not an informal note.

1. Define the recovery target. Record device role, critical services, site, hardware and module identifiers, software train, desired recovery time, acceptable data loss, configuration owner, support status, and approved replacement models. Prioritize devices that are single points of failure or trust boundaries.
2. Assemble the package. Preserve startup and running configuration, firmware and hashes, boot variables, licenses or entitlement steps, certificates and renewal details, secrets through an approved vault, inventory, diagrams, port mapping, dependencies, console settings, recovery contacts, and a dated known-good reference.
3. Protect the evidence. Encrypt sensitive backups, separate backup administration from device administration, use immutable or offline copies where appropriate, log access, restrict exports, and verify integrity. Keep recovery material available when normal identity, DNS, network, or cloud control planes are down.
4. Start from a clean state. Use spare or lab hardware that represents the production class, or a vendor-supported virtual equivalent when it can test the required behavior. Follow the documented initialization path, install the intended firmware, restore entitlement, and import configuration without hidden technician shortcuts.
5. Validate management. Test console access, named administrator authentication, AAA fallback, role authorization, time, DNS, certificate trust, management routing, configuration archive, logging, monitoring, backups, and alert delivery. Confirm default accounts and unexpected services are not left active.
6. Validate forwarding and policy. Exercise representative VLANs, routes, redundancy, VPNs, NAT, access policy, inspection, quality of service, multicast, wireless, or load-balancing functions relevant to the device. Confirm failover and recovery rather than testing only a ping to the management address.
7. Record and repeat. Capture elapsed time, manual decisions, failed steps, unavailable files, incompatible commands, missing secrets, vendor dependencies, and business tests. Update the package and runbook, retest unresolved gaps, and schedule another exercise after material hardware, firmware, identity, licensing, or topology change.

Factual boundary: A lab rebuild reduces uncertainty but cannot reproduce every production dependency, traffic pattern, carrier condition, or latent hardware fault. Vendor procedures differ, and some backups are not portable across models or software versions. Confirm support and change requirements for the exact platform.

Measure configuration-backup success, integrity verification, recovery-package completeness, tested device classes, rebuild time, manual steps, missing dependencies, business-test pass rate, and age of the last exercise. The meaningful claim is not “we back up the switches.” It is “we have recently rebuilt this class of device from protected material and verified the services it must restore.”

Official references

• CISA, Disable Cisco Smart Install Feature, Countermeasure CM0014.
• NIST, Guide for Security-Focused Configuration Management of Information Systems, SP 800-128 Update 1.
• CISA, Enhanced Visibility and Hardening Guidance for Communications Infrastructure.