Authentication Code Caching for HSM Delay Reduction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional systems relying on hardware security modules (HSMs) for data authentication face processing power and availability limitations, leading to delays and negative user experiences, especially during high-volume authentication requests.

Innovation Solution

Implementing a pre-generated authentication code derived from an HSM-generated verification code, stored in association with the user's account, to authenticate requests when the HSM is unavailable, using hash-based message authentication codes (HMAC) to reduce delays.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If HSMs are used for secure authentication, then security is improved, but authentication speed deteriorates due to processing power limitations

Engineering Contradiction:
ImprovesecurityVSAvoidauthentication speed
Core Design Contradiction:
ReliabilityVSSpeed

Solution Approach 1:

The system pre-generates authentication codes using HMAC functions before authentication requests arrive. These pre-generated codes are stored and can be immediately used when authentication is needed, eliminating the delay of real-time HSM processing while maintaining security.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system creates copies of authentication codes generated by HSMs and stores them for later use. Instead of requiring the original HSM to be available for every authentication, the system uses these pre-generated code copies, which can be retrieved and verified quickly without HSM involvement.

Inventive Principle:
Principle #26Copying

2Reliability

If HSMs are used for authentication, then security is improved, but system availability deteriorates during high-volume requests

Engineering Contradiction:
ImprovesecurityVSAvoidsystem availability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

Authentication codes are pre-generated and stored in advance, so when high-volume requests occur and HSMs are unavailable, the system can still authenticate users by retrieving and verifying these pre-generated codes, maintaining system availability during peak loads.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system introduces pre-generated authentication codes as an intermediary mechanism between the HSM and the authentication process. When HSMs are unavailable, this intermediary allows authentication to proceed without direct HSM involvement, ensuring continuous system operation.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Measurement precision

If real-time HSM processing is used, then authentication accuracy is improved, but authentication time increases causing user frustration

Engineering Contradiction:
Improveauthentication accuracyVSAvoidauthentication time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system performs authentication code generation in advance using HMAC functions and stores these codes for immediate retrieval. This eliminates the real-time processing delay while maintaining authentication accuracy, as the pre-generated codes are verified against stored values without requiring time-consuming HSM operations.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20260039477A1System and method for reducing authentication delays related to security module processing
Publication Date: 2026.02.05 CAPITAL ONE SERVICES LLC
  • US20260039477A1 patent drawing
  • US20260039477A1 patent drawing
  • US20260039477A1 patent drawing

AI summary

In some embodiments, reducing authentication delays related to security module processing may be facilitated. In some embodiments, a first authentication code may be generated based on a first verification code associated with an account. The first authentication code may be stored in association with the account. An authentication request may be obtained to authenticate an action, and the authentication request may comprise a second verification code. A security module request may be generated for a security module response related to the second verification code. A second authentication code may be generated based on the second verification code. Based on a determination that the second authentication code corresponds to the first authentication code, an authentication response for the authentication request may be provided.