Remote Command Authentication via Pre-signed Templates

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for remotely authenticating commands on computer systems require significant interaction and preconfiguration, and lack effective protection against unauthorized access.

Innovation Solution

A system that authenticates commands using a private key to produce an authenticated command, which is then verified by a target system using a public key, minimizing interaction and preventing unauthorized access through challenge messages and responses.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If traditional remote command issuance methods are used, then system administrators can issue commands to target systems, but significant interaction and preconfiguration are required

Engineering Contradiction:
Improvecommand issuance processVSAvoidpreconfiguration requirements
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The authentication system pre-generates and stores signed command templates in a database before they are needed. When a command needs to be issued, the system retrieves and fills in the template parameters rather than creating and signing the complete command at that moment. This preliminary preparation eliminates the need for complex real-time authentication operations and reduces interaction requirements.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces an authentication system with a database of signed command templates as an intermediary between the system administrator and the target systems. This intermediary handles the complex authentication and signing operations in advance, allowing administrators to issue commands with minimal interaction while maintaining security. The database acts as a mediator that stores pre-authenticated command patterns.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If traditional remote command issuance methods are used, then commands can be sent to target systems, but unauthorized users may issue unauthorized commands

Engineering Contradiction:
Improvecommand authenticationVSAvoidauthentication process
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system performs authentication and digital signing operations in advance when creating command templates, rather than requiring complex real-time authentication when commands are issued. The commands are pre-signed with the administrator's private key and stored in the database, ensuring reliability while simplifying the operational process.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The authenticated command templates in the database are self-contained with embedded digital signatures. When retrieved and executed, these templates automatically provide their own authentication verification without requiring additional interactive authentication steps, making the process easier while maintaining security.

Inventive Principle:
Principle #25Self-service

3Reliability

If individual preconfiguration of target systems with trust anchors is performed, then secure command execution is enabled, but the process becomes complex and time-consuming

Engineering Contradiction:
Improvesecure command executionVSAvoidpreconfiguration time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent creates a universal authentication mechanism where a single authentication system with a database of signed command templates can serve multiple target systems. Instead of configuring each target system individually with separate trust anchors, the system uses a centralized database that can authenticate commands for multiple targets, significantly reducing preconfiguration time while maintaining security.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The authentication system with its database of signed templates acts as a universal intermediary that eliminates the need for individual trust anchor configuration at each target system. This intermediary handles all authentication centrally, reducing both time and complexity while ensuring reliable secure command execution.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Ease of operation

If minimal interaction with system administrator is required, then ease of operation improves, but effective authentication may be compromised

Engineering Contradiction:
Improveadministrator interactionVSAvoidauthentication security
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The system performs all critical authentication and digital signing operations in advance when creating and storing command templates in the database. This preliminary action ensures strong authentication security is established before commands are issued, allowing minimal interaction during actual command issuance without compromising reliability.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The pre-signed command templates in the database are self-authenticating, containing embedded digital signatures that verify their origin and integrity automatically. This self-service capability maintains strong authentication security while requiring minimal administrator interaction during command execution.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS8225086B2Method and apparatus for remotely authenticating a command
Publication Date: 2012.07.17 ORACLE AMERICAN INC
  • US8225086B2 patent drawing
  • US8225086B2 patent drawing
  • US8225086B2 patent drawing

AI summary

A system that remotely authenticates a command is presented. During operation, an authentication system receives the command from an intermediary system, wherein the command is to be executed on a target system. Next, the authentication system authenticates the intermediary system. If the intermediary system is successfully authenticated, the authentication system authenticates the command using a private key for the authentication system to produce an authenticated command. Next, the authentication system sends the authenticated command to the intermediary system, thereby enabling the intermediary system to send the authenticated command to the target system so that the target system can use a public key for the authentication system to verify and execute the command.