Secure Communications Protocol with Centralized Key Rotation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing cryptographic key management systems in large networks are complex and resource-intensive, particularly in public internet communications, making them difficult to manage and vulnerable to security threats.

Innovation Solution

A zero-trust communications scheme using a central signing service that issues short-lived public-private key pairs, validated through a DNS signature and access token, ensuring secure communication by regularly rotating keys and minimizing reliance on Hardware Security Modules (HSMs).

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If pre-shared keys or certifications from trusted certificate authorities are used, then secure communication is achieved, but device complexity and operational processes become complex in large networks

Engineering Contradiction:
Improvesecure communicationVSAvoidkey management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts the key management function from individual servers and places it in a centralized signing service. Each server no longer manages its own complex key operations but instead obtains signatures from the central service, simplifying individual server operations while maintaining security.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The central signing service provides universal key management functionality to all servers in the network. A single centralized system performs the complex cryptographic operations for multiple servers, eliminating the need for each server to have its own key management infrastructure.

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

2Reliability

If each server has its own cryptographic keys, then secure communication is enabled, but computing resources and operational processes become significant

Engineering Contradiction:
Improvesecure communicationVSAvoidcomputing resources
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent merges the key management computing resources into a single centralized signing service. Instead of each server independently performing cryptographic operations, all servers share the computational burden with the central service, reducing overall resource consumption.

Inventive Principle:
Principle #5Merging (Combining)

3Device complexity

If long-lived cryptographic keys are used, then key management is simplified, but the window of opportunity for key compromise increases

Engineering Contradiction:
Improvekey management simplicityVSAvoidkey compromise risk
Core Design Contradiction:
Device complexityVSObject-affected harmful factors

Solution Approach 1:

The patent implements periodic key rotation where servers obtain new signatures from the central signing service at regular intervals. This periodic renewal of cryptographic credentials limits the window of opportunity for key compromise while maintaining simplified management through automation.

Inventive Principle:
Principle #19Periodic action

Solution Approach 2:

The central signing service provides feedback to servers about the status of their cryptographic credentials and enables automatic renewal. This feedback mechanism ensures keys are rotated timely without requiring manual intervention, balancing security with management simplicity.

Inventive Principle:
Principle #23Feedback

Data Source

PatentEP4475484B1Secure communications network protocol
Publication Date: 2025.07.30 MASTERCARD INT INC
  • EP4475484B1 patent drawingFigure 1
  • EP4475484B1 patent drawingFigure 2
  • EP4475484B1 patent drawingFigure 3

AI summary

A computer-implemented method is disclosed for generating a digital signature for a participant entity (102, 104) of a secure communications network system comprising a central signing service (106) in a public network, the method performed by the central signing service, comprising: receiving (216) an endpoint signature request from the participant entity for an endpoint associated with the participant entity, the endpoint signature request comprising a domain name and an access token; validating (218) the access token and looking up the domain name in a data store of the central signing service; retrieving (220) a domain name system, DNS, signature of the participant entity; and validating (222) the DNS signature using a private key of the central signing service, where on successful validation of the DNS signature, the method further comprises the steps of: retrieving (226) a configuration of the endpoint; generating (230) an endpoint signature from the configuration; and sending the endpoint signature to the participant entity.