Distributed Ledger Configuration Locking via Cryptographic Hashing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing cybersecurity systems and architectures face challenges such as lack of integrated incident response capabilities, complex procurement processes for incident response services, and inability to dynamically adapt to changes in the security landscape.

Innovation Solution

A customized cybersecurity framework that employs modeling to distribute verified intelligence, utilizing a distributed ledger to record and manage security configurations, and providing a recovery key for encrypted configurations, while also regenerating the recovery key upon detection of potential compromises or at predefined intervals.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If configuration data is stored in plaintext for easy access and recovery, then ease of operation is improved, but security is worsened due to potential compromise and unauthorized access

Engineering Contradiction:
ImproveConfiguration recoveryVSAvoidSecurity
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent creates cryptographic copies (hashes) of configuration data that can be stored and verified without exposing the original sensitive information. The hash function generates a fixed-size representation that can be stored efficiently while the original data remains protected, allowing verification of integrity without plaintext exposure.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent introduces cryptographic intermediaries including hash functions, encryption algorithms, and trusted execution environments that mediate between the need for configuration access and the need for security. These intermediaries enable secure storage and controlled access without requiring plaintext configuration data to be exposed.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If cryptographic hashing is applied to configuration data for security, then security is improved, but data recovery capability is worsened due to one-way function limitations

Engineering Contradiction:
ImproveSecurityVSAvoidConfiguration recovery
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent segments configuration data into multiple encrypted portions or uses hierarchical encryption schemes where different keys or credentials are required for different levels of access. This segmentation allows for controlled recovery scenarios where authorized entities can retrieve specific portions without needing the complete plaintext, balancing security with recovery capability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements preliminary cryptographic preparations such as pre-computed hashes, encrypted backups, and recovery key management systems that are set up in advance. These preliminary actions enable secure recovery processes without requiring plaintext storage, as the cryptographic infrastructure is already in place to facilitate authorized retrieval.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If frequent recovery key regeneration is performed to detect compromises, then security is improved, but loss of time is worsened due to additional processing overhead

Engineering Contradiction:
ImproveCompromise detectionVSAvoidKey regeneration time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements periodic key regeneration at scheduled intervals rather than continuously, combined with event-triggered regeneration when compromise indicators are detected. This periodic approach balances security monitoring with operational efficiency, ensuring timely detection without constant overhead.

Inventive Principle:
Principle #19Periodic action

Solution Approach 2:

The patent employs feedback mechanisms that monitor system state and security indicators to dynamically adjust key regeneration frequency. When the system detects anomalies or compromise indicators, feedback triggers immediate key regeneration; otherwise, regeneration occurs at optimized intervals, reducing unnecessary processing overhead while maintaining security.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS20250202694A1Systems and methods for configuration locking
Publication Date: 2025.06.19 AS0001 INC
  • US20250202694A1 patent drawing
  • US20250202694A1 patent drawing
  • US20250202694A1 patent drawing

AI summary

Systems, methods, and computer-readable media are disclosed. One system includes one or more processing circuits configured to determine at least one action performed on one or more computing systems of at least one entity based on identifying one or more endpoints or interfaces of the one or more computing systems. The one or more processing circuits can identify one or more configuration levels corresponding to the at least one action performed on the one or more computing systems. The one or more processing circuits can encrypt or tokenize the one or more configuration levels for storage on a distributed ledger or data source.