Secure Batch Access via Root Key Extraction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Administrative software tools face security risks when accessing multiple systems in batch mode due to the potential compromise of root accounts and the vulnerability of storing private encryption keys, which can lead to the compromise of other interconnected systems.

Innovation Solution

A method and system that involve obtaining a private key, storing it in a root-owned file system, disabling interactive login access to the root account, installing a secure application with root execution privileges, and using this application to access remote computer systems over a network without providing login credentials, while ensuring the private key is stored in an encrypted file system accessible only by authorized accounts.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If root account login access is enabled for administrative tools, then ease of operation is improved, but security is worsened due to potential compromise of root accounts and private encryption keys

Engineering Contradiction:
Improveease of operationVSAvoidsecurity
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent extracts the root account login capability from the administrative tool execution process. Instead of requiring root account login, the system uses a dedicated service account with minimal necessary privileges. This separates the authentication mechanism (login) from the privilege execution mechanism (batch mode with sudo), eliminating the security vulnerability of storing private keys in accessible root directories while maintaining operational capability.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces an intermediary authentication mechanism using SSH key pairs and sudo privileges. Rather than directly logging in as root, the system uses a service account with an SSH private key for authentication to remote systems, and sudo for local privileged operations. This intermediary layer protects the root account while enabling administrative functionality.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If private encryption keys are stored in root-owned file systems, then reliability of key access is improved, but security is worsened due to vulnerability to compromise if root account is accessed

Engineering Contradiction:
Improvereliability of key accessVSAvoidsecurity vulnerability
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent applies local quality by creating a dedicated service account with specific, limited privileges and ownership of the SSH key. Instead of using the root account universally, the system assigns local ownership and control to a specific service account. This ensures that even if root is compromised, the service account's keys remain protected by separate authentication credentials and file permissions.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent extracts the SSH key ownership from the root account and assigns it to a dedicated service account. This separation removes the vulnerability where compromise of root access would automatically expose private keys. The service account becomes the sole owner and controller of its authentication credentials, creating an isolated security boundary.

Inventive Principle:
Principle #2Taking out (Extraction)

3Productivity

If batch mode access without password is implemented, then productivity is improved, but security is worsened due to elimination of password authentication safeguards

Engineering Contradiction:
ImproveproductivityVSAvoidsecurity
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent replaces the mechanical password authentication system with cryptographic SSH key-based authentication. Instead of transmitting passwords that can be eavesdropped or brute-forced, the system uses asymmetric cryptography where the private key proves identity without being transmitted. This substitution maintains batch mode automation while providing stronger security guarantees against interception and attack.

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

Data Source

PatentUS9900294B2Key-based access in batch mode
Publication Date: 2018.02.20 ORACLE INT CORP
  • US9900294B2 patent drawing
  • US9900294B2 patent drawing
  • US9900294B2 patent drawing

AI summary

A method for accessing a remote computer system may include obtaining a private key, storing the private key in a file system owned by a root account, disabling login access to the root account from user accounts, installing a secure application with root execution privileges, mounting, via the secure application, the file system, obtaining, via the secure application, the private key from the file system, and accessing, via the secure application and over a network, the remote computer system using the private key.