Security Category Labels for Multi-Tenant PaaS Isolation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In Platform-as-a-Service (PaaS) environments, managing and securing multi-tenant applications across virtual machines is inefficient due to resource wastage and security concerns, as each application requires significant expertise and separate virtual machines, leading to high costs and resource strain, especially in public and private cloud settings.

Innovation Solution

A mechanism is introduced to apply unique security category labels to each multi-tenant application, assigning these labels to IP addresses, files, and running processes, utilizing the operating system's security features to enforce access permissions and maintain separation between applications, thereby optimizing resource utilization and enhancing security.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If separate virtual machines are allocated to each application, then security and isolation between applications are improved, but resource utilization deteriorates and costs increase

Engineering Contradiction:
Improvesecurity isolationVSAvoidresource wastage
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The system segments security contexts at the process level rather than requiring separate virtual machines for each application. Each process is assigned a unique security context that provides isolation and security boundaries, allowing multiple applications to share the same virtual machine infrastructure without compromising security.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Multiple applications are merged into a single virtual machine environment, sharing common infrastructure resources such as CPU, memory, and storage. The security context mechanism enables this consolidation while maintaining appropriate isolation between applications through process-level security boundaries.

Inventive Principle:
Principle #5Merging (Combining)

2Reliability

If separate virtual machines are used for each application, then security between applications is improved, but device complexity and operational overhead increase

Engineering Contradiction:
Improvesecurity isolationVSAvoidmanagement complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The security context mechanism serves as a universal solution that provides security isolation across multiple applications within a single virtual machine. This multi-functional approach replaces the need for separate virtual machine management, reducing operational overhead while maintaining security boundaries through a standardized process-level security framework.

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

3Productivity

If multiple applications share a virtual machine, then resource utilization is improved, but security isolation between applications deteriorates

Engineering Contradiction:
Improveresource utilizationVSAvoidsecurity isolation
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system applies local quality by providing customized security contexts to each individual process within the shared virtual machine environment. Each process receives a unique security context tailored to its specific security requirements, enabling fine-grained security control that maintains isolation between applications while allowing them to share infrastructure resources.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS9038128B2Applying security category labels to multi-tenant applications of a node in a platform-as-a-service environment
Publication Date: 2015.05.19 RED HAT INC
  • US9038128B2 patent drawing
  • US9038128B2 patent drawing
  • US9038128B2 patent drawing

AI summary

A mechanism for applying security category labels to multi-tenant applications of a node in a PaaS environment is disclosed. A method of embodiments includes generating, by a virtual machine (VM), a unique security category label (SCL) for each local user identification (UID) maintained by the VM, assigning, for each local UID maintained by the VM, the unique SCL associated with the local UID to one or more Internet Protocol (IP) addresses mapped to the local UID, receiving a request to initialize an application on the VM, assigning a local UID of the local UIDs maintained by the VM to the application, assigning files of the application the unique SCL associated with the local UID of the application, and assigning the unique SCL associated with the local UID of the application to a running process of the application.