Resource-Level Authentication Enforcement via Database Triggers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing client-server architectures face vulnerabilities in authentication mechanisms, as fraudulent attacks can occur at both the client and server levels, compromising the security of sensitive data transactions in web applications like e-commerce and e-banking.
Innovation Solution
Implementing an authentication mechanism at the resource level within a database management system, using authentication keys and referential integrity constraints to enforce secure access, and employing triggers to monitor and enforce authentication prior to data operations, thereby enhancing security by propagating authentication keys across data storage units.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If authentication mechanisms are implemented at client and server levels, then security against fraudulent attacks is improved, but vulnerabilities remain as attacks can occur at multiple levels
Solution Approach 1:
The patent segments the authentication mechanism into multiple independent layers: client-level authentication, server-level authentication, and resource-level authentication. Each layer operates independently with its own authentication keys and verification processes. This segmentation ensures that compromise at one level does not necessarily compromise the entire system, as each layer provides a separate security checkpoint.
Solution Approach 2:
The patent introduces resource-level authentication as a new dimensional layer of security beneath the traditional client-server architecture. Instead of only authenticating at the application level (client-server), the system now authenticates at the data level (resource), creating a vertical security dimension that intercepts and validates authentication credentials at the database tier, thereby blocking attacks that penetrate past the server level.
2Reliability
If authentication is enforced at resource level through multiple mechanisms, then security reliability is improved, but system complexity increases
Solution Approach 1:
The patent implements a universal authentication key propagation mechanism that works across all data storage units in the system. The same authentication key specification and verification process is applied uniformly to tables, views, and other database objects. This universal approach, while adding functionality, maintains consistent processing logic throughout the system, which helps manage complexity through standardization.
Solution Approach 2:
The patent introduces triggers as intermediary components that mediate between the authentication mechanism and the database operations. Triggers automatically execute authentication verification when data access operations occur, acting as an intermediary layer that handles the complex verification logic without requiring direct integration into every application layer. This intermediary approach encapsulates complexity in a manageable, reusable component.
3Reliability
If authentication keys are propagated across data storage units through triggers, then authentication coverage is improved, but processing overhead increases
Solution Approach 1:
The patent performs authentication key propagation and verification preparation in advance by establishing triggers during database object creation. The authentication keys are pre-propagated to all relevant data storage units through the trigger mechanism, so that when actual data access occurs, the verification process can proceed using pre-configured authentication parameters rather than performing full key propagation at access time. This preliminary setup reduces the time penalty during actual authentication operations.
Data Source
AI summary
The present description refers in particular to a computer-implemented method, a computer system, and a computer program product. The method may comprise providing authentication enforcement at resource level by specifying at design time at least one authentication key for at least one data storage unit of a resource. A request may be received at a server from a requester through a client to access the resource. Authentication of the requester may be enforced through the at least one authentication key at the at least one data storage unit of the resource.


