Start with one critical device
When branch recovery depends on the last engineer remembering a change, service continuity depends on personal memory. JOTOglobal suggests starting with one switch, router or firewall whose business role is clear. Create a small handover package covering purpose, business owner, maintenance contact, configuration version and recovery access procedure. Do not put plaintext passwords in that register. Complete and maintain one handover before extending the approach to comparable locations.
Define where the trusted baseline lives
The joint communications-infrastructure guidance published by CISA recommends centrally held configurations and investigation of changes outside the change process. It primarily addresses communications infrastructure and also notes relevance to on-premises enterprise equipment. For implementation, assign each baseline a version, approver and device scope. A fresh device export should not automatically become the accepted baseline. Successful backup and correct configuration are separate questions; someone must confirm that a new baseline matches an accepted business change.
Route differences to an accountable owner
Link each difference to a ticket, operator, time window and expected impact. Check whether it represents a planned change, an emergency action or an undocumented adjustment before deciding the response. Do not automatically overwrite the running configuration merely because it differs from the baseline: a remote branch could lose access. Give unexplained differences a response deadline and escalation contact. When a change is accepted, validate it and update the baseline so that monitoring remains meaningful.
Prove recovery with a bounded drill
Choose a maintenance window and a low-risk pilot. Check whether the owner can find the correct version, follow the recovery instructions and restore the agreed business function within the target time. Set stop conditions, on-site assistance and communications in advance. Record actual duration, failed steps and missing information. Possessing a configuration file is not proof of readiness to recover. These are JOTOglobal operational suggestions; device-specific recovery commands must follow vendor documentation and organizational authorization.
Source
CISA — Enhanced Visibility and Hardening Guidance for Communications Infrastructure
https://www.cisa.gov/resources-tools/resources/enhanced-visibility-and-hardening-guidance-communications-infrastructure