Trusted Execution Bit for Secure Binary Installation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Computer systems are vulnerable to unauthorized access and attacks, such as buffer overflow attacks, due to the lack of secure mechanisms for executing binaries, which can lead to compromised security and unauthorized program installations or modifications.

Innovation Solution

A method and system for trusted execution of applications on a computing system, where executable files are installed through an approved mechanism, with a kernel modifying a trusted execution bit for each file, and files are executed only if they have a valid trusted execution bit, preventing untrusted or modified files from being executed.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If traditional file execution mechanisms are used, then system flexibility and ease of operation are improved, but system security and reliability deteriorate due to vulnerability to unauthorized access and buffer overflow attacks

Engineering Contradiction:
Improvefile execution flexibilityVSAvoidsystem security
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The kernel sets a trusted execution bit for each executable file during the installation process via an approved mechanism. This preliminary action ensures that before any executable is run, it has already been marked with a trust indicator, preventing unauthorized or malicious executables from executing while maintaining system flexibility.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The trusted execution bit acts as an intermediary mechanism between the file installation process and the file execution process. The kernel checks this bit before allowing execution, serving as a mediator that verifies trustworthiness without restricting legitimate execution or ease of operation.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If executable files can be freely installed and executed, then system adaptability is improved, but system integrity deteriorates due to unauthorized program installations and modifications

Engineering Contradiction:
Improveprogram installation flexibilityVSAvoidsystem integrity
Core Design Contradiction:
Adaptability or versatilityVSStability of the object's composition

Solution Approach 1:

The system performs preliminary action by setting the trusted execution bit during the approved installation process. This ensures that only through the approved mechanism can executables be installed with the trust indicator, maintaining system integrity while allowing adaptability through legitimate installation channels.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The kernel continuously monitors the trusted execution bit status before allowing execution. This feedback mechanism ensures that only files with valid trust indicators can execute, preventing unauthorized installations from compromising system integrity while maintaining adaptability for approved programs.

Inventive Principle:
Principle #23Feedback

3Device complexity

If no execution verification is performed, then system complexity is reduced and ease of operation is improved, but security vulnerabilities increase allowing buffer overflow attacks and unauthorized access

Engineering Contradiction:
Improveexecution control mechanismVSAvoidsecurity vulnerability
Core Design Contradiction:
Device complexityVSObject-affected harmful factors

Solution Approach 1:

The trusted execution bit is set in advance during installation, so the verification process during execution is simple and does not add significant complexity. This preliminary action allows the system to maintain low operational complexity while effectively preventing security vulnerabilities.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The trusted execution bit serves as a simple intermediary check that the kernel performs before execution. This single-bit verification mechanism adds minimal complexity to the execution control while effectively preventing buffer overflow attacks and unauthorized access by blocking untrusted executables.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS9311475B2Trusted execution of binaries and modules
Publication Date: 2016.04.12 VMWARE INC
  • US9311475B2 patent drawing
  • US9311475B2 patent drawing
  • US9311475B2 patent drawing

AI summary

A computer system mechanism is provided that restricts execution of binaries, such as applications, kernel modules, shared libraries, on the computing system to only those that have been installed by an approved mechanism. The approved mechanism acts as a single entry point on the computing for installing new binaries. Any change in file content or metadata taints an executable file and prevents execution by the kernel. Files copied over and not installed via, the approved mechanism will not be executed.