Securing external access to runtime services in appliances
Disclosed herein are methods, systems, and processes to secure external access to runtime systems in appliances. A request to register a security token configured to permit access to a computing system is received at the computing system. An authorization response authenticating the security token is sent. Another request to access the computing system based on the authenticated security token is received, and access is permitted to the computing system.
1. A computer-implemented method comprising:
generating a security token at a client controlled computing device, wherein
the security token is generated and sent to a support computing device to authorize limited access to a debug mode of an appliance that is providing business services to the client controlled computing device,
the security token is configured to limit access to the debug mode using debug mode login credentials, and
the security token is configured to control types of commands that are available through a command line interface shell (CLISH) in the debug mode of the appliance;
receiving a first request to register the security token from the client controlled computing device at the appliance, wherein
the appliance comprises software configured to perform one or more internal computing services, a graphical user interface (GUI), and the CLISH, and the security token is received from the client controlled computing device at the GUI,
the appliance is configured to prevent access to change the one or more internal computing services during a runtime mode of operation of the appliance,
the appliance is configured with the debug mode, and
the debug mode is configured to be accessed via the CLISH, wherein the CLISH is configured as a restrictive shell to restrict direct access to low-level functions of the appliance while in the debug mode;
receiving a second request to register the security token from the support computing device that is different from the client controlled computing device and that provides technical support to the appliance without receiving business services therefrom, wherein
the second request to register the security token is received from the support computing device at the GUI of the appliance;
in response to receiving the second request to register the security token from the support computing device at the GUI of the appliance,
determining, by the appliance, that the security token authorizes access to the debug mode,
sending an authorization response authenticating the security token to the support computing device,
receiving login credentials and token authorization information at the CLISH from the support computing device, and
authorizing the support computing device to access the debug mode if the token authorization information indicates that the support computing device is authorized to access the debug mode of the appliance;
receiving command line commands at the CLISH from the support computing device to perform one or more operations in the debug mode of the appliance, wherein
the one or more operations are configured to be performed in response to the command line commands received from the support computing device at the CLISH, and
commands available through the CLISH in the debug mode are limited, at least in part, to the types of commands authorized by the security token; and
allowing multiple, separate commands to be received at the CLISH from the support computing device and executed during the debug mode so long as the security token remains authorized.
2. The computer-implemented method of claim 1 , wherein
the security token comprises a Quick Response (QR) code, and
the authorization response authenticating the security token is sent if the security token matches the QR code.
3. The computer-implemented method of claim 1 , further comprising:
determining that the access to the debug mode of the appliance has expired as determined by authorizations associated with the security token; and
invalidating the security token associated with the second request when the access to the debug mode of the appliance has expired as determined by authorizations associated with by security token.
4. The computer-implemented method of claim 1 , further comprising:
permitting debugging of one or more input commands and/or one or more output commands using the CLISH, without entering an operating system of the appliance in a way that would require elevation of the security token to a root privilege.
5. The computer-implemented method of claim 4 , wherein
preventing elevation of the security token to the root privilege does not prevent monitoring of a real-time output of the one or more output commands, and
the real-time output occurs during a runtime state of the appliance.
6. A non-transitory computer readable storage medium comprising program instructions executable to perform a method comprising:
generating a security token at a client controlled computing device, wherein
the security token is generated and sent to a support computing device to authorize limited access to a debug mode of an appliance that is providing business services to the client controlled computing device,
the security token is configured to limit access to the debug mode using debug mode login credentials, and
the security token is configured to control types of commands that are available through a command line interface shell (CLISH) in the debug mode of the appliance;
receiving a first request to register the security token from the client controlled computing device at the appliance, wherein
the appliance comprises software configured to perform one or more internal computing services while in a runtime mode of operation of the appliance, a graphical user interface (GUI), and the CLISH, and the security token is received from the client controlled computing device at the GUI,
the appliance is configured to prevent access to change the one or more internal computing services during the runtime mode of operation of the appliance,
the appliance is configured with the debug mode, and
the debug mode is configured to be accessed via the CLISH, wherein the CLISH is configured as a restrictive shell to restrict direct access to low-level functions of the appliance while in the debug mode;
receiving a second request to register the security token from the support computing device that is different from the client controlled computing device and that provides technical support to the appliance without receiving business services therefrom, wherein
the second request to register the security token is received from the support computing device at the GUI of the appliance;
in response to receiving the second request to register the security token from the support computing device at the GUI of the appliance,
determining, by the appliance, that the security token authorizes access to the debug mode,
sending an authorization response authenticating the security token to the support computing device,
receiving login credentials and token authorization information at the CLISH from the support computing device, and
authorizing the support computing device to access the debug mode if the token authorization information indicates that the support computing device is authorized to access the debug mode of the appliance;
receiving command line commands at the CLISH from the support computing device to perform one or more operations in the debug mode of the appliance, wherein
the one or more operations are configured to be performed in response to the command line commands received from the support computing device at the CLISH, and
commands available through the CLISH in the debug mode are limited, at least in part, to the types of commands authorized by the security token; and
allowing multiple, separate commands to be received at the CLISH from the support computing device and executed during the debug mode so long as the security token remains authorized.
7. The non-transitory computer readable storage medium of claim 6 , wherein
the security token comprises a Quick Response (QR) code, and
the authorization response authenticating the security token is sent if the security token matches the QR code.
8. The non-transitory computer readable storage medium of claim 6 , wherein the method further comprises:
determining that the access to the debug mode of the appliance has expired; and
invalidating the security token associated with the second request.
9. The non-transitory computer readable storage medium of claim 6 , wherein the method further comprises:
permitting debugging of one or more input commands and/or one or more output commands using the CLISH, without entering an operating system of the appliance in a way that would require elevation of the security token to a root privilege.
10. The non-transitory computer readable storage medium of claim 9 , wherein
preventing elevation of the security token to the root privilege does not prevent monitoring of a real-time output of the one or more output commands; and
the real-time output occurs during a runtime state of the appliance.
11. A system comprising:
a client controlled computing device;
a support computing device;
an appliance;
wherein the client controlled computing device, the support computing device, and the appliance are configured with instructions executable by one or more processors to cooperatively perform a method comprising:
generating a security token at the client controlled computing device, wherein
the security token is generated and sent to the support computing device to authorize limited access to a debug mode of the appliance that is providing business services to the client controlled computing device,
the security token is configured to limit access to the debug mode using debug mode login credentials, and
the security token is configured to control types of commands that are available through a command line interface shell (CLISH) in the debug mode of the appliance;
receiving a first request to register the security token from the client controlled computing device at the appliance, wherein
the appliance comprises software configured to perform one or more internal computing services, a graphical user interface (GUI), and the CLISH, and the security token is received from the client controlled computing device at the GUI,
the appliance is configured to prevent access to change the one or more internal computing services during a runtime mode of the appliance,
the appliance is configured with the debug mode, and
the debug mode is configured to be accessed via the CLISH, wherein the CLISH is configured as a restrictive shell to restrict direct access to low-level functions of the appliance while in the debug mode;
receiving a second request to register the security token from the support computing device that is different from the client controlled computing device and that provides technical support to the appliance without receiving business services therefrom, wherein
the second request to register the security token is received from the support computing device at the GUI of the appliance;
in response to receiving the second request to register the security token from the support computing device at the GUI of the appliance,
determining, by the appliance, that the security token authorizes access to the debug mode,
sending an authorization response authenticating the security token to the support computing device,
receiving login credentials and token authorization information at the CLISH from the support computing device, and
authorizing the support computing device to access the debug mode if the token authorization information indicates that the support computing device is authorized to access the debug mode of the appliance;
receiving command line commands at the CLISH from the support computing device to perform one or more operations in the debug mode of the appliance, wherein
the one or more operations are configured to be performed in response to the command line commands received from the support computing device at the CLISH, and
commands available through the CLISH in the debug mode are limited, at least in part, to the types of commands authorized by the security token; and
allowing multiple, separate commands to be received at the CLISH from the support computing device and executed during the debug mode so long as the security token remains authorized.
12. The system of claim 11 , wherein
the security token comprises a Quick Response (QR) code, and
the authorization response authenticating the security token is sent if the security token matches the QR code.
13. The system of claim 11 , wherein the method further comprising:
permitting debugging of one or more input commands and/or one or more output commands using the CLISH, without entering an operating system of the appliance in a way that would require elevation of the security token to a root privilege.
14. The system of claim 13 , wherein
preventing elevation of the security token to the root privilege does not prevent monitoring of a real-time output of the one or more output commands; and
the real-time output occurs during a runtime state of the appliance.