Extended Validation Architecture for Multi-Node Resource Access Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing Validation Architecture systems are unable to detect and prevent attacks from ransomware, malware, and hacking tools that do not modify database contents, allowing unauthorized access and data exfiltration, especially in situations where resource access is not audited or logged.

Innovation Solution

An Extended Validation Architecture system that computes and compares indicia across multiple nodes to control access to resources before they are utilized, using a Resource Controller and Indicia Engine to ensure matching requests and responses, thereby preventing unauthorized access and data breaches.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional Validation Architecture systems are used to ensure database integrity, then data consistency and reliability are improved, but the systems cannot detect and prevent unauthorized access and data exfiltration by ransomware, malware, and hacking tools that do not modify database contents

Engineering Contradiction:
Improvedata integrityVSAvoidunauthorized access and data exfiltration
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The system performs preliminary validation of access requests before they are executed. By computing indicia of the request parameters (such as user identity, resource location, access type, and timestamp) and comparing them across multiple nodes, the system prevents unauthorized access and data exfiltration attempts before they can occur, rather than detecting them after database corruption has happened.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The invention introduces an intermediary validation layer between the user/request and the database/resource. This intermediary layer computes and compares indicia of access requests across multiple nodes, acting as a mediator that blocks harmful requests (such as those from ransomware, malware, or hacking tools) before they reach the database, while allowing legitimate requests to proceed.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If periodic database comparison methods are used to ensure data matching, then data consistency is improved, but the time delay between data divergence and detection increases significantly

Engineering Contradiction:
Improvedata consistencyVSAvoiddetection delay
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

Instead of performing periodic comparisons after data has diverged, the system performs preliminary validation of each access request in real-time. By computing indicia of the request parameters and comparing them across multiple nodes before the request is executed, the system eliminates detection delays and identifies data consistency issues immediately when they occur.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system transitions from periodic, batch-based database comparison to continuous, real-time validation of each access request. The indicia comparison occurs continuously as requests are made, ensuring that data consistency is maintained without interruption and that any divergence is detected immediately, eliminating the time loss associated with periodic checks.

Inventive Principle:
Principle #20Continuity of useful action

3Reliability

If Validation Architecture systems validate transactions in real-time, then data integrity is improved, but the system complexity and overhead of computing and comparing indicia increases

Engineering Contradiction:
Improvedata integrityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system extracts only the essential parameters needed for validation (such as user identity, resource location, access type, and timestamp) and computes indicia from these parameters. By focusing only on these critical elements rather than validating every detail of the entire transaction, the system reduces computational overhead and complexity while maintaining effective data integrity protection.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

Instead of creating full copies of databases for comparison, the system creates and compares only the indicia (hash values or summaries) of the request parameters. This copying approach allows for efficient real-time validation without the heavy computational burden of copying and comparing entire database structures, thereby reducing system complexity and overhead.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS12118116B1Method and system for controlling access to resources in a multi-node system
Publication Date: 2024.10.15 GRAVIC
  • US12118116B1 patent drawing
  • US12118116B1 patent drawing
  • US12118116B1 patent drawing

AI summary

Methods are disclosed for controlling access to a resource that is accessible to multiple nodes in a multi-node system or multiple processors in a multi-processor system. In operation, each node or processor receives a matching request to access the resource. Indicia of the request to access the resource is computed at each node or processor and is then compared between nodes or processors. Access to the resource is given to a node or processor when the computed indicia matches.