Software Trust Verification via Local Reputation Cache

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems lack a comprehensive method to provide timely and reliable reputation and trust information for software applications running in cross-platform environments, which can lead to insecure installations and executions, especially in offline situations.

Innovation Solution

A method that involves generating a unique identifier for software applications using digital certificates and hash values, which is checked against reputation and trust services for installation and rating information, allowing users to make informed decisions through notifications and updates in a local cache.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If digital certificates and hash values are used to generate unique identifiers for software applications, then the reliability of software identification and trust verification is improved, but the device complexity and processing requirements increase

Engineering Contradiction:
Improvesoftware identification reliabilityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system divides the software verification process into separate modular components: certificate validation, hash computation, identifier generation, and reputation checking. Each component operates independently and can be implemented as a separate service or module, reducing overall system complexity while maintaining high reliability through specialized processing.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A reputation service acts as an intermediary between the software application and the user. This intermediary collects, stores, and provides reputation information about software applications, eliminating the need for users to directly verify certificates and hashes while maintaining security through automated intermediary processing.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If a network-based reputation service is implemented to provide timely software trust information, then the reliability of trust information is improved, but the loss of time for offline operations increases

Engineering Contradiction:
Improvetrust information reliabilityVSAvoidoffline operation time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by pre-computing and storing reputation information in a local database before it is needed. When software is installed or updated, the system can immediately query locally stored reputation data without requiring real-time network connectivity, thus providing timely information even in offline conditions.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system creates a local copy of the reputation service functionality by storing reputation information in a local database. This copy allows the system to operate independently of the network, providing trust information locally while the full network-based service remains available when connectivity is restored.

Inventive Principle:
Principle #26Copying

3Ease of operation

If comprehensive reputation and trust information is collected and stored locally, then the ease of operation for users is improved, but the quantity of data stored and processing requirements increase

Engineering Contradiction:
Improveuser decision makingVSAvoiddata volume
Core Design Contradiction:
Ease of operationVSQuantity of substance

Solution Approach 1:

The system extracts only the essential reputation information needed for user decision-making from the comprehensive data collected by the reputation service. Instead of storing all raw data, the system stores condensed reputation summaries and key attributes, reducing data volume while maintaining ease of operation through the provided information.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system implements partial action by storing and processing only the most relevant reputation attributes (such as trust score, installation history, and user ratings) rather than all possible software metadata. This selective approach reduces data quantity while still providing sufficient information for users to make informed decisions.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS9135433B2Identifying reputation and trust information for software
Publication Date: 2015.09.15 ADOBE INC
  • US9135433B2 patent drawing
  • US9135433B2 patent drawing
  • US9135433B2 patent drawing

AI summary

Methods, systems, and computer program products identify trust and reputation information for an application. Status information including installation information and/or rating information corresponding to a software application is stored in a service or in a local computer cache. A software application is identified as corresponding to the status information, and the installation information and/or rating information is presented to a user prior to installation, launch, and/or update of the software application. Using the status information the user can make an informed decision on whether the user will trust the software application to permit the installation, launch, and/or update to occur.