Application Integrity Verification via Associated File Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing technologies fail to effectively prevent abnormal operations due to files associated with applications, which can impact the integrity and proper functioning of applications and their cooperative services.

Innovation Solution

A device with processing circuitry and storage that stores associated file and application information, determining the integrity of files and affected applications, and controlling the operation of target applications when file integrity is compromised, thereby preventing abnormal operations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If integrity verification is performed only on application binaries, then verification scope is limited and simple, but abnormal operations due to associated files cannot be prevented

Engineering Contradiction:
Improveprevention of abnormal operationsVSAvoidintegrity verification scope
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The integrity verification scope is segmented into multiple categories: application binaries, associated files (libraries, configuration files, data files), and cooperative applications. Each category is verified independently with appropriate hash algorithms, allowing comprehensive verification without overwhelming complexity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary integrity verification of all associated files and cooperative applications before the target application is allowed to execute. This advance verification ensures that all dependencies are intact before operation, preventing abnormal operations due to file corruption or tampering.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If integrity verification includes all associated files and cooperative applications, then abnormal operations can be prevented, but verification time and system complexity increase

Engineering Contradiction:
Improveapplication operation integrityVSAvoidintegrity verification time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary integrity verification of all associated files and cooperative applications before the target application is allowed to execute. This advance verification ensures that all dependencies are intact before operation, preventing abnormal operations due to file corruption or tampering.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system dynamically adjusts verification parameters such as hash algorithm selection (MD5, SHA-1, SHA-256) and verification depth based on file types and risk levels. This allows faster verification for low-risk files while maintaining thorough verification for critical components, optimizing overall verification time.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If the system verifies integrity of cooperative applications, then service reliability is improved, but the complexity of managing verification across multiple applications increases

Engineering Contradiction:
Improvecooperative service integrityVSAvoidmulti-application verification management
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The integrity verification system is designed as a universal multi-functional platform that can verify various types of objects (binaries, libraries, configuration files, data files) and manage multiple cooperative applications through a unified interface. This universal approach simplifies management by providing consistent verification mechanisms across different application types and dependencies.

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

Solution Approach 2:

The system implements feedback mechanisms where verification results of cooperative applications are fed back to the target application's verification process. If a cooperative application fails integrity verification, this information is fed back to prevent the target application from executing, ensuring service integrity without requiring complex manual management.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS11977472B2Application operation control device, application operation control method, and application operation control program
Publication Date: 2024.05.07 NIPPON TELEGRAPH & TELEPHONE CORP
  • US11977472B2 patent drawing
  • US11977472B2 patent drawing
  • US11977472B2 patent drawing

AI summary

An application operation control device includes processing circuitry configured to store associated file information that indicates, in association with each other, an application and an associated file that is a file whose integrity is to be verified when integrity of the application is determined, and associated application information that indicates, in association with each other, the application and an associated application that is an application that is potentially affected when the integrity of the application is damaged, determine integrity of the associated file of the application, and in a case where, among a plurality of the associated files of the application, integrity of any of the plurality of the associated files is determined to be damaged, extract, as a target application for operation control, an application associated with an associated file the integrity of which is determined to be damaged from the associated file information.