Secure Backup and Restore of Configuration Data
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current solutions for backing up and restoring configuration data lack security, particularly when transferring encrypted data to another device, as they store configuration data in plaintext, compromising confidentiality and integrity.
Innovation Solution
A method involving encryption and decryption using pre-provisioned keys common to a pool of devices, such as those of the same product model, stored in a read-only memory, ensuring secure backup and restore processes across devices without user configuration, with integrity checks to verify authorized restoration.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If configuration data are encrypted using device-specific credentials for secure backup, then data confidentiality is improved, but restoration on another device becomes impossible
Solution Approach 1:
The encryption key is segmented into two parts: a device-specific component (device identifier) and a user-specific component (user identifier). This allows the encrypted configuration data to be restored on any device belonging to the same user, while still maintaining security through the device-specific portion of the key.
Solution Approach 2:
The user identifier acts as an intermediary that bridges the device-specific encryption and enables cross-device restoration. The encryption key is formed by combining the device identifier with the user identifier, allowing the user's credentials to mediate the restoration process across different devices.
2Adaptability or versatility
If configuration data are stored in plaintext for easy restoration on another device, then adaptability is improved, but data security deteriorates
Solution Approach 1:
The encryption key is segmented into device-specific and user-specific components, enabling the system to maintain encrypted storage while allowing restoration across devices through the user identifier portion of the key.
Solution Approach 2:
The encryption approach changes from using purely device-specific parameters to using a combination of device parameters and user parameters. This parameter change enables both security (through encryption) and adaptability (through user-based key derivation).
3Reliability
If user identifiers are included in encrypted backup data, then unauthorized restoration is prevented, but backup data size increases
Solution Approach 1:
Instead of encrypting the entire configuration data set with a complex key structure, the patent applies partial encryption by incorporating only the necessary user identifier portion of the key. This provides sufficient authorization control without excessively increasing data size.
Data Source
AI summary
Back-up procedures for saving configuration data are provided, which enable the restoration of said configuration data on the device when it is reset to default, or on another device when the device is stolen or broken. Since configuration data are sensitive data, it is important to protect their confidentiality and their integrity throughout the back-up and restore process. Current solutions enable a secure back-up and restore process on the same device since the backed-up configuration data are encrypted using credentials that are only known to the device. In order to overcome these drawbacks, a solution is proposed for performing a secure back-up process which enables the restoration of the backed-up data to the same device or to a distinct device. This is made possible by using encryption keys that are common to a pool of devices. Those common encryption keys are provided during the manufacturing of the devices.