Key Containers for Secure User Authentication

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing user devices lack hardware-based security mechanisms to securely authenticate users, making locally stored private keys vulnerable to attacks, especially when devices are lost or stolen, and hardware-based security mechanisms are not accessible to all processes, including non-certified applications.

Innovation Solution

A system where an authenticator process on the user device verifies user authentication by comparing user-supplied credentials to stored ones, generates a digitally signed authentication assertion using a signing key stored on a separate key container server, and destroys the signing key to maintain security, eliminating reliance on hardware-based security mechanisms.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If hardware-based security mechanisms are used to store private keys, then security is improved, but device compatibility and accessibility to all processes deteriorate

Engineering Contradiction:
ImprovesecurityVSAvoiddevice compatibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

A secure enclave process acts as an intermediary between applications and the hardware security mechanism. This mediator manages cryptographic keys and operations within the secure environment while providing standardized interfaces to applications, thereby maintaining security without requiring direct hardware access for all processes. This resolves the contradiction by enabling secure operations for non-certified applications through the intermediary layer.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Speed

If private keys are stored locally on user devices, then authentication speed is improved, but security against attacks deteriorates

Engineering Contradiction:
Improveauthentication speedVSAvoidvulnerability to attacks
Core Design Contradiction:
SpeedVSObject-affected harmful factors

Solution Approach 1:

The most critical security function (key storage and cryptographic operations) is extracted from the general-purpose processing environment and placed into a dedicated secure enclave. This separation allows fast authentication operations to occur in the secure environment while the host system remains vulnerable to attacks, thus achieving both speed and security.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system prepares cryptographic keys and security credentials in advance within the secure enclave, before any authentication attack can occur. This pre-positioning of security measures in a protected environment cushions the system against potential attacks while maintaining ready-to-use authentication capabilities for normal operations.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

3Reliability

If hardware-protected execution regions are used, then security is improved, but accessibility to non-certified processes deteriorates

Engineering Contradiction:
ImprovesecurityVSAvoidaccessibility
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The secure enclave process provides universal access to cryptographic operations for all applications, regardless of certification status. By implementing a standardized interface that multiple applications can use, the system achieves both security through hardware protection and accessibility for non-certified processes through the multi-functional secure enclave service.

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

4Reliability

If private keys are embedded in device hardware, then security is improved, but flexibility and adaptability deteriorate

Engineering Contradiction:
ImprovesecurityVSAvoidflexibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The system dynamically manages cryptographic keys within the secure enclave, allowing keys to be created, stored, and used based on application needs rather than being statically embedded. This dynamic key management provides both the security of hardware-based storage and the flexibility to adapt to different applications and scenarios.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS9942042B1Key containers for securely asserting user authentication
Publication Date: 2018.04.10 EMC IP HLDG CO LLC
  • US9942042B1 patent drawing
  • US9942042B1 patent drawing
  • US9942042B1 patent drawing

AI summary

A digitally signed authentication assertion is generated in response to successful authentication of a current user of a user device by using a signing key that is uniquely assigned to the authenticator process to digitally sign a document indicating that the current user of the user device was successfully authenticated on the user device. The signing key uniquely assigned to the authenticator process is stored in a key container associated with the user device, and the key container is located on a key container server that is physically separate from the user device. The digitally signed authentication assertion is conveyed from the authenticator process to an authentication service, in order to securely indicate to the authentication service that the current user of the user device has been verified as an authentic user by the authenticator process.