Firewall backup
To support recovery after failure or natural disaster, a firewall, like any other network host, has to have some policy-defining system backup. Data files and system configuration files need to have some backup plan in case of firewall failure.
Tip The firewall (system software, configuration data, database files, etc.) should be backed up daily, weekly, and monthly so that in case of system failure, data and configuration files can be recovered. Backup files should be stored securely on a read-only media so data in storage are not overwritten inadvertently, and they should be locked up so that the media is only accessible to the appropriate personnel.
Another backup alternative is to have another firewall configured as the one already deployed. This firewall would be kept safe so that if there is a failure of the current one, this backup firewall would simply be turned on and used as the firewall while the previous one is undergoing a repair.
Tip At least one firewall should be configured and reserved (not in use) so that in case of a firewall failure, this backup firewall can be switched on to protect the network.
In this tutorial:
- Firewall Security Policy
- Firewall protection
- Firewall architectures
- Multi-homed host
- Screened host
- Screened subnet
- Types of firewalls
- Packet-filtering gateways
- Application gateways
- Hybrid or complex gateways
- Routing versus forwarding
- IP spoofing
- DNS and mail resolution
- Intranet
- Network trust relationships
- Virtual private networks
- Qualification of the firewall administrator
- Remote firewall administration
- Firewall backup
- System integrity
- Physical firewall security
- Firewall incident handling
- Upgrading the firewall
- Revision/update of firewall policy
- Examples of service-specific policies
