Database Record Encryption via Metadata-Driven Key Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current encryption solutions for database management systems require significant user training and application modification, making them burdensome and inefficient for securing sensitive data.

Innovation Solution

A method and system that utilize encryption metadata to determine encryption keys for database files, allowing for transparent encryption and decryption operations without modifying database applications, using an encryption manager that provides a layer of processing between the database server and storage, enabling field or record-level encryption with a master key for security.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If current encryption solutions are implemented, then security for database information is improved, but user training requirements and application modification complexity increase

Engineering Contradiction:
ImprovesecurityVSAvoidapplication modification complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces an encryption manager as an intermediary component between the database server and storage devices. This encryption manager handles all encryption and decryption operations transparently, eliminating the need for users to directly interact with complex encryption commands or modify database applications. The encryption manager mediates between the database server's read/write requests and the storage devices, automatically applying encryption based on metadata associated with database files.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If encryption services are added through add-on programs, then data protection is improved, but ease of operation deteriorates due to required user training

Engineering Contradiction:
Improvedata protectionVSAvoidease of operation
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The encryption manager operates autonomously to perform encryption and decryption operations without requiring user intervention or training. The system automatically manages encryption keys, applies encryption based on file metadata, and handles decryption of retrieved data. This self-service approach eliminates the need for users to learn encryption commands or understand cryptographic concepts, maintaining ease of operation while providing robust data protection.

Inventive Principle:
Principle #25Self-service

3Reliability

If database applications are modified to incorporate encryption commands, then security is improved, but productivity decreases due to modification burden

Engineering Contradiction:
ImprovesecurityVSAvoidproductivity
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The encryption manager serves as an intermediary layer that intercepts database server requests before they reach storage devices and processes the encryption/decryption automatically. This eliminates the need to modify existing database applications, as the encryption functionality is injected at the server level. Users can continue to operate existing applications without changes, maintaining productivity while achieving enhanced security through the intermediary encryption layer.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS7904732B2Encrypting and decrypting database records
Publication Date: 2011.03.08 ROCKET SOFTWARE
  • US7904732B2 patent drawing
  • US7904732B2 patent drawing
  • US7904732B2 patent drawing

AI summary

Provided are a method, system, and article of manufacture for encrypting and decrypting database records. Encryption metadata is provided for a database file having fields, wherein the encryption metadata indicates at least one encryption key for the file. A request is received to perform a read or write operation with respect to a record including the fields for the database file. A determination is made from the encryption metadata of the at least one encryption key for the database file. The determined encryption key is used to encrypt or decrypt for the read or write operation with respect to at least one of the fields in the database file.