Cross-Platform Trust Verification for Software Integrity

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current cybersecurity systems face challenges in verifying the integrity of plug-ins across multiple operating system platforms, leading to inefficiencies and delays in updating cybersecurity agents to combat evolving threats.

Innovation Solution

A cross-platform trust verification system that conducts dual-stage verification using package verification logic, catalog verification logic, and component verification logic to confirm the integrity of software components, ensuring platform-agnostic hash value usage across different OS platforms.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If monolithic executables are used with hash verification, then software legitimacy can be verified, but updates require significant delays and cannot keep pace with evolving threats

Engineering Contradiction:
Improvesoftware legitimacy verificationVSAvoidupdate delay
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent divides the monolithic executable into a core application and separate plug-in components. Each plug-in can be independently verified and updated, allowing rapid deployment of security updates without requiring full application re-verification. The verification system segments the hash verification process to handle only the updated plug-in portion rather than the entire application.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements pre-verification of plug-ins before installation. The verification logic checks plug-in legitimacy in advance through hash verification against a catalog of expected values, preventing malicious plug-ins from being installed. This preliminary verification enables rapid updates by ensuring security checks are completed before deployment rather than requiring post-installation verification.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If each operating system platform uses its own distinct mechanism to confirm plug-in integrity, then platform-specific requirements are met, but cross-platform efficiency and consistency are lost

Engineering Contradiction:
Improveplatform-specific verificationVSAvoidcross-platform development efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent creates a universal verification system where a single verification logic component handles multiple operating system platforms. The system uses a platform-agnostic hash verification approach that works across Windows, Linux, and macOS without requiring separate verification mechanisms for each platform. This universal approach maintains adaptability to different platforms while dramatically improving cross-platform development efficiency.

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

Solution Approach 2:

The patent uses a catalog that contains pre-computed hash values (representations) of legitimate plug-ins. The verification logic copies this catalog across platforms and uses it to verify plug-in integrity. Instead of implementing different verification mechanisms for each platform, the system copies the same verification logic and catalog data structure across all platforms, ensuring consistency and reducing development complexity.

Inventive Principle:
Principle #26Copying

3Adaptability or versatility

If applications and plug-ins are updated on different schedules, then flexibility is maintained, but verifying plug-in integrity becomes challenging across platforms

Engineering Contradiction:
Improveupdate schedule flexibilityVSAvoidintegrity verification complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a dynamic verification system where the verification logic automatically adapts to different update schedules. When a plug-in is updated, the system dynamically retrieves the corresponding hash value from the catalog and performs verification. This dynamic approach allows applications and plug-ins to be updated independently on different schedules while maintaining simplified integrity verification through automated hash comparison.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS11392700B1System and method for supporting cross-platform data verification
Publication Date: 2022.07.19 MAGENTA SECURITY HOLDINGS LLC
  • US11392700B1 patent drawing
  • US11392700B1 patent drawing
  • US11392700B1 patent drawing

AI summary

A trust verification system for automatically verify an integrity of an object across multiple operating system (OS) platforms. The trust verification system features package verification logic, catalog verification logic, and component verification logic. The package verification logic recovers, from an incoming package, (i) an object, (ii) a catalog including identifiers associated with software component(s) forming the object and representation(s) associated with each of the software component(s), and (iii) a representation of the catalog. The catalog verification logic is configured to verify an integrity of the catalog while the component verification logic is configured to verify an integrity of software component(s) associated with the object. Thereafter, the package verification logic verifies an integrity of the object associated with the incoming package in response to the catalog verification logic verifying the integrity of the catalog and the component verification logic verifying the integrity of the software component(s).