Runtime Library Virtual File System Secure Storage
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing runtime libraries do not effectively provide secure, isolated storage solutions for programs, allowing unauthorized access to private data and lacking seamless integration of local and remote storage access.
Innovation Solution
A runtime library with a virtual file system that uses an API to manage multiple storage areas, authenticates programs based on identifiers, and maps information to file resources, ensuring secure access and integration of local and remote storage through a unified file access routine.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a runtime library provides storage access functions allowing programs to create private storage areas in local hard drive, then data security and isolation are improved, but access complexity and device complexity increase
Solution Approach 1:
The patent introduces a runtime library as an intermediary layer between programs and the storage system. This runtime library provides a virtual file system that mediates all file access operations, automatically handling authentication and storage area selection. Programs interact with the intermediary (runtime library) rather than directly with the complex storage system, thus improving security while maintaining simple programmatic access through unified API calls.
2Reliability
If a virtual file system provides separate private and shared storage areas, then data isolation and security are improved, but system complexity and difficulty of operation increase
Solution Approach 1:
The runtime library implements a universal file access routine that handles multiple storage scenarios through a single unified interface. The same API call can access private storage areas when authentication succeeds, or shared storage areas when the program lacks authentication credentials. This multi-functional approach allows the system to provide both isolation and shared access without requiring different interfaces or increasing operational complexity for users.
3Reliability
If authentication mechanisms are implemented to control access to private storage areas, then security is improved, but processing time and device complexity increase
Solution Approach 1:
The system performs preliminary authentication actions during program loading or initialization phases, before actual file access operations occur. By authenticating programs in advance and establishing their access rights beforehand, the system avoids repeated authentication overhead during normal file operations. This preliminary action ensures security requirements are met while minimizing time loss during actual data access.
4Ease of operation
If a unified file access routine is used for both private and shared storage, then ease of operation is improved, but security control and reliability may be compromised
Solution Approach 1:
The runtime library implements local quality by applying different access control policies to different storage areas based on their nature. Private storage areas have strict authentication requirements enforced by the runtime library, while shared storage areas have more permissive access rules. The unified file access routine automatically adapts its behavior based on the target storage area, maintaining simple user interface while enforcing appropriate security controls for each local context.
Data Source
AI summary
This specification describes technologies relating to a runtime library including a virtual file system. In general, a method can include interfacing with an operating system of a computer; and providing runtime services, including a virtual file system, to programs running on the computer. Providing runtime services can include receiving first information and second information through a single file access routine of an API for the virtual file system; determining a selected one of multiple file storage areas to access based on the first information, the multiple file storage areas including a first local area accessible by a first program and inaccessible by a second program, and a second area accessible by the first program and the second program; mapping the second information to file resource(s) in the selected file storage area in the virtual file system; and accessing the one or more file resources for the first program.