Database Session State Reset Mechanism for Leakage Prevention
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current database management systems lack an automated and guaranteed method to reset session state at the end of requests, leading to potential session state leakage and transaction leakage between sessions, which can result in security issues and performance degradation.
Innovation Solution
The system identifies and records session state aspects, classifying them as client-restorable, server-restorable, or non-restorable, and automatically resets the session state at designated points in the request lifecycle, ensuring no state leakage occurs by maintaining and modifying session attributes through configuration and templates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If session state is maintained across requests for performance efficiency, then request processing speed improves, but session state leakage between sessions occurs causing security issues
Solution Approach 1:
The system performs preliminary classification of session state aspects into client-restorable, server-restorable, and non-restorable categories before requests occur. This pre-established classification framework enables automatic reset mechanisms to be ready and configured in advance, allowing rapid session state clearance when needed without compromising security during request processing.
Solution Approach 2:
The patent introduces an intermediary classification mechanism that acts as a mediator between session state maintenance and security requirements. By classifying session state aspects into different restorability categories, the system creates a controlled intermediate layer that determines what can be safely preserved and what must be reset, thereby enabling both performance efficiency and security isolation.
2Reliability
If automated session state reset is implemented to prevent leakage, then security and session isolation improve, but system complexity increases due to tracking and classification requirements
Solution Approach 1:
The system segments session state into distinct aspects that can be independently classified and managed. By dividing session state into client-restorable, server-restorable, and non-restorable categories, the complex problem of session state management is broken down into manageable segments with different reset behaviors, reducing overall system complexity while maintaining security.
Solution Approach 2:
The patent changes the parameter of session state management by introducing classification attributes (restorability categories) that transform the complex binary decision of reset vs. preserve into a multi-dimensional classification system. This parameter transformation simplifies the management logic by providing clear rules for each category.
3Reliability
If session state is reset at the end of each request to ensure isolation, then security improves, but request processing time increases due to reset operations
Solution Approach 1:
Instead of resetting the entire session state, the system applies partial reset actions only to specific aspects that require isolation. By resetting only the necessary portions of session state based on their classification, the system achieves security isolation while minimizing the time cost associated with comprehensive reset operations.
Solution Approach 2:
The patent applies different reset qualities to different aspects of session state based on their classification. Client-restorable aspects are handled differently from server-restorable and non-restorable aspects, allowing localized optimization of reset operations where full reset is applied only where necessary for security, while other aspects maintain their state for performance efficiency.
Data Source
AI summary
Techniques are described to perform an automatic reset of a database session to generate an environment that resembles a brand new session without the computational cost of creating a brand new session. In an embodiment, a DBMS receives a request from a client application to execute commands within a session. The DBMS identifies that the end request boundary, the end of the logical work unit for the client application, is reached within the session. The DBMS verifies that the end request boundary is at a resettable point of a session state of the session for the session to be safely reset. If the verification is successful, the DBMS performs a reset of the session to prevent any leakage of application-related session state to the next request.