Virtual Computer Authentication via Hash Verification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing authentication methods for accessing an organization's computer network using only user credentials such as usernames and passwords are inadequate, as they do not provide sufficient security against unauthorized access and do not verify the integrity of the computing device and virtual computer application, making them vulnerable to hacking and malicious code insertion.

Innovation Solution

A method that generates a hash value based on user credentials, a security code from a security token, and the program code of the virtual computer application, which is then authenticated by the network, followed by multi-factor authentication using a passcode sent via a different communication channel, ensuring the integrity of both the user and the application.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If only user credentials (username and password) are used for authentication, then the authentication process is simple and easy to operate, but the security level is insufficient and vulnerable to hacking and phishing attacks

Engineering Contradiction:
Improveauthentication process simplicityVSAvoidsecurity level
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The authentication process is divided into multiple independent verification stages: initial credential validation, device integrity checking via hash verification, and multi-factor authentication with passcode confirmation. Each stage operates independently to provide layered security without complicating the user experience.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary device integrity verification by computing and validating hash values of the virtual computer application code before allowing authentication to proceed. This preliminary check ensures the application hasn't been compromised with malicious code, preventing security breaches before they can occur.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If multi-factor authentication with device and application verification is implemented, then the security level increases significantly, but the authentication process complexity increases

Engineering Contradiction:
Improvesecurity levelVSAvoidauthentication process complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system automatically performs device integrity verification by computing hash values of the virtual computer application code and comparing them against expected values. The authentication process self-manages these complex verification steps without requiring user intervention, reducing perceived complexity while maintaining high security.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system provides continuous feedback during the authentication process, validating each component (credentials, device state, application integrity) and progressing only when verification succeeds. This structured feedback mechanism guides the authentication flow clearly, managing complexity through systematic verification steps.

Inventive Principle:
Principle #23Feedback

3Productivity

If user credentials are transmitted and validated without additional verification, then the authentication process is fast and efficient, but the system is vulnerable to credential theft and unauthorized access

Engineering Contradiction:
Improveauthentication speedVSAvoidvulnerability to credential theft
Core Design Contradiction:
ProductivityVSObject-affected harmful factors

Solution Approach 1:

The system performs preliminary device integrity verification by computing and validating hash values of the virtual computer application code before allowing credential validation to proceed. This preliminary check ensures the application environment is trustworthy, preventing credential theft even if credentials are transmitted efficiently.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system introduces an intermediary verification layer that validates device state and application integrity between credential submission and authentication completion. This intermediary check acts as a security gate, ensuring credentials are only accepted from verified, uncompromised devices without significantly impacting authentication speed.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Ease of operation

If the virtual computer application is not verified for integrity, then the authentication process is simpler and faster, but malicious code insertion and device compromise become possible

Engineering Contradiction:
Improveauthentication simplicityVSAvoidmalicious code insertion risk
Core Design Contradiction:
Ease of operationVSObject-generated harmful factors

Solution Approach 1:

The system performs preliminary verification of the virtual computer application by computing hash values of the application code and comparing them against expected values stored on the server. This preliminary integrity check occurs before authentication is granted, preventing malicious code execution while maintaining a streamlined authentication process for verified applications.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The virtual computer application self-verifies its own integrity by providing its code for hash computation and validation. The application autonomously participates in its own security verification, eliminating the need for complex external inspection mechanisms while ensuring protection against code tampering and malicious insertion.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS12063210B1Secure authentication for a virtual computer
Publication Date: 2024.08.13 WELLS FARGO BANK NA
  • US12063210B1 patent drawing
  • US12063210B1 patent drawing
  • US12063210B1 patent drawing

AI summary

A computing device may generate a hash value based at least in part on user credentials for accessing an internal network, a security code generated by a security token, and at least a portion of program code of a virtual computing application for accessing the internal network. The computing device may send, using a first communications channel, an indication of the hash value to a computing system associated with the internal network. The computing device may, in response to sending the hash value, receive, via a second communications channel, a first indication of a passcode from the computing system. The computing device may, in response to receiving the passcode, send a second indication of the passcode to the computing system.