Remote Secured Console for Inoperable Virtual Machines
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for accessing an inoperable virtual machine are inefficient, often requiring on-site intervention and taking significant time due to security concerns and lack of direct access, leading to frustration for both customers and support personnel.
Innovation Solution
A remote secured console is created over a secured connection using a token and password generated by a service person, allowing secure access to the inoperable virtual machine without direct exposure to potential security risks, utilizing a separate channel for token and password transmission and employing encryption for secure communication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If support personnel perform on-site debugging with live CD, then access to inoperable virtual machine is achieved, but time consumption increases significantly (1-2 hours)
Solution Approach 1:
A boot service is pre-installed within the virtual machine that remains dormant during normal operation but activates when the VM becomes inoperable, eliminating the need for on-site live CD debugging and reducing access time from hours to minutes
Solution Approach 2:
The boot service acts as an intermediary component embedded in the VM that facilitates remote debugging by establishing a bridge between the inoperable VM and the debugging system, allowing support personnel to access the VM without physical presence
2Ease of operation
If Remote Desktop Service is implemented in the virtual machine, then remote access is enabled, but security risks increase due to backdoor creation
Solution Approach 1:
The boot service is pre-configured within the VM to activate only when needed for debugging, rather than continuously running as a Remote Desktop Service, thereby enabling remote access capability while minimizing the window of security exposure
Solution Approach 2:
The debugging interface dynamically activates only when the VM is in an inoperable state and automatically deactivates when debugging is complete, creating a temporary remote access channel that exists only when necessary, thus balancing ease of operation with security
3Reliability
If service personnel travel to customer location for debugging, then direct access to virtual machine is achieved, but travel time and operational efficiency decrease
Solution Approach 1:
The boot service serves as a remote intermediary that enables support personnel to access and debug the inoperable VM from any location without physical travel, converting a time-intensive on-site process into a rapid remote operation
Solution Approach 2:
The physical mechanical process of traveling to the customer site is replaced by an electronic remote debugging mechanism, where the boot service enables network-based access to the VM, eliminating travel time and improving operational efficiency
Data Source
AI summary
A method for creation of a secured connection for an inoperable virtual machine includes receiving a token at an on-host service running on an inoperable virtual machine (“VM”) on a server. The token is generated by a remote service person. The method includes receiving a user generated password from a user having direct access to the on-host service. The method includes creating a secured connection, using the token and password, between the on-host service and a remote server of the service person. The method includes transmitting a VM identifier of the inoperable VM to the user and receiving communications from the remote server. The communications include commands for the inoperable VM. The service person accesses the on-host service and inoperable VM using the VM identifier and the password. The password and VM identifier are transmitted to the service person by the user via a channel separate from the secured connection.