Secure Key Distribution Service Identity Verification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In dynamic server environments, traditional methods for identifying and distributing sensitive data, such as encryption keys, are either insecure or incur significant operational overhead, making it difficult to manage validation and distribution efficiently.

Innovation Solution

A secure key distribution service (SKDS) that assigns a fully qualified domain name (FQDN) to servers during setup, registers it with a directory service, and uses this information to securely distribute keys without requiring a pre-shared secret, by comparing the FQDN and network address to verify identity and retrieve keys from a key storage module.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional secure identification methods are used to distribute encryption keys, then security is improved, but operational overhead increases significantly

Engineering Contradiction:
ImprovesecurityVSAvoidoperational overhead
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a key distribution service as an intermediary component that mediates between key storage and requesting servers. This service handles the complex trust relationship establishment and key distribution logic centrally, eliminating the need for each server to implement complex secure identification protocols independently. The intermediary absorbs the operational overhead while maintaining security.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system segments the key distribution functionality into separate components: a key distribution service that handles identification and authorization, a key storage module that securely holds keys, and client servers that simply request keys. This segmentation allows each component to be optimized independently, reducing the operational overhead on servers while maintaining security through specialized handling in the distribution service.

Inventive Principle:
Principle #1Segmentation

2Device complexity

If minimal overhead identification methods are used, then operational overhead is reduced, but security is compromised

Engineering Contradiction:
Improveoperational overheadVSAvoidsecurity
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The system performs preliminary actions by establishing trust relationships and registering server identities with the key distribution service during initial server setup and deployment. This preliminary identification and registration work is done once during provisioning, allowing servers to subsequently request keys with minimal overhead using their pre-registered identities without needing to perform complex security handshakes each time.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If pre-shared secrets are required for secure key distribution, then security is improved, but device complexity and setup complexity increase

Engineering Contradiction:
ImprovesecurityVSAvoidsetup complexity
Core Design Contradiction:
ReliabilityVSEase of manufacture

Solution Approach 1:

The key distribution service enables servers to self-identify and authenticate using their FQDN and network address that are automatically resolved through DNS. Servers don't need manual configuration of pre-shared secrets or complex authentication credentials. The system automatically retrieves the server's identity information and uses it to establish secure key distribution, eliminating manual setup complexity while maintaining security.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS9252947B1Secure key distribution service
Publication Date: 2016.02.02 AMAZON TECH INC
  • US9252947B1 patent drawing
  • US9252947B1 patent drawing
  • US9252947B1 patent drawing

AI summary

A secure key distribution server (SKDS) determines the identity of a requesting server without use of a shared secret by resolving the fully qualified domain name (FQDN) to a network address and comparing it with the network address of a key request. A credential string may also be used as part of the identification. Once identity is established, keys may be securely distributed. The SKDS may also be implemented in a peer-to-peer configuration.