Automated Code Signing with File Security Credential Evaluation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current code signing processes face challenges in managing high-volume signing requests, detecting erroneous requests, and preventing misuse of high-value keys, leading to potential misuse or accidental shipment of low-quality files to clients.

Innovation Solution

An automated management system for code signing based on file security credentials, which evaluates signing requests using file security values and criteria to determine if a file should be signed with a specific key, ensuring only trustworthy files are signed and suggesting alternative keys if necessary.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If automated signing systems process high-volume signing requests, then productivity increases, but the risk of erroneous requests and key misuse increases

Engineering Contradiction:
Improvesigning request processing volumeVSAvoidsigning request accuracy
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system performs preliminary evaluation of signing requests by calculating file security values and comparing them against key criteria before actual signing occurs. This advance verification prevents erroneous signing requests from consuming cryptographic keys, thereby maintaining both high processing volume and high reliability.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms by providing detailed evaluation results and rejection reasons back to the signing request initiators. This feedback loop enables continuous improvement of file quality and security credentials, reducing erroneous requests over time while maintaining automated high-volume processing.

Inventive Principle:
Principle #23Feedback

2Reliability

If high-value cryptographic keys are used for signing, then file security and trustworthiness improve, but the risk of key misuse for low-quality files increases

Engineering Contradiction:
Improvefile trustworthinessVSAvoidkey misuse risk
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The system calculates file security values and performs preliminary assessments against key criteria before allowing high-value keys to be used. This ensures that only files meeting quality thresholds can consume high-value cryptographic keys, preventing key misuse while maintaining file trustworthiness.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system dynamically evaluates file parameters (security credentials, quality metrics) and matches them against key parameters (key value, security requirements). This parameter-based matching ensures that high-value keys are only applied to files with corresponding high security parameters, preventing mismatched key usage.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If manual review processes are implemented for signing requests, then signing accuracy improves, but processing time and operational complexity increase

Engineering Contradiction:
Improvesigning request verification accuracyVSAvoidsigning request processing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs self-service verification by automatically calculating file security values, comparing them against stored key criteria, and making signing decisions without human intervention. This automated self-evaluation maintains high verification accuracy while eliminating manual review time delays.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system replaces manual mechanical review processes with automated computational evaluation. The processor automatically retrieves file security credentials, calculates security values, and compares them against key criteria, substituting human manual review with efficient automated computational mechanisms.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS12039088B2Signing files based on file security credentials
Publication Date: 2024.07.16 HEWLETT PACKARD ENTERPRISE DEV LP
  • US12039088B2 patent drawing
  • US12039088B2 patent drawing
  • US12039088B2 patent drawing

AI summary

Examples described herein relate to signing of files based on file security credentials. A signing request for a file is received from a file author device. The signing request may include a file identifier associated with the file and a first key identifier associated with a first key stored in a hardware security module (HSM). File security credentials associated with the file may be obtained from one or more file security databases using the file identifier. A file security value for the file may be determined based on the file security credentials. On determining that the file security value satisfies a predetermined first key criteria, the file may be signed using the first key.