Zero-Trust Network Authentication via Distributed Node Validation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional software-based systems rely on a single central authority for authentication, making them vulnerable to internal and external compromises, as the trusted resource can be compromised by malicious or negligent internal parties, leading to system integrity violations.

Innovation Solution

Implementing a zero-trust network system where all nodes mutually authorize and unauthorize each other, with a directory system and monitor system ensuring that no single point of failure exists, by randomly selecting nodes for validation and requiring co-authentication from multiple agents, thus eliminating the opportunity for identity spoofing and reducing the likelihood of system compromise.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If a single central authority is used for authentication, then authentication efficiency is improved, but system security deteriorates due to vulnerability to compromise

Engineering Contradiction:
Improveauthentication efficiencyVSAvoidsystem security
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent segments the centralized authentication authority into multiple distributed authority nodes. Instead of relying on a single central authority, the system distributes authentication functions across multiple nodes, so that no single point of failure exists. This segmentation resolves the contradiction by maintaining authentication efficiency through distributed parallel processing while improving security by eliminating the single-point vulnerability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces intermediary components including a directory system that maintains node information and a monitor system that oversees authentication processes. These intermediaries coordinate between multiple authority nodes and clients, enabling efficient distributed authentication while enhancing security through additional validation layers and monitoring capabilities.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If multiple parties are involved in authentication, then system security is improved, but authentication complexity increases

Engineering Contradiction:
Improvesystem securityVSAvoidauthentication complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent designs authority nodes with universal functionality that can perform multiple roles: acting as authentication authorities, serving as directory services, and functioning as monitor nodes. This multi-functionality reduces overall system complexity by eliminating the need for separate specialized components for each function, while still maintaining the security benefits of multi-party involvement.

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

Solution Approach 2:

The system implements self-service mechanisms where authority nodes automatically discover and validate each other through mutual authentication protocols. The directory system automatically updates node information, and monitor nodes autonomously oversee authentication processes. This self-service approach reduces operational complexity by eliminating manual configuration and management overhead, while maintaining robust multi-party security validation.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS10110585B2Multi-party authentication in a zero-trust distributed system
Publication Date: 2018.10.23 ENTEFY
  • US10110585B2 patent drawing
  • US10110585B2 patent drawing
  • US10110585B2 patent drawing

AI summary

A zero-trust network and methods of using same are disclosed. The network includes a plurality of nodes, some of which are user devices, such as mobile phones, some of which are computer servers. One or more of the nodes includes a directory system. When a server receives an access request by a user device or other node, the directory system is notified of the request. The directory system will contact a number of randomly selected nodes, and if any one of the nodes does not recognize the requesting device, the requesting device will be denied access. If every queried node is able to authenticate the requesting device, the directory system creates a session for the first device to access the server. The directory system can grant access by providing the server and device reciprocating keys. After the session ends, the accessed node is assigned a new identifier.