Cloud-Based Dynamic Code Signing for Executable Integrity

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing software security systems are inadequate in preventing unauthorized modifications to executables when the dynamic code signing certificate (CER) file leaks out, as they rely on secure build environments and lack robust authentication and authorization mechanisms, leading to potential unauthorized changes and execution of tampered applications.

Innovation Solution

A cloud-based dynamic code signing service that securely handles dynamic executable verification, restricting access to authorized personnel with proper credentials, and using cloud-based virtual machines or local activation to generate and verify dynamic code signatures, preventing unauthorized signing and tampering.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If dynamic code signing certificate (CER) file is stored locally in secure build environment, then dynamic executable verification can be performed, but security is compromised when CER file leaks out

Engineering Contradiction:
Improveexecutable verification reliabilityVSAvoidunauthorized signing capability
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent introduces a cloud-based intermediary service that acts as a mediator between the executable verification process and the code signing certificate. Instead of storing the CER file locally, the system uploads it to a secure cloud service that performs the actual signing operations. This intermediary approach prevents direct access to the CER file while maintaining verification reliability, as the cloud service handles all signing requests securely without exposing the certificate to local environments where it could leak.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If CER file is made accessible for dynamic signing, then executable verification works, but unauthorized personnel can perform signing operations

Engineering Contradiction:
Improvedynamic signing accessibilityVSAvoidsigning authorization security
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent implements a feedback mechanism through authenticated access control where the cloud-based service verifies credentials before allowing any signing operations. The system provides feedback by accepting only authenticated requests from authorized personnel and rejecting unauthorized access attempts. This ensures that while the signing capability remains accessible for legitimate operations, unauthorized personnel cannot perform signing operations even if they attempt to access the system.

Inventive Principle:
Principle #23Feedback

3Reliability

If cloud-based service is used for dynamic code signing, then security against CER leakage is improved, but system complexity increases

Engineering Contradiction:
ImproveCER file securityVSAvoidsystem architecture complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements self-service capabilities where the cloud-based dynamic code signing service automatically handles certificate management, authentication verification, and signing operations without requiring complex local infrastructure. The service autonomously manages the CER file security, performs cryptographic operations, and enforces access controls, thereby improving security while minimizing the complexity burden on the client system. The automated nature of these services reduces manual configuration and maintenance overhead despite the distributed architecture.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS20210334358A1Cloud-based dynamic executable verification
Publication Date: 2021.10.28 ARRIS ENTERPRISES LLC
  • US20210334358A1 patent drawing
  • US20210334358A1 patent drawing
  • US20210334358A1 patent drawing

AI summary

A method and system provide the ability to dynamically verify an executable. Encrypted build data and developer permissions are received from a first developer into a build registration tool within a secure cloud computing environment. The encrypted build data includes a build identification (ID), a dynamic code signing certificate (CER), and developer credentials. The build registration tool authenticates the developer credentials based on developer permissions. A dynamic code signing tool (within the secure cloud computing environment) decrypts the encrypted build data and activates the executable by dynamically signing the executable to obtain a dynamic code signature (SEC). The SEC is delivered for runtime deployment.