SELinux Automatic Labeling via Transition Rules
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
SELinux security policies often require manual correction of mislabeled objects, which is inconvenient and prone to human errors, as newly created objects may need labels different from their parent directories or default labels to ensure proper access control.
Innovation Solution
A method and system that automatically define and apply security labels for newly created objects based on the label of the process creating them, the class of the object, and its name, using a policy rule compiler and a labeling subsystem within the operating system, ensuring accurate labeling and access control.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If manual correction of security labels is used, then security policy compliance can be achieved, but administrative burden and human error increase
Solution Approach 1:
The system performs preliminary action by automatically assigning correct security labels at object creation time based on transition rules, preventing mislabeling before it occurs. This eliminates the need for manual correction and reduces administrative burden while ensuring security policy compliance.
Solution Approach 2:
The system implements self-service by enabling automatic label assignment through transition rules that autonomously determine and apply appropriate security labels without human intervention. The labeling subsystem automatically evaluates transition rules and applies correct labels, reducing reliance on manual administrative actions.
2Ease of manufacture
If default parent directory labels are applied, then label assignment is simplified, but security policy requirements may not be met
Solution Approach 1:
The system applies local quality by allowing different security labels to be assigned to different objects based on their specific characteristics and transition rules. Instead of uniformly applying parent directory labels, the system evaluates object-specific transition rules to assign appropriate labels, ensuring both simplicity and security policy compliance.
Solution Approach 2:
The system implements parameter changes by dynamically determining security labels based on transition rule parameters such as process type, object class, and object name. The labeling subsystem evaluates these parameters and applies appropriate labels, enabling flexible label assignment that maintains simplicity while meeting security requirements.
3Ease of operation
If automatic label assignment based on transition rules is implemented, then administrative burden is reduced, but system complexity increases
Solution Approach 1:
The system introduces an intermediary component - the transition rule evaluation mechanism - that mediates between object creation events and label assignment. This intermediary automatically evaluates transition rules and determines appropriate labels, reducing administrative burden while managing system complexity through structured rule-based processing.
Solution Approach 2:
The system implements feedback by continuously evaluating transition rules against object creation events and adjusting label assignments accordingly. The labeling subsystem monitors object creation, evaluates applicable transition rules, and automatically applies correct labels, creating a closed-loop system that reduces administrative intervention while maintaining manageable complexity through automated feedback mechanisms.
Data Source
AI summary
An operating system identifies a request of a process to create a new object with a name in a file system of the processing device. The operating system identifies a policy rule applicable to the new object in view of at least the name of the new object. The operating system creates a label for the new object using the applicable policy rule and associates the new object with the created label.