Secure Configuration Updates With Fallback for Legacy Electronic Devices
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing methods for updating firmware in electronic devices are complex, costly, and can disrupt the operation of systems, especially when new devices with updated security features are introduced, as they may not be compatible with existing devices, leading to security risks and operational interruptions.
Innovation Solution
A method for secure configuration updates that includes selecting device functions, assigning implementation rules, and using a fallback function to ensure continued operation, allowing updates to be executed regardless of device functionality, with enhanced security authorization and graphical verification.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a firmware update is performed to improve security functions, then security vulnerability is reduced, but device complexity and update cost increase
Solution Approach 1:
The firmware is segmented into security-related parts and application-related parts, allowing independent updates. The security officer can update only security functions without affecting application configurations, reducing update complexity and cost while maintaining security improvements.
Solution Approach 2:
The system performs preliminary checks to verify device compatibility and authorization status before executing firmware updates. This preliminary validation prevents incompatible updates and reduces the need for complex error handling, simplifying the update process while ensuring security improvements are applied correctly.
2Reliability
If device replacement is performed to improve security, then security function is updated, but system operation is interrupted
Solution Approach 1:
The system dynamically adapts when a replacement device is introduced by automatically detecting the new device and re-evaluating security configurations. This dynamic adaptation allows the system to maintain operation while updating security functions, avoiding complete system shutdowns and reducing downtime.
Solution Approach 2:
The system uses an intermediary configuration layer that mediates between old and new devices. This intermediary layer allows seamless transition during device replacement, maintaining system operation while security functions are updated through the firmware update mechanism.
3Reliability
If strict security authorization is enforced to ensure security, then security function is improved, but ease of operation deteriorates
Solution Approach 1:
The system implements self-service mechanisms where devices automatically verify their own authorization status and compatibility before accepting updates. This self-verification reduces the need for manual security officer intervention for routine operations, improving ease of operation while maintaining strict security authorization for critical security function updates.
Data Source
Figure 1
AI summary
To ensure the continued safe operation of the electronic device (1) after a configuration update, a method for performing a safe configuration update of the electronic device (1) is provided, comprising the steps of: - providing a configuration update program (2), comprising the steps of: i) selecting at least one device function for the device that forms part of the device's configuration update, ii) assigning a first execution instruction to the device function, wherein the first execution instruction sets a first device function property if the selected device function is present on the device, iii) assigning a second execution instruction to a fallback function, wherein the second execution instruction enables either releasing the configuration update or ignoring an impossible configuration update.This includes stopping the device or adjusting device functions when the fallback function is executed on the device, - running the configuration update program (2) on the device and performing the following steps: a) checking whether the device function selected in step i) and/or the first execution instruction assigned in step ii) are supported by the device (1), b) saving the first execution instruction as a configuration update to the device if the selected device function and/or the assigned first execution instruction is supported by the device (1), or c) executing the fallback function if the selected device function and/or the assigned first execution instruction is not supported by the device (1), so that the second execution instruction is executed.