Key Enclave for Delegated Cryptographic Authentication

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current cryptographic systems face challenges in securely managing and protecting cryptographic keys, often requiring duplicate key distribution and exposing private keys, which compromises system security.

Innovation Solution

The implementation of a key enclave that stores and manages cryptographic keys in an isolated environment, allowing for device-agnostic delegation of access to key operations while keeping private keys secure, using a secure channel for authentication and verification over wireless communications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If cryptographic keys are kept in the same location as where cryptographic operations are performed, then ease of operation is improved, but security is worsened due to duplicate key distribution and exposure of private keys

Engineering Contradiction:
Improveease of cryptographic operationsVSAvoidsecurity of cryptographic keys
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The system segments the cryptographic key management by separating the private key storage (in the key enclave) from the cryptographic operation execution (on the delegate computer). The private key is divided into key shares that are stored securely in the enclave, while the delegate computer performs operations using these shared keys without having access to the complete private key.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The key enclave acts as an intermediary between the secure key storage and the delegate computer. It mediates cryptographic operations by receiving requests from the delegate computer, performing the operations using the stored private key, and returning results without exposing the private key itself. This intermediary mechanism enables secure key management while maintaining operational capability.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If private keys are distributed to multiple devices for cryptographic operations, then adaptability is improved, but security is worsened due to increased exposure risk

Engineering Contradiction:
Improveaccess to cryptographic operationsVSAvoidexposure of private keys
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The private key is segmented into multiple key shares that are distributed to different devices including the key enclave and delegate computers. No single device possesses the complete private key, which prevents exposure risk while maintaining adaptability across multiple devices for cryptographic operations.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Different devices have different levels of access to key material. The key enclave has secure storage of key shares, while delegate computers have limited access for performing specific operations. This local quality differentiation ensures that each device has appropriate access rights without compromising overall security.

Inventive Principle:
Principle #3Local quality

3Reliability

If cryptographic operations are centralized in one location, then security is improved by protecting private keys, but device complexity increases due to key management infrastructure

Engineering Contradiction:
Improveprotection of private keysVSAvoidkey management system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The key enclave serves as a specialized intermediary component that handles key management complexity. By isolating the key management infrastructure into a dedicated enclave, the system protects private keys while managing the complexity in a contained manner that doesn't propagate to the entire system.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The key management functionality is extracted from the general cryptographic operation system and placed into a separate key enclave. This extraction isolates the complexity of key management into a dedicated component, protecting private keys while allowing the rest of the system to operate with simpler key access mechanisms.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS20180041484A1Systems and methods for delegated cryptography
Publication Date: 2018.02.08 KRYPTCO INC
  • US20180041484A1 patent drawing
  • US20180041484A1 patent drawing
  • US20180041484A1 patent drawing

AI summary

In some embodiments, an authentication method comprises receiving a request for a digital signature of data from a delegate computer over a secure channel using cryptography to provide authentication, wherein the secure channel comprises at least one wireless communications link; displaying information derived from the data; prompting a user for approval of the request with information derived from the data; in response to receiving approval from the user, creating the digital signature of the data using one or more private keys stored in a key enclave; and sending the digital signature to the delegate computer over the secure channel.