Hierarchical Role-Based Access Control for Cluster Security
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing Unix user access privilege control paradigm is overly restrictive, offering only two categories (normal and root users) without a middle ground, leading to operational and security issues such as overwhelming root users with mundane tasks, potential misuse of root privileges, and lack of intermediate privileges for users needing enhanced access for benign actions.
Innovation Solution
Implementing a hierarchical role-based access control system with categories like monitor, administration, and configuration, allowing for intermediate privileges that span the gap between non-root and root privileges, and using an authorization map to determine user roles and privileges dynamically, which are stored in memory for efficient access.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If normal users are prevented from performing administrative actions, then system security is improved, but root users become overwhelmed with mundane tasks and normal users must surreptitiously employ root access
Solution Approach 1:
The patent segments the monolithic root privilege into multiple hierarchical roles (e.g., system administrator, network administrator, application administrator) with specific被授予 permissions. This segmentation allows normal users to perform specific administrative actions without having full root access, resolving the contradiction by maintaining security while improving operational efficiency through role-specific access.
Solution Approach 2:
The patent changes the parameter of user privilege from a binary state (normal/root) to a multi-level hierarchical structure with configurable permission sets. This allows the system to adjust the degree of access granted based on specific administrative needs, enabling normal users to obtain targeted administrative capabilities without compromising overall system security.
2Ease of operation
If root privileges are granted to users with limited administrative needs, then operational convenience is improved, but system security deteriorates due to potential misuse
Solution Approach 1:
The patent applies local quality by assigning different permission sets to different roles based on their specific administrative needs. Instead of granting universal root privileges, each role receives localized access rights appropriate to its function (e.g., application administrators can manage applications but not system configuration). This resolves the contradiction by providing operational convenience where needed while maintaining security through restricted access elsewhere.
Solution Approach 2:
The patent introduces role-based access control as an intermediary layer between normal users and root privileges. This intermediary mechanism allows users with limited administrative needs to perform necessary actions through assigned roles without directly obtaining full root access, thus improving operational convenience while preventing security risks associated with unrestricted root privileges.
3Device complexity
If an all-or-nothing user access paradigm is used, then system simplicity is maintained, but operational flexibility and security are compromised
Solution Approach 1:
The patent introduces dynamics by making the access control system adaptable and configurable rather than static. The hierarchical role structure allows administrators to dynamically assign and modify roles and permissions based on changing operational requirements. This resolves the contradiction by maintaining relative simplicity through standardized role templates while providing flexibility through customizable role assignments and permission sets.
Data Source
AI summary
A computer-implemented method for authorizing a user request from a user to perform an action with respect to one of at least one of the plurality of nodes and at least one of the plurality of packages of a cluster is disclosed. The user request is received from a host coupled to communicate with the cluster. The method includes consulting an authorization map to ascertain a role associated with the user. The authorization map is kept in a memory space in one of the plurality of nodes. The method further includes authorizing the user to perform the action if the role associated with the user includes a granted privilege that is higher than a privilege required to perform the user request.