Container Identity Files for Secure Cross-Signer Data Exchange
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing technologies face challenges in securely exchanging data between containerized applications on a mobile device, particularly when these applications have different signer information due to containerization tools like Oracle Mobile Security Suite, leading to issues with signature level protection and unauthorized access.
Innovation Solution
A method is implemented where a device registers containerized applications with an access server, generates public/private keys, and uses an Intent Encryption Key (IEK) and root key for secure data exchange, ensuring only authorized applications can access shared data by verifying identities and encrypting communications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If signature level protection is used to secure data exchange between applications, then security is improved, but containerized applications with different signer information cannot communicate
Solution Approach 1:
The patent introduces a container identity file as an intermediary mechanism that mediates between applications with different signer information. This identity file contains the signer's certificate and public key, allowing applications to verify each other's identities without requiring the same signer. The intermediary enables secure communication between containerized applications from different vendors while maintaining signature-level security through cryptographic verification.
2Reliability
If containerization tools are used to secure applications, then security is improved, but different containerized applications cannot exchange data due to different signer information
Solution Approach 1:
The patent implements preliminary action by pre-generating and storing container identity files containing signer certificates and public keys before data exchange occurs. These identity files are created during containerization and stored in advance, enabling applications to perform identity verification and establish secure communication channels without real-time signer matching. This preliminary preparation eliminates the need for same-signer requirements while maintaining security.
3Object-affected harmful factors
If same signer information is required for secure communication, then unauthorized access is prevented, but vendor independence and application diversity are reduced
Solution Approach 1:
The patent applies local quality by implementing security verification at the individual application level rather than requiring global signer uniformity. Each containerized application has its own identity file with unique signer information, and security is enforced locally through identity verification during data exchange. This allows different vendors to sign their applications differently while maintaining security through localized cryptographic verification of each application's identity.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Techniques are provided for establishing a secure exchange of data between containerized applications. A method can include registering, by a device, a first containerized application on the device with an access server, registering, by the device, a second containerized application on the device with the access server, verifying that the first containerized application and the second containerized application are configured to exchange data, and exchanging data between the first containerized application and the second containerized application registered with the access server.