Data Entity Transformation for Consistent Access Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
As the number of applications and users accessing a database increases, inconsistencies in security controls compromise the security of the data maintained in the database.
Innovation Solution
Implementing data interlocutors that transform data into data entities with embedded security metadata, ensuring all transactions occur through these interlocutors to enforce consistent security and access controls at the data level.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If security controls are implemented at the application layer, then each application can have customized security rules, but the inconsistency in security controls increases as the number of applications increases
Solution Approach 1:
The patent introduces data entities as intermediary objects between applications and the database. These data entities contain embedded security metadata that acts as a mediator, translating application access requests into standardized database operations. This intermediary layer ensures that security rules are consistently applied at the data level regardless of which application is accessing the data, resolving the contradiction between customized security rules and security consistency.
Solution Approach 2:
The patent shifts the security control dimension from the application layer to the data entity layer. Instead of managing security at the application level (horizontal dimension), the system embeds security metadata within data entities (vertical dimension), creating a new layer of security management. This dimensional shift allows customized security rules to be maintained while ensuring consistent enforcement across all applications through the standardized data entity interface.
2Productivity
If the number of applications and users accessing the database increases, then data management scalability improves, but the risk of data compromise increases due to inconsistent security controls
Solution Approach 1:
Data entities serve as intermediaries that standardize access requests from multiple applications and users. Each data entity encapsulates security metadata that mediates access control decisions, ensuring that security policies are consistently enforced regardless of the number of applications or users. This intermediary mechanism enables scalable data management while maintaining security integrity.
Solution Approach 2:
The patent applies preliminary action by embedding security metadata within data entities before they are stored in the database. This pre-configured security information is prepared in advance, allowing the system to efficiently evaluate and enforce security policies without complex real-time processing. This preliminary preparation enables the system to handle increased numbers of applications and users while maintaining consistent security controls and reducing data compromise risk.
3Ease of manufacture
If security controls are implemented at the application layer, then implementation flexibility is maintained, but the complexity of managing security across multiple applications increases
Solution Approach 1:
The data entity intermediary simplifies security management by providing a standardized interface between applications and the database. Applications interact with data entities using uniform operations, and the embedded security metadata automatically handles access control decisions. This eliminates the need for each application to implement its own security logic, reducing management complexity while preserving implementation flexibility through the configurable security metadata.
Solution Approach 2:
The data entity structure provides universal functionality by serving as a common vehicle for all data access operations across different applications. The standardized data entity interface with embedded security metadata can be used by any application, eliminating the need for application-specific security implementations. This universal approach reduces overall system complexity while maintaining flexibility through the configurable security attributes within each data entity.
Data Source
AI summary
In some implementations, a data management system may obtain, via a data interlocutor, a set of data intended for inclusion in a database, wherein the set of data is associated with at least one data type, wherein the set of data comprises at least one data value. The data management system may generate, via the data interlocutor, a set of data entities based on the set of data and a set of security metadata associated with the set of data, wherein the set of data entities comprises a data entity associated with a data value of the at least one data value, the data entity comprising transaction authorization information associated with the data value. The data management system may output, via the data interlocutor, the set of data entities for inclusion in the database.


