Cryptographic Assertion Tracing for Software Reliability Verification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods struggle to verify the reliability of software in devices without access to the device's code, particularly in agile development environments where software is frequently updated, leading to potential issues with device interactions and unreliable core software.
Innovation Solution
A cryptographic assertion tracer (CAT) and encrypted reproducible record (ERR) system is implemented to track and verify that reliability requirements are met in device instructions, ensuring that assertions are cryptographically linked to specific software states and updates, with automatic detection of modifications and generation of verification records.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If software development follows agile processes with frequent updates, then productivity and adaptability improve, but software reliability deteriorates due to consistent changes and dependencies
Solution Approach 1:
The system performs preliminary actions by generating cryptographic assertions and verification records before software updates are deployed. This allows reliability verification to be prepared in advance, ensuring that even with frequent agile updates, each change can be verified against its reliability requirements before affecting production systems.
Solution Approach 2:
The system implements continuous feedback mechanisms where software updates are automatically verified against reliability requirements, and verification results are fed back to developers. This closed-loop approach maintains reliability despite frequent changes by providing immediate detection and correction of reliability issues.
2Measurement precision
If developers have access to device code and internal auditing materials, then reliability verification improves, but device security and intellectual property protection worsen
Solution Approach 1:
The system introduces cryptographic assertions and verification records as intermediaries between the device code and auditors. These cryptographic artifacts enable reliable verification of software reliability without requiring direct access to the actual device code, thus maintaining security while achieving verification goals.
Solution Approach 2:
Instead of requiring access to original device code, the system uses cryptographic copies and representations (assertions and verification records) that contain sufficient information for reliability verification. This copying approach allows verification without exposing sensitive code or internal materials.
3Reliability
If comprehensive reliability tracking is implemented across all software instructions, then reliability assurance improves, but system complexity and implementation difficulty worsen
Solution Approach 1:
The system enables self-service reliability tracking where the verification process automatically generates and manages cryptographic assertions and verification records without requiring complex manual intervention. This automation reduces implementation complexity while maintaining comprehensive reliability tracking across software instructions.
Data Source
AI summary
Computer systems, devices, and associated methods of verifying reliability of instructions for a device are disclosed herein. In one embodiment, a method includes identifying a reliability requirement associated with instructions for a device and receiving, from a user, an assertion in relation to the reliability requirement. The method includes generating a cryptographic assertion tracer (CAT) based at least in part on the received assertion. The method includes receiving assertion-related instructions in association with the CAT and generating a first code verification encrypted reproducible record based at least in part on the CAT and the received assertion-related instructions. The method then includes reporting that the reliability requirement is addressed.