Application Policy File Generation for Secure Memory Access
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing electronic devices face inefficiencies in obtaining and updating policy files for securing applications, particularly when installing or executing applications that handle personal information, leading to inconvenient and resource-intensive processes.
Innovation Solution
An electronic device is configured to authenticate applications and generate policy files associated with domains, allowing secure access to specific areas of memory based on these files, thereby streamlining the installation and execution processes while ensuring security.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If policy files are obtained from authentication server through FOTA for each application installation, then application security is ensured, but system resources are inefficiently used and the process is inconvenient
Solution Approach 1:
The patent pre-generates policy files during application compilation or packaging, so that when the application is installed, the policy file is already available locally without needing to retrieve it from the authentication server. This preliminary action eliminates the need for runtime server communication, improving both security (by ensuring policy availability) and resource efficiency (by avoiding repeated network operations).
Solution Approach 2:
The patent creates a copy of the policy file and embeds it within the application package or stores it in local storage during the installation process. This copying mechanism allows the system to use the local copy instead of repeatedly accessing the authentication server, thereby reducing network traffic and server load while maintaining security policy enforcement.
2Reliability
If policy files are obtained from authentication server for each application installation, then application security is ensured, but the process becomes inconvenient and time-consuming
Solution Approach 1:
The policy file is generated and attached to the application package in advance during compilation or packaging. When the application is installed, the policy file is already present in the local system, eliminating the time-consuming process of retrieving it from the authentication server during installation or runtime.
Solution Approach 2:
The patent copies the policy file from the authentication server during application packaging or installation and stores it locally. This copying process, performed once during installation rather than repeatedly during runtime, significantly reduces the time required for policy file acquisition while ensuring security policies are available for enforcement.
3Reliability
If authentication server is contacted for policy files during application execution, then security is maintained, but system resources are wasted
Solution Approach 1:
The patent creates a local copy of the policy file during application installation and stores it in device memory or storage. This local copy is then used for security enforcement during application execution, eliminating the need for continuous network communication with the authentication server and thereby reducing energy consumption from network operations while maintaining security.
Solution Approach 2:
The system performs self-service by maintaining local copies of policy files and autonomously enforcing security policies without requiring continuous external verification from the authentication server. This self-service approach reduces energy consumption by eliminating repeated network transactions while ensuring security policies are consistently applied.
Data Source
AI summary
An electronic device is provided. The electronic device includes a memory to store an application, a communication interface to communicate with an external device, and a processor operatively connected with the memory and the communication interface. The processor determines whether the application is authenticated if receiving an installation request or an execution request of the application, generates a policy file associated with a domain of the application if the application is authenticated, and assigns the application to a specified domain, which is accessible to a secure area of the memory, based on the generated policy file.