Binary Comparison for Detecting Unintended Software Functionality

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current software analysis methods, such as Software Composition Analysis (SCA) and Vulnerability Exploitability Exchange (VEX), fail to provide comprehensive cyber risk assessment by relying on vulnerability databases, leading to false positives and an inability to detect unintended software functionality changes, as exemplified by the SolarWinds attack.

Innovation Solution

A method for comparative analysis that examines behavioral and functional changes between software versions, using machine learning and artificial intelligence to identify unintended software functionality by comparing features and behaviors across different versions, without requiring source code execution.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If Software Composition_analysis (SCA) and Vulnerability Exploitability exchange (VEX) are used to provide vulnerability information, then vulnerability assessment capability is improved, but the ability to determine live impact and detect unintended functionality deteriorates

Engineering Contradiction:
Improvevulnerability assessment capabilityVSAvoidbehavioral context information
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The patent segments the software analysis into multiple independent components: SBOM generation, VEX data collection, behavioral feature extraction, and risk assessment. This segmentation allows each component to specialize in specific aspects, with behavioral analysis separately examining function calls, system interactions, and execution patterns to detect unintended functionality without compromising the vulnerability assessment pipeline.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent adds a temporal dimension by analyzing behavioral changes between software versions. Instead of static vulnerability listing, the system compares behavioral features across versions to identify new unintended functions. It also adds a functional dimension by extracting and analyzing specific behavior patterns (function calls, system interactions) to determine live impact, transforming the assessment from component-level to behavior-level analysis.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Reliability

If conventional vulnerability scanning techniques are used, then vulnerability detection is improved, but false positives increase and cyber analyst time is wasted

Engineering Contradiction:
Improvevulnerability detectionVSAvoidcyber analyst time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements feedback mechanisms where behavioral analysis results feed back into the risk assessment process. The system continuously monitors behavioral features, compares them against baseline expectations, and adjusts vulnerability assessments accordingly. This feedback loop reduces false positives by validating vulnerability claims against actual observed behavior, allowing cyber analysts to focus only on confirmed high-risk issues.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent creates virtual copies of software behavior through dynamic instrumentation and sandboxing. Instead of directly analyzing potentially malicious code execution, the system copies and monitors behavior patterns in isolated environments. This copying approach enables comprehensive behavioral analysis without exposing analysts to actual malware, reducing both false positives and time required for manual verification.

Inventive Principle:
Principle #26Copying

3Loss of information

If SBOM techniques are used to provide component lists, then software composition understanding is improved, but the ability to assess live impact and detect malicious functionality deteriorates

Engineering Contradiction:
Improvecomponent informationVSAvoidmalicious functionality detection
Core Design Contradiction:
Loss of informationVSReliability

Solution Approach 1:

The patent merges SBOM component listing with behavioral feature extraction and risk assessment into a unified analysis platform. The system combines static component information from SBOMs with dynamic behavioral data, function call graphs, and execution patterns to create a comprehensive view of software risk. This merging allows the system to detect malicious functionality by analyzing how components actually behave rather than relying solely on declared compositions.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent changes the analysis parameters from static component identifiers to dynamic behavioral metrics. Instead of assessing risk based solely on component lists and vulnerability databases, the system monitors parameters such as function call frequencies, system resource consumption, network interactions, and execution timing patterns. These parameter changes enable the detection of malicious functionality that may not be captured in traditional SBOM data.

Inventive Principle:
Principle #35Parameter changes

4Measurement precision

If manual analysis methods are used, then detection accuracy is improved, but cost and complexity increase prohibitively

Engineering Contradiction:
Improvedetection accuracyVSAvoidanalysis system complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent implements self-service automation where the system performs its own analysis without requiring manual intervention. Automated behavioral feature extraction, machine learning-based risk assessment, and comparative analysis across versions are all performed automatically. The system self-calibrates using baseline data from known-good software versions and continuously improves its detection accuracy through automated learning, eliminating the need for manual analysis while maintaining high precision.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent replaces manual mechanical analysis with automated computational systems. Instead of human analysts manually reviewing code and behavior, the system uses automated tools for dynamic instrumentation, sandboxing, machine learning classification, and statistical analysis. This substitution maintains detection accuracy while dramatically reducing complexity from the perspective of the analyst, as the automated system handles all analytical tasks.

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

Data Source

PatentUS12625972B2Comparative analysis of binaries for software supply chain security
Publication Date: 2026.05.12 KARAMBITAI INC
  • US12625972B2 patent drawing
  • US12625972B2 patent drawing
  • US12625972B2 patent drawing

AI summary

Comparing how behaviors, functions, and other features have changed between different software versions, embodiments determine how the software has changed between versions and make an assessment as to whether or not the newer version of the software has unintended functionality.