Database Query Plan Auditing for Precise Privileged Data Access
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing database search auditing solutions generate many 'false positives' by processing queries that do not actually access privileged data, leading to inefficiencies in identifying actual privileged data access.
Innovation Solution
Insert indicators directly into database queries that access privileged data values or columns, allowing for precise identification and determination of search queries that access such data.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If existing database search auditing solutions process all queries to detect privileged data access, then auditing coverage is comprehensive, but false positives increase and auditing efficiency decreases
Solution Approach 1:
The system performs preliminary analysis of the query plan before executing the full query, inserting indicators into the query plan to identify which queries will access privileged data. This preliminary action allows the auditing system to filter and focus only on relevant queries, eliminating false positives while maintaining comprehensive coverage and improving auditing efficiency.
2Reliability
If existing auditing solutions audit all queries accessing tables with privileged data, then no privileged access is missed, but processing overhead increases significantly
Solution Approach 1:
The system extracts and isolates the specific portion of the query plan that accesses privileged data by inserting indicators at those precise locations. Instead of auditing entire queries that touch tables containing privileged data, the system selectively identifies and audits only the specific data access operations, reducing processing time while maintaining auditing completeness.
3Loss of information
If existing solutions generate detailed audit logs for all queries, then audit trail completeness is maximized, but storage and analysis resources are wasted on false positives
Solution Approach 1:
The system applies local quality by inserting indicators specifically at the locations in the query plan where privileged data is accessed, rather than uniformly processing all queries. This allows the auditing system to generate detailed audit logs only for the specific portions of queries that actually access privileged data, maintaining audit trail completeness while minimizing storage resource consumption by eliminating false positives.
Data Source
AI summary
An approach for identifying privileged access to a database is provided. A processor receives a query plan to search the database. A processor determines the query plan includes a request that accesses privileged data. A processor generates an updated query plan with an indication of the request that accesses privileged data. A processor sends the updated query plan for an audit of the query plan.