Environment Hash Validation for Network Access Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing network security systems face challenges in identifying and mitigating unauthorized changes to hardware, software, and data configurations, which can lead to potential threats both within a system and across the network, making it difficult to maintain compliance and security.

Innovation Solution

The implementation of a virtual environment system that verifies and validates configurations using cryptographic hashes before allowing access to a network, comparing hashes against authorized requirements to ensure only safe configurations are implemented and maintained, and isolating systems that fail to meet these requirements.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional network access control is used, then systems can access the network freely, but unauthorized configurations can spread threats across the network

Engineering Contradiction:
Improvenetwork securityVSAvoidsystem access
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system performs preliminary validation of configuration hashes before allowing network access. Configuration hashes are verified against authorized hashes in advance, and only systems with valid configurations are granted network access permissions, preventing potential threats before they can spread.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

Configuration hashes serve as an intermediary mechanism between the system and network access control. Instead of directly checking system configurations, the system uses hash representations as a mediator to verify system integrity, enabling efficient and secure access control decisions.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If configuration monitoring is implemented to identify unauthorized changes, then system security is improved, but the complexity of implementation and maintenance increases

Engineering Contradiction:
Improveconfiguration securityVSAvoidmonitoring system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

Instead of directly monitoring and analyzing actual system configurations, the system creates and validates hash representations (copies) of configurations. These hash copies serve as simplified proxies that capture essential configuration integrity information without requiring complex analysis of the full configuration data.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The system transforms complex configuration data into simplified hash parameters for validation. By changing the representation from detailed configuration data to condensed hash values, the system achieves efficient security verification with reduced computational complexity and easier maintenance.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If configuration validation is performed before system updates, then unauthorized configurations are prevented, but the time required for updates increases

Engineering Contradiction:
Improveconfiguration validityVSAvoidupdate time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system replaces complex mechanical or manual configuration analysis with cryptographic hash validation. Hash computation and comparison provide rapid verification of configuration integrity, substituting time-consuming manual or mechanical inspection processes with efficient computational operations.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS11973762B2System for prevention of unauthorized access using authorized environment hash outputs
Publication Date: 2024.04.30 BANK OF AMERICA CORP
  • US11973762B2 patent drawing
  • US11973762B2 patent drawing
  • US11973762B2 patent drawing

AI summary

When a system tries to access a network (e.g., another system, an application, data, or the like) at least two-factor authentication may be used to validate the system. At least one authentication factor may include utilizing authentication credentials of the entity or system accessing the network. At least a second authentication factor may include using an environment hash of the system, which is a representation of the configuration (e.g., hardware, software, or the like) on the system trying to access the network. The environment hash may be compared to hash requirements (e.g., authorized environment hashes, unauthorized environment hashes, or the like) to aid in the validation. The system may only access the network when both the authentication credentials and the environment hashes meet requirements.