Container Integrity Enforcement via Runtime Policy Checks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In container-based applications, there is a risk of unauthorized access and data breaches as different creators can use the same container images for different tasks, leading to potential reading or modification of confidential data or runtime configurations of other applications.
Innovation Solution
A method is introduced to enforce integrity conditions by assigning and evaluating integrity guidelines for one container-based application in relation to others in a common runtime environment, ensuring that only necessary privileges are allocated and preventing unauthorized access by dynamically configuring or deleting violating applications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If container instances are allowed to run with broad execution authorizations and device integrations, then application functionality and ease of operation are improved, but security risks and harmful factors increase as applications may access confidential data or runtime configurations of other applications
Solution Approach 1:
The system performs preliminary checks of integrity guidelines before allowing container instances to start. The host system evaluates whether the container's requested execution authorizations and device integrations would violate integrity conditions of other applications, and prevents startup if violations are detected, thereby avoiding security issues before they occur
Solution Approach 2:
The host system acts as an intermediary between container instances and host resources. It mediates access requests by checking integrity guidelines and controlling which execution authorizations and device integrations are actually granted, preventing direct unauthorized access while maintaining necessary functionality
2Productivity
If multiple container instances are created from the same container image to handle intensified user calls, then productivity and service capacity are improved, but the complexity of managing execution authorizations and ensuring integrity across instances increases
Solution Approach 1:
The integrity guideline checking mechanism serves multiple functions: it validates individual container instances, ensures consistency across multiple instances from the same image, prevents conflicts between different applications, and maintains security policies. This universal approach simplifies managing multiple instances by applying the same validation rules to all of them
Solution Approach 2:
The system automatically checks integrity guidelines and enforces security policies without requiring manual intervention for each container instance. The host system self-manages the evaluation of execution authorizations and device integrations, reducing the operational complexity of managing multiple instances
3Productivity
If different creators use the same container image for different tasks, then resource utilization and productivity are improved, but the risk of reading or modifying confidential data of other applications increases
Solution Approach 1:
The system applies different integrity guidelines and access restrictions to different container instances based on their specific tasks and creators. Each application receives customized execution authorizations and device integrations appropriate to its function, ensuring that confidential data remains protected while allowing legitimate resource sharing
Solution Approach 2:
Before allowing container instances from different creators to access host resources, the system preliminarily checks whether their requested access would violate the integrity conditions or confidentiality requirements of other applications. Instances are only permitted to run if they pass these preliminary security evaluations
Data Source
AI summary
A method is provided for enforcing integrity conditions of a first container-based application with respect to all second container-based applications running in a shared runtime environment of a host system, the method including: assigning a first integrity standard including at least one requirement with regard to a second application; receiving a first piece of provisioning information and the first integrity standard from a user of the first application in the runtime environment, before the start of a first container instance of the first application; verifying the first piece of provisioning information with respect to a second integrity standard verifying the second pieces of provisioning information for each of the second applications with respect to the first integrity standard; reporting to the user a violation; and carrying out an operation to rectify the at least one violation and running the first container instance in the runtime environment.