Encrypted Credential File Integrity Verification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In computer systems, managing credentials for executing instructions is cumbersome, especially when password rotation is required, as existing methods either necessitate recompiling applications or expose passwords in plain text, posing security risks.

Innovation Solution

An encrypted file is decrypted to obtain a hash value for a credentials setting component, with a test hash verifying the integrity before decrypting credentials, which are then passed to set credentials securely without exposing them in plain text, allowing for dynamic password changes without recompilation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If credentials are written into an application, then credentials can be securely stored, but the application must be recompiled every time credentials change

Engineering Contradiction:
Improvecredential securityVSAvoidcredential update efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent extracts credentials from the application binary and stores them separately in an encrypted file. The application no longer contains hardcoded credentials, instead it references the external credential file at runtime. This allows credential updates without application recompilation while maintaining security through encryption.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces an intermediary encrypted credential file that mediates between the application and the actual credentials. The application interacts with the encrypted file through a standardized interface, allowing credential changes without modifying the application code or requiring recompilation.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If credentials are written into a script, then credentials can be updated without recompilation, but credentials are exposed in plain text

Engineering Contradiction:
Improvecredential update efficiencyVSAvoidsecurity risk
Core Design Contradiction:
ProductivityVSObject-affected harmful factors

Solution Approach 1:

The patent takes the flexibility of script-based credential storage (easy updates) and combines it with encryption to eliminate the security vulnerability. The encrypted credential file provides both update efficiency and security, converting the harmful plain-text exposure into a secure encrypted format that can be dynamically updated.

Inventive Principle:
Principle #22Blessing in disguise (Convert harm into benefit)

Solution Approach 2:

The patent changes the state of credentials from plain text to encrypted form. The credential storage mechanism transitions from unencrypted script variables to encrypted file format, maintaining the ability to update credentials dynamically while transforming the security characteristics to eliminate plain-text exposure.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If passwords are changed periodically, then security is improved, but the time required for credential management increases

Engineering Contradiction:
ImprovesecurityVSAvoidcredential management time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements automated credential management where the system automatically handles encryption, decryption, and validation of credentials. The application automatically retrieves updated credentials from the encrypted file without manual intervention, enabling periodic password changes to be handled automatically by the system rather than requiring manual management time.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS8667569B2Credentials management
Publication Date: 2014.03.04 TARGET BRANDS INC
  • US8667569B2 patent drawing
  • US8667569B2 patent drawing
  • US8667569B2 patent drawing

AI summary

An encrypted file is decrypted to gain access to a stored hash value for a credentials setting component. A test hash value of the credentials setting component is formed. Before decrypting a set of encrypted credentials to form decrypted credentials, it is required that the test hash value of the credentials setting component match the stored hash value of the credentials setting component. The decrypted credentials are then passed to the credentials setting component to set credentials that instructions are to be executed under.