Token Table Dual-Column Architecture for Zero-Downtime Security Updates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Large tokenized databases face security compromises over time, requiring periodic token updates that necessitate system downtime, which is unacceptable for large databases.
Innovation Solution
Implementing two token fields with an active token flag and token version field to allow one inactive token field to be updated while the active field remains available, enabling updates during processing time without downtime.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If tokens are updated periodically to maintain security, then security is improved, but system downtime increases
Solution Approach 1:
The token storage structure is segmented into two separate token columns (first token column and second token column) within the same token table. This segmentation allows the system to switch between different token sets, enabling one token column to be updated while the other remains active for data access, thus avoiding system downtime during token updates.
Solution Approach 2:
The system performs preliminary actions by pre-generating and storing multiple sets of tokens (first and second token columns) before an update is needed. When a token update is required, the system can immediately switch to a pre-prepared token column, allowing updates to occur without interrupting data access operations.
2Reliability
If tokens are updated frequently to prevent compromise, then security is improved, but processing overhead increases
Solution Approach 1:
The system implements dynamic token management through an active token flag that indicates which token column is currently active. This dynamic switching mechanism allows the system to efficiently alternate between token columns based on update needs, minimizing processing overhead while maintaining security through frequent token rotation.
Data Source
AI summary
A method includes (a) selecting a first token column or a second token column of a token table as an active token column based upon the value of a current token flag, (b) selecting a row of the token table uniquely associated with a sensitive piece of data, the selected row having a first token field storing a first token value and a second token field storing a second token value, (c) selectively extracting an active token value from the first token field when the first token column is the active token column and from the second token field when the second token column is the active token column, (d) selecting a row of a data table having the extracted active token value within a token field, and (e) causing contents of the selected row of the data table to be displayed to a user over a user interface.