Floating Point Cohort Encryption Key Version Storage

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing format-preserving encryption techniques for floating point numbers require external storage for key versions, complicating schema management in databases and increasing security risks.

Innovation Solution

The method involves storing the key version within the floating point number itself by determining a floating point cohort and using the exponent as the key version, eliminating the need for secondary storage and enhancing security.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If external storage is used for key versions in format-preserving encryption, then key management is possible, but storage system complexity increases and security risks increase

Engineering Contradiction:

Improveencryption securityVSAvoidstorage system complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent merges the key version information with the encrypted floating point number by embedding it in the exponent field of the same data structure. This eliminates the need for separate external storage systems for key versions, thereby reducing storage system complexity while maintaining encryption security.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The key version is nested within the encrypted data structure itself, specifically stored in the exponent field of the floating point number. This nested approach allows the key version to be contained within the same storage location as the encrypted data, reducing the need for additional storage systems.

Inventive Principle:

Principle #7Nested doll (Nesting)

2Reliability

If external storage is used for key versions, then key version tracking is enabled, but the risk of key compromise increases

Engineering Contradiction:

Improvekey version trackingVSAvoidkey compromise risk

Core Design Contradiction:

ReliabilityVSObject-affected harmful factors

Solution Approach 1:

By combining the key version with the encrypted floating point number in the same data structure, the patent ensures that key version tracking is maintained while reducing the attack surface. The key version is no longer stored separately in external systems that could be compromised independently.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The exponent field acts as an intermediary that safely holds the key version information within the encrypted data structure. This intermediary approach allows key version tracking without requiring separate external storage systems that could become security vulnerabilities.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Reliability

If separate storage for key versions is implemented, then encryption functionality is complete, but database schema management becomes complicated

Engineering Contradiction:

Improveencryption functionalityVSAvoidschema management complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent combines key version storage with the existing floating point number storage by utilizing the exponent field. This merging eliminates the need for separate columns or tables for key version storage, thereby simplifying database schema management while maintaining complete encryption functionality.

Inventive Principle:

Principle #5Merging (Combining)

Data Source

PatentUS10505714B2Floating point cohort based encryption

Publication Date: 2019.12.10 MICRO FOCUS LLC

AI summary

In some examples, floating point cohort based encryption may include determining an exponent of a floating point cohort.