System and method for preventing thin/zero client from unauthorized physical access
First Claim
1. A system, comprising:
- a computing device as a thin client or a zero client, wherein the computing device comprises a central processing unit (CPU) and a chassis enclosing the CPU, and the computing device as the thin client or the zero client is remotely accessible by a server; and
a microcontroller located and operated entirely within the chassis of the computing device and operated independently and separately from the computing device, and communicatively connected to the chassis via a first interface, the microcontroller comprises a processor and a storage device storing computer executable code, wherein the computer executable code, when executed at the processor, is configured to;
monitor the chassis, wherein the chassis is configured to generate a signal for the first interface when the chassis is physically opened;
in response to receiving the signal from the chassis via the first interface, determine that a physical access event occurs to the computing device; and
in response to the physical access event,generate a log to record events for the computing device, and store the log in the storage device; and
perform a self-protect action to the computing device.
5 Assignments
0 Petitions
Accused Products
Abstract
Certain aspects direct to systems and methods for preventing a thin client or a zero client from unauthorized physical access. A microcontroller is provided and connected to the chassis of the thin client or zero client computing device via a first interface, such as a general-purpose input/output (GPIO) line. Whenever the chassis is physically opened, the chassis generates a signal, and sends the signal to the microcontroller via the GPIO line. Upon receiving the signal, the microcontroller determines that a physical access event occurs to the computing device. Unless the physical access event is authorized, the microcontroller may generate a log to record events for the computing device, and store the log in the storage device; and perform a self-protect action to the computing device. If network connectivity is available, the microcontroller may send the log to a server via the network.
10 Citations
20 Claims
-
1. A system, comprising:
-
a computing device as a thin client or a zero client, wherein the computing device comprises a central processing unit (CPU) and a chassis enclosing the CPU, and the computing device as the thin client or the zero client is remotely accessible by a server; and a microcontroller located and operated entirely within the chassis of the computing device and operated independently and separately from the computing device, and communicatively connected to the chassis via a first interface, the microcontroller comprises a processor and a storage device storing computer executable code, wherein the computer executable code, when executed at the processor, is configured to; monitor the chassis, wherein the chassis is configured to generate a signal for the first interface when the chassis is physically opened; in response to receiving the signal from the chassis via the first interface, determine that a physical access event occurs to the computing device; and in response to the physical access event, generate a log to record events for the computing device, and store the log in the storage device; and perform a self-protect action to the computing device. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10)
-
-
11. A method for preventing a thin client or a zero client from unauthorized physical access, the method comprising:
-
monitoring, by a microcontroller, a chassis of a computing device as the thin client or the zero client of a system, wherein the microcontroller is located and operated entirely within the chassis of the computing device and operated independently and separately from the computing device, and is communicatively connected to the chassis via a first interface, the computing device as the thin client or the zero client is remotely accessible by a server, and the chassis is configured to generate a signal for the first interface when the chassis is physically opened; in response to receiving the signal from the chassis via the first interface, determining, by the microcontroller, that a physical access event occurs to the computing device; and in response to the physical access event, generating, by the microcontroller, a log to record events for the computing device, and storing the log in a non-volatile memory; and performing, by the microcontroller, a self-protect action to the computing device. - View Dependent Claims (12, 13, 14, 15)
-
-
16. A non-transitory computer readable medium storing computer executable code, wherein the computer executable code, when executed at a processor of a microcontroller, is configured to:
-
monitor a chassis of a computing device as a thin client or a zero client of a system, wherein the microcontroller is located and operated entirely within the chassis of the computing device and operated independently and separately from the computing device, and is communicatively connected to the chassis via a first interface, the computing device as the thin client or the zero client is remotely accessible by a server, and the chassis is configured to generate a signal for the first interface when the chassis is physically opened; in response to receiving the signal from the chassis via the first interface, determine that a physical access event occurs to the computing device; and in response to the physical access event, generate a log to record events for the computing device, and store the log in a non-volatile memory; and perform a self-protect action to the computing device. - View Dependent Claims (17, 18, 19, 20)
-
Specification