Why are automated configuration backups important?+
Automation eliminates human error and ensures backups happen consistently. Without automation, backups are often forgotten, leading to extended downtime during outages when no recent configuration is available.
How does rConfig back up configs from multi-vendor devices?+
rConfig uses SSH, Telnet and APIs to connect to devices. It supports CLI commands for legacy devices (like Cisco IOS, Juniper Junos) and API calls for modern infrastructure (Palo Alto, Meraki), normalising the process across all vendors.
Is configuration data encrypted?+
Yes. rConfig encrypts configuration data at rest and in transit, ensuring sensitive information like passwords, keys and architecture details remain secure.
Can I restore a configuration from backup?+
Absolutely. rConfig provides a restore workflow allowing you to push a specific version of a configuration back to a device directly from the dashboard.
Does rConfig support versioning and rollback?+
Yes. Every time a backup runs, rConfig compares it to the previous version. If changes are detected, a new version is created. You can view diffs between versions and roll back to any previous point in time.
How does rConfig ensure compliance with ISO/NIST/CIS frameworks?+
rConfig provides an auditable history of all configuration changes, centralised secure storage and policy enforcement. This helps satisfy the configuration management controls found in frameworks like the NIST Cybersecurity Framework, CISA's compliance resources and the EU's NIS2 Directive.