Secure Database Architecture for Record-Level Access and Audit Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current database systems lack granular privacy and data usage policies, leading to potential security vulnerabilities and lack of accountability, as they often rely on application-level security that can be bypassed, and do not provide transparent data ownership and usage tracking.

Innovation Solution

A secure database system utilizing blockchain technology and encryption ensures granular control over data access and ownership, encrypting data with multiple keys and storing it across distributed nodes, with audit logs maintained on a distributed ledger to track access and enforce permissions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If standard database systems are used with application-level security, then ease of operation is improved, but data security and privacy protection deteriorate

Engineering Contradiction:
Improveease of operationVSAvoiddata security
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent segments data security control to the individual record level rather than application-level. Each data record has its own encryption keys and access control policies, allowing fine-grained security management. This segmentation enables the database system to maintain ease of operation while improving data security through granular access control at the core database level.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary layer of cryptographic key management and policy enforcement within the core database system. Encryption keys are managed separately from data, and policy enforcement mechanisms act as intermediaries between users and data records. This intermediary approach maintains operational simplicity while enhancing security through automated key management and policy validation.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of manufacture

If broad privacy policies are implemented across multiple entities, then ease of manufacture is improved, but measurement precision of data ownership and accountability deteriorates

Engineering Contradiction:
Improveease of manufactureVSAvoiddata ownership tracking
Core Design Contradiction:
Ease of manufactureVSMeasurement precision

Solution Approach 1:

The patent applies local quality by assigning unique encryption keys and access policies to each data record rather than applying broad policies uniformly. Each record can have its own ownership attributes and access control settings, enabling precise tracking of data ownership and usage. This local-level customization maintains ease of policy implementation while dramatically improving the precision of ownership tracking and accountability.

Inventive Principle:
Principle #3Local quality

3Adaptability or versatility

If encryption schemes are built into the application layer, then adaptability is improved, but device complexity increases

Engineering Contradiction:
ImproveadaptabilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent merges encryption and key management functionality into the core database system rather than keeping it separate in the application layer. This consolidation reduces overall system complexity by eliminating redundant encryption operations at multiple layers. The database engine itself handles encryption, key management, and policy enforcement, providing adaptability while reducing device complexity through centralized management.

Inventive Principle:
Principle #5Merging (Combining)

4Ease of operation

If administrators and analysts have direct database access, then ease of operation is improved, but harmful factors increase due to potential policy violations

Engineering Contradiction:
Improveease of operationVSAvoidprivacy policy violations
Core Design Contradiction:
Ease of operationVSObject-generated harmful factors

Solution Approach 1:

The patent applies preliminary anti-action by implementing automated policy enforcement and audit logging at the core database level before administrators or analysts can violate privacy policies. Access requests are automatically validated against encryption keys and policy rules, preventing unauthorized access before it occurs. This preemptive approach maintains ease of operation for authorized users while automatically blocking policy violations, thereby reducing harmful factors.

Inventive Principle:
Principle #9Preliminary anti-action

Data Source

PatentUS12481771B2System and method for operating a secure database
Publication Date: 2025.11.25 THE ETHICAL IDENTITY CO
  • US12481771B2 patent drawing
  • US12481771B2 patent drawing
  • US12481771B2 patent drawing

AI summary

Various implementations of a system and method may include a secure database that can be structured with a strong emphasis on individual entity permissions and enforcement of read, write, and audit policies relative to individual database record entries to close security and privacy gaps that exist in current database systems.