Role-Oriented Database Security Model for Encrypted Field Access
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current security systems in multi-component computing environments, such as IBM's HTTP and Web Services processing environments, lack a well-defined security model, leading to administrative confusion and inadequate protection of sensitive data, as roles are not clearly distinguished, and existing encryption methods require extensive application changes or do not provide data masking.
Innovation Solution
A role-oriented authorization scheme is implemented, where specific roles have defined responsibilities and access rights within a relational database management system, including system administrators, security administrators, auditors, application users, and developers, enforcing end-to-end encryption across the database management system without requiring application changes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If encryption methods are implemented at the table level or column level in existing database systems, then data security is improved, but application complexity increases and extensive application changes are required
Solution Approach 1:
The patent segments the security functionality by introducing a dedicated security administrator role (SECADM) separate from the system administrator role (SYSADM). This segmentation allows security policies, encryption key management, and access control to be independently configured and maintained without requiring changes to application logic or database structure, thereby improving data security while minimizing application complexity
Solution Approach 2:
The patent introduces a security administrator as an intermediary between the system administrator and application users. This intermediary manages encryption keys, defines security policies, and controls access to sensitive data without requiring applications to directly handle encryption/decryption operations, thus enhancing security while avoiding extensive application changes
2Reliability
If existing encryption methods are used without a role-oriented model, then some data protection is achieved, but administrative confusion increases due to lack of well-defined roles
Solution Approach 1:
The patent divides administrative responsibilities into distinct segments: SYSADM manages database structure and overall system configuration, while SECADM manages security policies, encryption keys, and access control. This clear segmentation eliminates role confusion and improves administrative clarity while maintaining strong data protection
Solution Approach 2:
The patent applies different security qualities to different data elements by allowing SECADM to define column-level masks and encryption policies for specific sensitive columns. This enables fine-grained control where only necessary data elements are encrypted with appropriate security measures, improving both data protection and administrative manageability
3Adaptability or versatility
If passwords are defined and maintained by application owners independently, then application access control is improved, but system complexity increases and security management becomes difficult
Solution Approach 1:
The patent merges application access control with the centralized security framework by allowing SECADM to manage all authentication and authorization. Application owners do not maintain independent passwords; instead, they use the unified security system that provides both application-specific access control and centralized security management, reducing overall system complexity
4Productivity
If no data masking is provided with encryption, then full data access is available to authorized users, but data protection is insufficient for sensitive information
Solution Approach 1:
The patent applies different data presentation qualities based on user needs and security requirements. SECADM can define masks that display only certain portions of encrypted data (e.g., last four digits of credit card numbers) while keeping other portions hidden. This provides both data accessibility for authorized operations and enhanced protection for sensitive information
Data Source
AI summary
A database management system implements a role-oriented authorization scheme that facilitates operating system (OS) supported encrypted field access for a table in the database. A security model provides for various roles that have varying responsibilities and rights with respect to the database tables and the data supported therein. In this approach, data that is considered sensitive is encrypted. A system administrator role is authorized to create, update, and maintain a table but is not authorized to view sensitive field data, i.e., data stored in encrypted columns of the table. A security administrator role is authorized to define column masks with OS-enforced security access control to the sensitive field data. By separating (fencing) these responsibilities, the security model enforces end-to-end encryption across the entire database management system.