System and method for providing session-level access management of a redirected device
View Patent ↗Managing access restriction to a device is provided. The operations may include determining that a device stack corresponds to a device that is remote to the server and is connected locally to a client that is remote to the server; attaching a device access restriction object on top of the device stack; receiving, at the device access restriction object, an access request to the device; and determining, at the device access restriction object, whether the access request is allowed access to the device.
1. A method for managing access restriction to a device, the method comprising:
determining, by traversing a device stack downwards to identify a device object corresponding to a virtual bus driver at the bottom of the device stack, at a server, that the device stack corresponds to a device that is remote to the server and is connected locally to a client that is remote to the server, the device stack including a plurality of device objects each associated with a device driver;
attaching a device access restriction object on top of the device stack;
receiving, at the device access restriction object, an access request to the device; and
determining, at the device access restriction object, whether the access request is allowed access to the device, including:
determining whether a session from which the access request is received is the same as a session of the client; and
determining that the access request is allowed if the session from which the access request is received is the same as the session of the client.
2. The method according to claim 1 , further comprising:
determining that the access request is blocked if the session from which the access request is received is not the same as the session of the client; and
generating an error message indicating that the device does not exist.
3. The method according to claim 1 , further comprising determining whether the device is configured to be provided with access restriction, wherein the attaching the access restriction object comprises:
attaching the access restriction object on top of the device stack if the device is configured to be provided with access restriction.
4. The method according to claim 1 , wherein the method is performed without hooking to a kernel module.
5. The method according to claim 1 , wherein the device is a USB device.
6. The method according to claim 1 , wherein the access request is made by a process of an application, and wherein receiving the access request to the device comprises:
intercepting the access request made by the process to the device.
7. A non-transitory machine-readable storage medium encoded with instructions executable by one or more processors to perform one or more operations, the one or more operations comprising:
determining, by traversing a device stack downwards to identify a device object corresponding to a virtual bus driver at the bottom of the device stack, at a server, that the device stack corresponds to a device that is remote to the server and is connected locally to a client that is remote to the server;
attaching a device access restriction object on top of the device stack;
receiving, at the device access restriction object, an access request to the device; and
determining, at the device access restriction object, whether the access request is allowed access to the device, including:
determining whether a session from which the access request is received is the same as a session of the client; and
determining that the access request is allowed if the session from which the access request is received is the same as the session of the client.
8. The non-transitory machine-readable storage medium according to claim 7 , wherein the one or more operations further comprises:
determining that the access request is blocked if the session from which the access request is received is not the same as the session of the client; and
generating an error message indicating that the device does not exist.
9. The non-transitory machine-readable storage medium according to claim 7 , wherein the one or more operations further comprises determining whether the device is configured to be provided with access restriction, wherein the attaching the access restriction object comprises attaching the access restriction object on top of the device stack if the device is configured to be provided with access restriction.
10. The non-transitory machine-readable storage medium according to claim 7 , wherein the one or more operations are performed without hooking to a kernel module.
11. The non-transitory machine-readable storage medium according to claim 7 , wherein the device is a USB device.
12. The non-transitory machine-readable storage medium according to claim 7 , wherein the access request is made by a process of an application, and wherein receiving the access request to the device comprises:
intercepting the access request made by the process to the device.
13. A server comprising:
a processor;
a memory communicatively coupled to the processor;
a device access restriction driver including instructions in the memory, the instructions executable by the processor, the instructions, when executed, configure the device access restriction driver to:
determine, by traversing a device stack downwards to identify a device object corresponding to a virtual bus driver at the bottom of the device stack, that the device stack corresponds to a device that is remote to the server and is connected locally to a client that is remote to the server, the device stack including a plurality of device objects each associated with a device driver;
attach a device access restriction object on top of the device stack;
the device access restriction object including instructions in the memory, the instructions executable by the processor, the instructions, when executed, configure the device access restriction object to:
receive an access request to the device; and
determine whether the access request is allowed access to the device, including:
determining whether a session from which the access request is received is the same as a session of the client; and
determining that the access request is allowed if the session from which the access request is received is the same as the session of the client.
14. The server according to claim 13 , wherein the device access restriction object further includes instructions in the memory, the instructions, when executed, configure the device access restriction object to:
determine that the access request is blocked if the session from which the access request is received is not the same as the session of the client; and
generate an error message indicating that the device does not exist.
15. The server according to claim 13 , wherein the device access restriction object further includes instructions in the memory, the instructions, when executed, configure the device access restriction object to:
determine whether the device is configured to be provided with access restriction; wherein attaching the access restriction object further comprises attaching the access restriction object on top of the device stack if the device is configured to be provided with access restriction.
16. The server according to claim 13 , wherein the device access restriction driver is not hooked to a kernel module.
17. The server according to claim 13 , wherein the device is a USB device.
18. The server according to claim 13 , wherein the access request is made by a process of an application, and wherein receiving the access request to the device comprises intercepting the access request made by the process to the device.