Binary Code Security Risk Assessment via Functional Context

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods fail to effectively assess and compare security risks in binary software code based on its functional context, leading to inadequate protection against malicious attacks and vulnerabilities.

Innovation Solution

A system that analyzes binary software code by determining its functional context, comparing security risk assessments with other codes performing similar functions, and generating notifications to indicate relative security levels, utilizing a software service platform with a security analyzer and database to store and retrieve risk assessments.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If binary software code is analyzed without considering functional context, then analysis simplicity is maintained, but security risk assessment accuracy deteriorates

Engineering Contradiction:
Improvesecurity risk assessment accuracyVSAvoidanalysis complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The system performs preliminary classification of binary software code into functional contexts before conducting security analysis. By pre-grouping code into categories such as network communication, file operations, and system control, the system prepares the analytical framework in advance, enabling more accurate security assessments without adding significant complexity to the actual analysis process.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The security analysis process is segmented into distinct phases: functional context determination, security vulnerability identification within each context, and comparative risk assessment. This segmentation allows the system to handle complex analysis tasks in manageable steps, improving accuracy while maintaining analytical tractability.

Inventive Principle:
Principle #1Segmentation

2Measurement precision

If security risk assessment is performed without functional context comparison, then analysis speed is maintained, but security risk evaluation accuracy deteriorates

Engineering Contradiction:
Improvesecurity risk evaluation accuracyVSAvoidanalysis time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system pre-establishes a database of security risk profiles for different functional contexts by analyzing representative code samples. When new binary code is analyzed, the system quickly matches it to pre-characterized functional contexts and retrieves relevant risk profiles, significantly reducing analysis time while maintaining high evaluation accuracy through contextual comparison.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system creates and maintains copies of security risk assessment data organized by functional context. By storing pre-analyzed security characteristics of similar code functions, the system can rapidly compare new code against these stored profiles without performing complete re-analysis, thereby reducing analysis time while preserving assessment accuracy.

Inventive Principle:
Principle #26Copying

3Reliability

If comprehensive security analysis is performed on all binary code, then security coverage is improved, but computational resource consumption increases

Engineering Contradiction:
Improvesecurity coverageVSAvoidcomputational resource consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The system applies different levels of analysis intensity to different functional contexts based on their inherent security risk profiles. High-risk contexts such as network communication and system control undergo comprehensive security analysis, while lower-risk contexts receive streamlined analysis. This localized quality approach ensures thorough security coverage for critical functions while reducing computational resource consumption overall.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system dynamically adjusts analysis parameters such as detection sensitivity, scanning depth, and validation thoroughness based on the identified functional context of the binary code. By changing these parameters according to context-specific risk levels, the system achieves comprehensive security coverage for high-risk areas while conserving computational resources on lower-risk code.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentEP3633531B1Determining security risks in binary software code
Publication Date: 2022.07.27 BLACKBERRY LTD
  • EP3633531B1 patent drawingFigure 1~2
  • EP3633531B1 patent drawingFigure 3

AI summary

Systems, methods, and software can be used to analyze security risks of a set of binary software code based on its functional context. In some aspects, a computer-implemented method comprises: receiving, by a server, a set of binary software code; determining, by the server, a functional context of the set of binary software code; determining, by the server, a security risk assessment of the set of binary software code; retrieving, by the server, a plurality of security risk assessment of other software codes having a same functional context as the functional context of the set of binary software code; comparing, by the server, the security risk assessment of the set of binary software code and the plurality of security risk assessments of other software codes having the same functional context; and generating, by the server, a security notification indicating a result of the comparing.