Error Report Normalization via Canonical Metadata

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Software diversity introduces variations in error reports that hinder automated error reporting and correlation, making it difficult for developers to identify and fix defects across different implementations of software, as machine code addresses diverge, interfering with the utility of error report correlation.

Innovation Solution

The normalization of error reports using meta-data that encodes the effects of program transformations, allowing error reports to be transformed into a canonical form, effectively removing the interference of software diversity, enabling effective correlation and defect identification.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If software diversity is implemented to protect against exploits, then security against cyber attacks is improved, but error report correlation capability deteriorates

Engineering Contradiction:
Improvesecurity against exploitsVSAvoiderror report correlation capability
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The patent introduces an intermediary normalization process that translates diversified error reports into a canonical form. This mediator component receives error reports from diversified implementations, applies normalization transformations using stored metadata about the diversification, and produces standardized reports that can be correlated effectively, thus preserving both security and debugging utility

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent changes the parameters of error reports by applying transformations that reverse the effects of software diversification. By using metadata that encodes the relationship between diversified and canonical implementations, the system transforms error report parameters (such as code addresses and identifiers) from their diversified state back to a canonical state, enabling effective correlation while maintaining the security benefits of diversity

Inventive Principle:
Principle #35Parameter changes

2Reliability

If software diversity varies program implementation aspects, then protection against mass exploitation is improved, but automated error reporting utility deteriorates

Engineering Contradiction:
Improveprotection against mass exploitationVSAvoidautomated error reporting utility
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent performs preliminary action by pre-computing and storing metadata that describes the transformations applied during software diversification. This metadata is generated beforehand and stored for later use, enabling the normalization process to efficiently reverse the effects of diversification without requiring complex real-time analysis, thus maintaining automated error reporting utility

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The normalization function acts as an intermediary that bridges the gap between diversified implementations and error reporting tools. It receives error reports in their diversified form, applies transformations based on pre-stored metadata, and outputs normalized reports that automated error reporting systems can process effectively, preserving ease of operation while maintaining security

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10430265B2Error report normalization
Publication Date: 2019.10.01 RGT UNIV OF CALIFORNIA
  • US10430265B2 patent drawing
  • US10430265B2 patent drawing
  • US10430265B2 patent drawing

AI summary

Error report reporting errors that occur during software execution may be normalized to account for diversification of single software program. A method for useful providing error reports comprises receiving information regarding computer system status at a time of failure of proper execution of a diversified implementation of a computer program, the computer program having a plurality of diversified implementations; and transforming the information regarding the computer system status using metadata indicative of differences between the diversified implementation of the computer program and a canonical implementation of the computer program.