Certificate Authentication via Segmented Records

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional secure online systems face inefficiencies in managing and distributing large certificate revocation lists (CRLs), which are time-consuming and vulnerable to security attacks, especially in large-scale systems where immediate access to current CRLs is necessary.

Innovation Solution

A system and method for efficient certificate authentication management using a structured data source, such as an XML file or database, where each security certificate is encoded with a unique record ID, allowing for rapid and secure authentication across multiple private gateway server nodes, with each record using four bits or less, enabling fast indexing and small data size for efficient distribution.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional certificate revocation lists are used to track revoked certificates, then security validation is maintained, but the system becomes inefficient and vulnerable when scaling to large numbers of certificates

Engineering Contradiction:
Improvecertificate authentication securityVSAvoidauthentication speed
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent segments the monolithic CRL into individual certificate status records distributed across multiple backend authentication databases. Each private gateway server node can independently query and cache relevant certificate status information without needing to retrieve entire CRLs, enabling parallel processing and faster authentication decisions while maintaining security validation.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary actions by allowing private gateway server nodes to cache certificate status information locally before authentication requests occur. This pre-caching mechanism reduces real-time network dependencies and enables rapid authentication decisions even when backend databases are temporarily unavailable, maintaining both security and speed.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If large certificate revocation lists are distributed to multiple gateways, then all nodes can validate certificates, but data distribution becomes inefficient and time-consuming

Engineering Contradiction:
Improvesystem scalabilityVSAvoidCRL distribution time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent divides the large CRL into smaller, manageable certificate status records that can be independently distributed and cached at each private gateway server node. This segmentation allows incremental updates where only changed or relevant portions need to be transmitted, dramatically reducing distribution time while enabling the system to scale to accommodate additional gateways without proportional increases in distribution overhead.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Each private gateway server node maintains local cache of certificate status information tailored to its specific authentication needs. This local quality approach allows each node to have optimized, relevant data locally available, eliminating the need to distribute entire CRLs to every node and reducing both distribution time and network bandwidth consumption while maintaining scalability.

Inventive Principle:
Principle #3Local quality

3Reliability

If systems check remotely-located CRLs for certificate validation, then centralized control is maintained, but the system becomes vulnerable to security attacks and connectivity failures

Engineering Contradiction:
Improvecentralized certificate controlVSAvoidsecurity attack vulnerability
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The system performs preliminary actions by caching certificate status information locally at private gateway server nodes before authentication requests arrive. This pre-caching creates a buffer that allows the system to maintain centralized control through periodic backend updates while protecting against security attacks and connectivity failures during actual authentication operations, as decisions can be made based on cached data.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces an intermediary layer consisting of private gateway server nodes that mediate between the centralized backend authentication databases and the authentication requests. These intermediaries cache and validate certificate status information locally, reducing direct dependencies on remote CRL checks and protecting the system from security attacks targeting centralized CRL distribution while maintaining centralized control through periodic synchronization.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Device complexity

If hourly or daily CRL publication is used instead of immediate notification, then system complexity is reduced, but authentication reliability deteriorates

Engineering Contradiction:
ImproveCRL management complexityVSAvoidcertificate revocation timeliness
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent implements a dynamic CRL distribution model where private gateway server nodes can cache certificate status information for extended periods and update their caches asynchronously based on actual changes in certificate status. This dynamic approach allows the system to operate with reduced complexity compared to immediate real-time updates while maintaining authentication reliability, as nodes automatically refresh their cached data when backend databases indicate changes have occurred.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS10530587B2Web scale authentication
Publication Date: 2020.01.07 OPENVPN INC
  • US10530587B2 patent drawing

AI summary

A system and method for efficient certificate authentication management and distribution of large, web scale authentication information. The method includes receiving at a server, security certificate information, said security certificate including a unique certificate identifier. A structured data source, such as an XML file or database is encoded with a unique record for each possible security certificate using the record ID as the security certificate ID. Each unique record includes a record of four bits or less. Owing to the small size of the data source, large amounts of security certificates may be managed and distributed efficiently over a network to one of more private gateways allowing for large scale certificate authentication.