Software Verification Management Service for Cloud Application Trust

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing network-based computing applications face challenges in verifying the trustworthiness of remotely-executed applications, as existing security protocols are insufficient to ensure that applications are not misused after data reaches its destination, leading to concerns about data misuse and privacy breaches.

Innovation Solution

A software verification management service (SVMS) is implemented to manage the build, deployment, and execution of applications, using a cryptographically verifiable and auditable build process, generating immutable audit records, and providing runtime encryption keys to ensure the trustworthiness of the software stack, allowing end-users to verify the legitimacy of the application through security artifacts.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If cryptographic verification and auditing mechanisms are implemented to verify application trustworthiness, then data security and reliability are improved, but system complexity and computational overhead increase

Engineering Contradiction:
Improveapplication trustworthinessVSAvoidverification system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements preliminary cryptographic verification by generating digital signatures during the application build process and creating verification artifacts before deployment. This allows trust verification to be performed in advance rather than requiring complex real-time verification mechanisms, thus improving reliability while managing system complexity.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces a software verification management service as an intermediary that handles cryptographic verification operations. This mediator manages the complexity of trust verification by centralizing cryptographic operations, generating verification artifacts, and providing standardized interfaces, thereby improving application trustworthiness without proportionally increasing overall system complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Loss of information

If comprehensive audit records and verification artifacts are generated, then transparency and trust verification are improved, but data processing time and resource consumption increase

Engineering Contradiction:
Improveverification information completenessVSAvoidverification processing time
Core Design Contradiction:
Loss of informationVSLoss of time

Solution Approach 1:

The patent extracts essential verification information into separate verification artifacts and audit records that are generated during the build process. By separating verification data from the main application execution flow, the system achieves comprehensive verification information without significantly impacting application runtime performance, as the artifacts are prepared in advance.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent performs comprehensive auditing and generates verification artifacts during the build and deployment phases before the application runs. This preliminary action ensures complete verification information is available without adding processing overhead during actual application execution, thus maintaining both information completeness and time efficiency.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If encryption keys are provided at runtime for verification, then security assurance is improved, but computational overhead and resource usage increase

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

Solution Approach 1:

The patent implements selective cryptographic verification by providing encryption keys and verification artifacts only when needed for specific verification operations. Rather than continuously performing full cryptographic verification, the system uses verification artifacts prepared in advance and only performs necessary cryptographic checks, thus maintaining security assurance while reducing computational overhead and resource consumption.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS11494493B1Software verification for network-accessible applications
Publication Date: 2022.11.08 AMAZON TECH INC
  • US11494493B1 patent drawing
  • US11494493B1 patent drawing
  • US11494493B1 patent drawing

AI summary

An executable version of an application is deployed at a dynamically provisioned execution resource. An encryption key, based at least partly on an analysis of the execution resource, is transmitted to the execution resource after the application is instantiated. In response to a software verification request, which includes a security artifact, a verification response indicating that the software used for the application at the execution resource meets a trust criterion is provided. The security artifact is generated using the encryption key, and the verification response is based on analysis of the security artifact.