Container Authority Control via External Configuration Validation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for authority control in container technology during software development, such as using chmod, rbash, and lshell, fail to accurately restrict user permissions, leading to security risks and inaccuracy in executing scripts, as they close all restrictions when a user is deemed whitelisted.

Innovation Solution

A method and apparatus for authority control that load and execute a container by acquiring a configuration file managed outside the container, validating it, and performing a validity check on user instructions and script content based on the configuration file, allowing for granular control of user permissions according to business scenarios, thereby improving security and adjustability.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional authority control tools (chmod, rbash, lshell) are used to restrict user permissions in containers, then security risks are reduced, but the control accuracy decreases and security is compromised when users are whitelisted

Engineering Contradiction:
ImprovesecurityVSAvoidauthority control accuracy
Core Design Contradiction:
ReliabilityVSMeasurement precision

Solution Approach 1:

The patent segments authority control into two distinct layers: (1) traditional authority control tools (rbash, lshell, chmod) that provide baseline security restrictions, and (2) a new script-level validation mechanism that checks each command statement against a configuration file. This segmentation allows the system to maintain both broad security coverage and fine-grained control accuracy, resolving the contradiction between security and control precision.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements preliminary validation by checking command statements against a configuration file before execution. The system pre-defines allowed commands and parameters in a configuration file, then validates each user instruction against these predefined rules prior to execution. This preliminary action ensures that even whitelisted users cannot execute unauthorized commands, maintaining both security and control accuracy.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If configuration files are managed outside the container with business scenario-specific authority rules, then adaptability and security are improved, but device complexity increases

Engineering Contradiction:
Improvebusiness scenario adaptabilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a configuration file as an intermediary between the container execution environment and authority control rules. This configuration file, managed outside the container, serves as a mediator that translates business scenario requirements into executable validation rules. The intermediary approach allows flexible adaptation to different business scenarios without modifying the container or execution engine, thereby improving adaptability while managing complexity through a dedicated configuration layer.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system implements self-service by automatically validating command statements against the configuration file without requiring manual intervention or complex authorization workflows. The validation mechanism autonomously checks each command against predefined rules, executes valid commands, and rejects invalid ones, thereby adapting to different business scenarios through configuration rather than system redesign.

Inventive Principle:
Principle #25Self-service

3Ease of operation

If all authority restrictions are closed when a user is deemed whitelisted, then ease of operation is improved, but security and control accuracy deteriorate

Engineering Contradiction:
Improveuser operation convenienceVSAvoidsecurity
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent implements dynamic authority control where the validation strictness adapts based on the specific command being executed. Rather than statically closing all restrictions for whitelisted users, the system dynamically evaluates each command statement against the configuration file. This dynamic approach maintains ease of operation for legitimate commands while preserving security control for potentially harmful commands, resolving the contradiction between operational convenience and security.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS11599654B2Method and apparatus for authority control, computer device and storage medium
Publication Date: 2023.03.07 ENVISION DIGITAL INT PTE LTD
  • US11599654B2 patent drawing
  • US11599654B2 patent drawing
  • US11599654B2 patent drawing

AI summary

A method and an apparatus for authority control, a computer device, and a storage medium, and relates to the field of the Internet technologies. The method includes: acquiring a configuration file according to a business scenario when a container is initialized, wherein the configuration file is managed outside the container; validating the configuration file in the container; receiving a user instruction; and identifying a type of the user instruction when the user instruction is an executable instruction. The method further including acquiring script content of a script file when the type of the user instruction indicates that the user instruction is the script file, wherein the script content includes at least one command statement; and performing a validity check on the at least one command statement based on the configuration file.