Split-Key IMD Authentication Using Cloud Vault and Therapy App
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Commercial wireless protocols used for communication between implantable medical devices (IMDs) and external devices have limited security, making them vulnerable to breaches due to insecure pairing procedures and access by other applications on commercial off-the-shelf devices, posing a risk to device security.
Innovation Solution
A split key architecture is employed to authenticate external devices with IMDs, where a device authentication parameter is decomposed into two key components, with one component stored in cloud storage and the other embedded in the therapy application, requiring both to be reconstituted for authentication, thus enhancing security by mitigating the risk of key disclosure.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If commercial wireless protocols are used for communication between external devices and IMDs, then ease of operation and device compatibility are improved, but security and vulnerability to breaches deteriorate
Solution Approach 1:
The authentication key is segmented into multiple components (first key component and second key component) that are stored in separate locations (cloud storage system and therapy application, respectively). This segmentation ensures that even if one component is compromised, the complete authentication parameter cannot be reconstructed, thereby maintaining security while using commercial wireless protocols.
2Speed
If a single authentication key is stored in the therapy application, then authentication speed is improved, but security risk from key disclosure increases
Solution Approach 1:
The authentication key is divided into multiple components stored in different locations. The first key component is obtained from cloud storage through an authenticated API call, while the second key component is retrieved from the therapy application using de-obfuscation logic. Both components are required to reconstitute the complete authentication parameter, maintaining authentication speed while reducing security risk from key disclosure.
Solution Approach 2:
A cloud storage system acts as an intermediary to store and provide the first key component. This intermediary layer ensures that the complete authentication parameter is never stored in a single location, reducing the security risk from key disclosure while maintaining authentication functionality.
3Reliability
If key components are distributed across multiple locations, then security against key disclosure is improved, but system complexity increases
Solution Approach 1:
The cloud storage system serves as a trusted intermediary that manages the first key component. This approach distributes key components across multiple locations (cloud and local device) to improve security, while the standardized API interface and automated retrieval process minimize the increase in system complexity.
Solution Approach 2:
The therapy application performs multiple functions: it executes the authentication process, retrieves the second key component using de-obfuscation logic, obtains the first key component from cloud storage via API call, and reconstitutes the complete authentication parameter. This multi-functionality reduces the need for separate dedicated components, thereby limiting the increase in system complexity.
Data Source
AI summary
A system and method for facilitating device and application authentication between an external device and an implanted medical device (IMD), wherein a therapy application executing on the external device is operative to communicate with the IMD via wireless telemetry communications. A device authentication parameter may be decomposed into two key components, wherein one component may be stored in a cloud key vault and the other component may be distributed to the external device as an obfuscated portion embedded in the therapy application. Upon receiving the therapy application, the external device is operative to separately retrieve both key components and reconstitute the original authentication parameter therefrom, which may be presented to the IMD for authentication.