Database Connector Attribute-Based Encryption Key Segmentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current database encryption techniques often limit functionality and have vulnerabilities, as they provide the same level of security to all data, even if only a portion requires it, and rely on symmetric keys that are difficult to manage for access control.

Innovation Solution

Implementing attribute-based encryption (ABE) in a database connector to encrypt data based on logical attribute statements, allowing different data to be protected at different security levels, with private keys encoding specific attributes for decryption.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If symmetric key encryption is used for database security, then data protection is achieved, but key management complexity and access control difficulty increase

Engineering Contradiction:
Improvedata securityVSAvoidkey management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the single symmetric key into multiple private keys distributed to different applications. Each application has its own private key, eliminating the need for a centralized key management system. The encryption key is divided such that no single application holds the complete decryption capability, thereby reducing key management complexity while maintaining security.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a database connector as an intermediary between applications and the database. The connector manages the encryption and decryption processes, holding the segmented key components and coordinating access. This intermediary approach simplifies access control by centralizing key management logic in the connector rather than requiring complex distributed key management across all applications.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If entire database is encrypted with single key, then security is provided uniformly, but functionality is limited and vulnerability increases

Engineering Contradiction:
Improvesecurity levelVSAvoiddatabase functionality
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent implements local quality by allowing different segments of the database to be encrypted with different key segments tailored to specific applications. Each application's private key is designed to decrypt only the data segments it needs, providing customized security levels for different data portions. This enables fine-grained access control where security requirements vary by data type and application, thereby maintaining functionality while enhancing security.

Inventive Principle:
Principle #3Local quality

3Reliability

If individual rows or columns are encrypted, then selective security is achieved, but system complexity increases

Engineering Contradiction:
Improveselective securityVSAvoidencryption system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent creates a universal encryption system where the database connector handles all encryption and decryption operations for the entire database using a unified approach. The same connector infrastructure and key segmentation mechanism apply regardless of which data segment needs access. This multi-functional design allows selective security for individual rows or columns without requiring separate encryption systems for each data element, thereby reducing overall system complexity.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS11822674B1Blockchain provenance information for database
Publication Date: 2023.11.21 ARCHITECTURE TECH CORP
  • US11822674B1 patent drawing
  • US11822674B1 patent drawing
  • US11822674B1 patent drawing

AI summary

Embodiments for a method of tracking provenance information for data in a database are disclosed. The method includes storing data in a first one or more cells of a database, translating provenance information for the data into a new block for a provenance blockchain corresponding to the first one or more cells, and storing the new block in the database.