Database Reference Mapping for Secure Plain-Text Data Storage

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing database security measures are inadequate against internal attackers who can modify or exfiltrate confidential data, often masking their activity by deleting access logs, and traditional approaches are difficult to administer or break backward compatibility.

Innovation Solution

Replace plain-text values in databases with cryptographic hash digests or random references, maintaining relationships and associations while securing the data, and implement a system to transparently manage data access and retrieval.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional database security measures (air-gapping, permission schemes) are implemented, then data security is improved, but administrative complexity increases and backward compatibility is broken

Engineering Contradiction:

Improvedata securityVSAvoidadministrative complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments data into two types: reference data (stored in the database) and distinct data (stored externally). This segmentation allows the database to maintain simple reference structures while sensitive data resides in a more secure external location, reducing administrative overhead compared to comprehensive air-gapping approaches.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary reference mechanism that mediates between the database and external data storage. Instead of direct access to sensitive data, systems interact through reference values, providing security without requiring complex permission schemes or air-gapping infrastructure.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If air-gapping is implemented to secure data, then data security is improved, but access speed decreases and administrative burden increases

Engineering Contradiction:

Improvedata securityVSAvoiddata access speed

Core Design Contradiction:

ReliabilityVSSpeed

Solution Approach 1:

By segmenting data into references (in database) and distinct values (external), the system enables fast access to reference data while sensitive data remains securely isolated. This avoids the performance penalty of air-gapping entire databases while maintaining security for sensitive information.

Inventive Principle:

Principle #1Segmentation

3Reliability

If permission schemes are implemented to control access, then data security is improved, but ease of operation decreases

Engineering Contradiction:

Improvedata securityVSAvoidease of administration

Core Design Contradiction:

ReliabilityVSEase of operation

Solution Approach 1:

The reference mechanism acts as an intermediary that simplifies access control. Instead of managing complex permissions for sensitive data, the system uses reference values that inherently control access - the reference itself is the security mechanism, eliminating the need for baroque permission schemes.

Inventive Principle:

Principle #24Intermediary (Mediator)

4Adaptability or versatility

If traditional database structures are used, then backward compatibility is maintained, but data security against internal attackers is insufficient

Engineering Contradiction:

Improvebackward compatibilityVSAvoiddata security

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The patent maintains backward compatibility by keeping reference data in the traditional database structure while segmenting distinct data to external storage. This allows existing applications to continue using the database as before, while sensitive data gains enhanced security through the segmentation approach.

Inventive Principle:

Principle #1Segmentation

5Ease of operation

If plain-text values are stored in the database, then data accessibility is improved, but data security deteriorates

Engineering Contradiction:

Improvedata accessibilityVSAvoiddata security

Core Design Contradiction:

Ease of operationVSReliability

Solution Approach 1:

The patent segments data into reference values (stored in database for easy access) and distinct values (stored externally for security). This segmentation maintains accessibility for applications using reference data while protecting sensitive distinct data from internal threats.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent extracts sensitive distinct data from the database and stores it externally, while keeping only non-sensitive reference data in the database. This extraction maintains accessibility for reference data while removing the security risk of storing sensitive plain-text values in the database.

Inventive Principle:

Principle #2Taking out (Extraction)

Data Source

PatentUS12566879B2Replacing distinct data in a relational database with a distinct reference to that data and distinct de-referencing of database data

Publication Date: 2026.03.03 ALTR SOLUTIONS INC

AI summary

Provided is a process including: obtaining criteria to select plain-text values in a lower-trust database; selecting, based on the criteria, a first plain-text value; in response, determining a first reference value; storing the first plain-text value in a higher-trust database in a second entry identified by the first reference value; storing the first reference value in the first entry of the lower-trust database; selecting another instance of the first plain-text value stored requested to be stored in a third entry in the lower-trust database; and in response, storing the first reference value in the third entry.