In-Memory File System for Secure Application Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing solutions for security and access control in computer systems and user space file systems, such as sockets, shared memory, and command line interfaces, face issues like security vulnerabilities, synchronization problems, and lack of fine-grained access control, particularly in managing commands like 'create user' and 'delete user' across different user groups.

Innovation Solution

A Manager File System (MFS) is implemented as an in-memory pseudo-file system that redirects file system operations with a specified mount point prefix to a controlling process, allowing for overloaded commands to manage applications and enforce user permissions through authentication and access control lists, ensuring secure and fine-grained access control.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If sockets (TCP/UDP) are used for communication interface, then network communication capability is provided, but security vulnerabilities and port opening issues arise

Engineering Contradiction:
Improvecommunication capabilityVSAvoidsecurity vulnerabilities
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The patent introduces a controlling entity that acts as an intermediary between users and the managed entity. This controller receives and processes commands through a secure interface (such as a shell or command interface) before executing them on the managed entity, thereby eliminating the need to open network ports while maintaining communication capability. The controller mediates all interactions, providing security while preserving functionality.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If shared memory is used for communication interface, then inter-process communication is enabled, but synchronization problems occur

Engineering Contradiction:
Improveinter-process communicationVSAvoidsynchronization reliability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The controlling entity serves as an intermediary that handles all communication requests through a standardized interface. Instead of using shared memory that requires complex synchronization, the controller processes commands sequentially through its interface, managing access control and command execution without requiring direct memory sharing or synchronization mechanisms between processes.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If command line interface is used for communication interface, then command execution capability is provided, but command parser implementation complexity increases

Engineering Contradiction:
Improvecommand execution capabilityVSAvoidcommand parser implementation
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The controlling entity implements a universal command interface (such as a shell) that can handle multiple types of commands (user management, system configuration, application control) through a single standardized mechanism. This multi-functional interface reduces the need for separate parsers for different command types, as the same interface framework processes all commands, thereby reducing overall implementation complexity while maintaining execution capability.

Inventive Principle:
Principle #6Universality (Multi-functionality)

4Adaptability or versatility

If existing communication interfaces are used, then basic communication is enabled, but fine grained access control on commands is lacking

Engineering Contradiction:
Improvecommunication functionalityVSAvoidfine grained access control
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent segments the command execution process into distinct controllable units. The controlling entity maintains a namespace with multiple objects (such as users, groups, and commands), where each command can have its own access control permissions. This segmentation allows different users to be granted specific permissions for specific commands (e.g., some users can only list users, others can create or delete users), providing fine-grained access control while maintaining communication functionality.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS11971863B2Techniques for using an in-memory only file system as an interface for managing computer systems and user space file systems
Publication Date: 2024.04.30 ORACLE INT CORP
  • US11971863B2 patent drawing
  • US11971863B2 patent drawing
  • US11971863B2 patent drawing

AI summary

A manager file system (MFS), implemented using an OS process, exposes a path in the native file system as the root of its file system (e.g., mount point). The MFS informs the OS kernel that any file system operation whose path contains the mount point as its prefix, should be handed over to the process by invoking an appropriate interface method that the process implements as part of its file system implementation. The MFS manages one or more applications and leverages the authentication mechanism of the OS to provide fined-grained access control of MFS managed applications.