# Should we back up the configuration of firewalls, switches and routers?

Yes, and it is often forgotten. Network devices hold configuration that took years to build: firewall rules, VPN settings, VLANs, routing and access lists. If a firewall fails, is wiped by an attacker or has to be replaced after a compromise, rebuilding that configuration from memory takes days and usually introduces mistakes. Export the configuration automatically after every change and at least weekly, store the copies outside the devices themselves, ideally in version control so that you can see what changed and when, and keep at least one copy offline. Protect the exports, because they contain sensitive details and sometimes credentials or keys. A configuration history also has a security benefit: an unexpected new rule, account or port forward is a classic sign that someone has tampered with an edge device. Include restoring a device configuration in your recovery tests, ideally onto a spare unit.

FAQ: [Backups and recovery](https://netsenx.com/en/faq/backups) · https://netsenx.com/en/faq/should-we-back-up-network-device-configurations

## Read next

- https://netsenx.com/en/detect-ransomware-on-the-network
- https://netsenx.com/en/blog/2026-10-24_ransomware-protection

## Related questions

- [Is a snapshot a backup?](https://netsenx.com/en/faq/is-a-snapshot-a-backup)
- [What is the 3-2-1 backup rule?](https://netsenx.com/en/faq/what-is-the-3-2-1-backup-rule)
- [What is an immutable backup?](https://netsenx.com/en/faq/what-is-an-immutable-backup)
- [What is an offline or air-gapped backup?](https://netsenx.com/en/faq/what-is-an-offline-or-air-gapped-backup)
- [How often should we test a restore?](https://netsenx.com/en/faq/how-often-should-we-test-a-restore)