Centralized Key Management with Dual Authenticator Verification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Managing cryptographic keys across multiple clients with varying requirements is burdensome and complex, leading to increased resource usage and complexity in key management systems.

Innovation Solution

A centralized key management system that authenticates clients using a client authenticator and token authenticator pair, generates and manages customer keys and tokens, and verifies ownership using a master key, allowing clients to encrypt/decrypt data while reducing the need for local key management resources.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If a centralized key management system is implemented to manage cryptographic keys for multiple clients, then key management complexity and resource usage are reduced, but the system requires a more sophisticated authentication and verification mechanism

Engineering Contradiction:
Improvekey management complexityVSAvoidauthentication mechanism sophistication
Core Design Contradiction:
Device complexityVSExtent of automation

Solution Approach 1:

The authentication mechanism is segmented into two distinct components: a client authenticator provided to the client and a token authenticator embedded in the token. This segmentation allows the centralized key management system to verify client identity through comparison of these two components, reducing the need for complex centralized verification while maintaining security.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The client authenticator is generated and provided to the client in advance, before the actual key retrieval operation. This preliminary action allows the client to present the authenticator with their token, enabling the key management system to perform a simple comparison operation rather than conducting a complex verification process at the time of key retrieval.

Inventive Principle:
Principle #10Preliminary action

2Productivity

If cryptographic keys are distributed to clients for local storage and management, then clients can independently encrypt/decrypt data, but the risk of key compromise and the burden of secure local key management increases

Engineering Contradiction:
Improvedata encryption/decryption efficiencyVSAvoidkey security
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The critical security function of key verification is extracted from the client system and centralized in the key management system. The client receives only the token and client authenticator, but the actual verification of whether the client is authorized to use the key is performed by the key management system through comparison of the token authenticator with the client authenticator. This extraction allows clients to efficiently encrypt/decrypt data while the centralized system maintains security control.

Inventive Principle:
Principle #2Taking out (Extraction)

3Adaptability or versatility

If multiple different key management systems are provided for different clients with varying requirements, then each client's specific security needs are met, but the overall system complexity and resource consumption increase significantly

Engineering Contradiction:
Improveclient-specific security requirements fulfillmentVSAvoidoverall system complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The key management system implements a universal authentication mechanism that can serve multiple clients with different requirements through a single standardized process. The token-based approach with authenticator comparison can be applied uniformly across all clients, whether they require individual key management, group key management, or temporary key access. This universality allows the system to adapt to various client needs without requiring separate key management infrastructures for each client type.

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

Data Source

PatentUS7925023B2Method and apparatus for managing cryptographic keys
Publication Date: 2011.04.12 ORACLE INT CORP
  • US7925023B2 patent drawing
  • US7925023B2 patent drawing
  • US7925023B2 patent drawing

AI summary

One embodiment of the present invention provides a system for managing keys. During operation, the system authenticates a client at a key manager. Next, the system receives a token from the client at the key manager, wherein the token is associated with a customer key, and includes a token authenticator. This token authenticator comprises one-half of an authenticator pair which is used to determine if the client is the owner of the customer key. Next, the system decrypts the token using a master key. The system then verifies a client authenticator, which comprises the other half of the authenticator pair which is used to determine if the client is the owner of the customer key. If the client is the owner of the customer key, the system sends the customer key to the client, which enables the client to encrypt/decrypt data. Finally, the client deletes the customer key.