Privilege Model for Transparent Super-User Coexistence

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The traditional Unix-based operating system security model uses an all-or-nothing approach, where processes require super-user privileges to perform any privileged operations, lacking a seamless way for super-user and traditional privilege-based processes to coexist and manage privileges effectively.

Innovation Solution

A kernel-based security policy framework that allows super-user and traditional privilege-based processes to coexist transparently, using multiple privilege sets and a privilege awareness property state to manage privileges on a per-process basis, enabling processes to transition between privilege-aware and non-privilege-aware states dynamically.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the traditional super-user model is used, then processes can perform privileged operations, but all processes need to run as super-user to access any privileged function

Engineering Contradiction:
Improveprivilege access flexibilityVSAvoidprocess configuration complexity
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent segments the monolithic super-user privilege model into fine-grained individual privileges. Each privilege represents a specific capability (e.g., file access, network binding), and processes can be granted only the specific privileges they need rather than all super-user powers. This segmentation enables flexible privilege assignment while maintaining security.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements local quality by allowing different processes to have different privilege sets tailored to their specific needs. Instead of a uniform super-user model, each process can be configured with exactly the privileges required for its function, creating localized privilege assignments that improve both security and operational ease.

Inventive Principle:
Principle #3Local quality

2Reliability

If the traditional super-user model is used, then privileged operations can be performed, but security control is coarse-grained

Engineering Contradiction:
Improvesecurity control precisionVSAvoidprivilege management flexibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent divides the coarse-grained super-user privilege into fine-grained individual privileges. Each privilege represents a specific system resource or operation, allowing precise control over what each process can do. This segmentation improves security control precision while enabling flexible privilege management.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent changes the parameter of privilege granularity from coarse (all-or-nothing super-user) to fine (individual privileges). This parameter change enables both improved security control precision through specific privilege assignment and enhanced adaptability through flexible privilege configuration.

Inventive Principle:
Principle #35Parameter changes

3Adaptability or versatility

If super-user and privilege-based processes coexist, then granular privilege control is achieved, but system complexity increases

Engineering Contradiction:
Improveprivilege model flexibilityVSAvoidprivilege system structure
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal privilege framework that can accommodate both traditional super-user processes and fine-grained privilege-based processes within the same system. The privilege model is designed to be multi-functional, supporting different process types and privilege assignment strategies, thereby reducing the need for separate system configurations.

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

Solution Approach 2:

The patent introduces a privilege management intermediary layer that mediates between processes and system resources. This intermediary handles privilege verification and enforcement, allowing complex privilege logic to be managed centrally rather than embedded in each process, thus reducing overall system complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Reliability

If processes are modified to use privilege-based security, then fine-grained control is achieved, but modification effort increases

Engineering Contradiction:
Improvesecurity policy precisionVSAvoidprocess adaptation effort
Core Design Contradiction:
ReliabilityVSEase of manufacture

Solution Approach 1:

The patent enables processes to automatically manage their own privileges through self-service mechanisms. Processes can declare their required privileges, and the system automatically grants appropriate access rights. This eliminates the need for manual modification of process code to implement fine-grained security control.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent introduces a privilege management intermediary that automatically handles the assignment and verification of fine-grained privileges. This intermediary simplifies the integration process by providing standardized interfaces that work with existing processes without requiring extensive modifications to achieve security policy precision.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS7383437B1Method and system for implementing super-user-compatible privileges
Publication Date: 2008.06.03 ORACLE AMERICAN INC
  • US7383437B1 patent drawing
  • US7383437B1 patent drawing
  • US7383437B1 patent drawing

AI summary

A system for implementing a super-user-compatible privilege security policy on a computer operating system is disclosed. The system includes a kernel for enforcing a security policy on processes, based on privileges. The system also includes a privilege model that interfaces with the kernel and implements a framework in which super-user based processes and privilege based processes transparently interface with the kernel. The privilege model includes several privilege sets associated with each process, a privilege awareness property state associated with each process, the property state indicating whether or not a process is privilege aware, and a software module for automatically modifying the privilege sets and the property state, on a per process basis, based on individual process behavior.