Handheld Medical Device Software Revocation via Configuration Device
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Handheld medical devices for diabetes management require secure and efficient updating of software to maintain functionality and ensure patient safety, as existing systems lack secure data distribution and revocation mechanisms.
Innovation Solution
A method involving a configuration device that receives revocation lists from remote servers to protect handheld medical devices from executing unauthorized software entities, by comparing cryptographic certificates and selectively executing protective functions to prevent execution of revoked software, and regulating data updates based on these lists to ensure secure and authorized updates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If cryptographic verification and revocation list checking are implemented to secure software updates, then security and reliability are improved, but device complexity and processing time increase
Solution Approach 1:
The configuration device performs cryptographic verification and revocation list checking before allowing software updates to be installed on the handheld medical device. This preliminary security check ensures that only authorized and non-revoked software is updated, preventing execution of unauthorized code while maintaining device security without requiring complex runtime verification mechanisms
2Reliability
If cryptographic verification and revocation list checking are implemented to secure software updates, then security and reliability are improved, but update processing time increases
Solution Approach 1:
The configuration device performs cryptographic verification and revocation list checking on a selective basis - verifying the cryptographic certificate and checking against the revocation list only when software updates are being processed. This partial verification approach provides adequate security for the critical update operation without requiring continuous verification that would excessively increase processing time during normal device operation
3Reliability
If revocation lists are maintained and checked to prevent execution of unauthorized software, then security is improved, but data management complexity and storage requirements increase
Solution Approach 1:
The revocation list and cryptographic verification functionality are extracted from the handheld medical device and implemented in the external configuration device. This extraction allows the medical device to maintain simple operation while the configuration device handles the complex tasks of maintaining revocation lists, performing cryptographic verification, and managing security policies, thereby reducing data management complexity within the medical device itself
Data Source
Figure 1~2
Figure 3
Figure 4
AI summary
A method includes: receiving a revocation list from a remote data server at a configuration device. The revocation list includes N cryptographic certificates associated with N computer software entities, respectively, that are not to be executed by any of a group of medical devices including a handheld medical device. N is an integer greater than or equal to zero The method further includes receiving data from the handheld medical device at the configuration device. The data includes a cryptographic certificate that is associated with a given computer software entity that is presently installed in memory of the handheld medical device for execution by the handheld medical device. The method further includes comparing the cryptographic certificate with the revocation list; and selectively executing a protective function by the configuration device when the cryptographic certificate is the same as one of the N cryptographic certificates of the revocation list.