Granted Patent B2

US 11,757,881 · App. 17/126,144 · Granted Sep 12, 2023

Inventors: Carlton A. Andrews (Austin, TX); Charles D. Robison (Buford, GA); Nicholas D. Grobelny (Austin, TX); Joseph Kozlowski (Hutto, TX); David Konetski (Austin, TX)

Assignee: Dell Products, L.P.

H04L63/0884H04L63/0442H04L63/0876H04L63/166

Abstract

Claims (55)

1. A first Information Handling System (IHS), comprising:

a processor; and

a memory coupled to the processor, the memory having program instructions stored thereon that, upon execution, cause the first IHS to:

establish a first connection with a second IHS, wherein the second IHS is managed by a workspace orchestration service, and configured to establish a second connection with the workspace orchestration service, and wherein the workspace orchestration service is configured to:

receive device identification information of the first IHS from the second IHS; and

authenticate the device identification information of the first IHS, that was received from the second IHS, against a database provided by a manufacturer of the first IHS;

in response to a successful authentication, establish a third connection with the workspace orchestration service;

transmit context information to the workspace orchestration service, wherein the workspace orchestration service is further configured to:

calculate a security target and a productivity target based upon the context information, wherein the security target is calculated, at least in part, based upon a participation of the second IHS in the authentication of the first IHS; and

create a workspace definition based upon the security target and the productivity target; and

receive the workspace definition from the workspace orchestration service via the third connection.

2. The first IHS of claim 1 , wherein the second IHS is managed by the workspace orchestration service prior to the first connection.

3. The first IHS of claim 1 , wherein the program instructions upon execution, further cause the first IHS to:

receive an orchestration code from the second IHS, wherein the second IHS is configured to receive the orchestration code from the workspace orchestration service and to transmit the orchestration code to the first IHS; and

transmit the device identification information and the orchestration code encrypted with a first key to the second IHS, wherein the second IHS is configured to forward the encrypted device identification information and orchestration code to the workspace orchestration service, and wherein the workspace orchestration service is configured to retrieve a second key corresponding to the first key and decrypt the encrypted device identification information and orchestration code using the second key.

4. The first IHS of claim 1 , wherein the program instructions, upon execution, further cause the first IHS to:

receive Transport Layer Security (TLS) or Secure Sockets Layer (SSL) data from the second IHS, wherein the second IHS is configured to receive the TLS or SSL data from the workspace orchestration service and to transmit the TLS or SSL data to the first IHS; and

establish the third connection using the TLS or SSL data.

5. The first IHS of claim 1 , wherein the database comprises a software entitlement database.

6. The first IHS of claim 1 , wherein the security target is calculated, at least in part, based upon at least one of: a risk metric associated with a locale of the first IHS, a risk metric associated with a user of the first IHS, a risk metric associated with a network of the client IHS, a risk metric associated with hardware of the first IHS, a risk metric associated with a requested datafile, or a regulatory risk metric associated with the user, the locale, and the requested datafile, and wherein the productivity target is calculated by the workspace orchestration service based upon at least one of: a resource metric associated with a locale of the first IHS, a resource metric associated with a user of the first IHS, a resource metric associated with a network of the first IHS, a resource metric associated with hardware of the first IHS, or a resource metric associated with a storage system of a requested datafile.

7. The first IHS of claim 1 , wherein the workspace definition comprises at least one of: a threat monitoring level, a threat detection level, a threat analytics level, a threat response level, a storage confidentiality level, a network confidentiality level, a memory confidentiality level, a display confidentiality level, a user authentication level, an Information Technology (IT) administration level, a regulatory compliance level, a local storage control level, a Central Processing Unit (CPU) access level, a graphics access level, an application usage level, or an application installation level.

8. The first IHS of claim 1 , wherein the program instructions, upon execution, further cause the IHS to instantiate a workspace based upon the workspace definition.

9. A memory storage device having program instructions stored thereon that, upon execution by an Information Handling System (IHS) of a workspace orchestration service, cause the IHS to:

establish a first connection with a first IHS managed by the workspace orchestration service;

receive device identification information of a second IHS from the first IHS, wherein the first IHS is configured to retrieve the device identification information from the second IHS over a second connection;

authenticate the device identification information of the second IHS, received from the first IHS, against a database provided by a manufacturer of the second IHS;

in response to a successful authentication of the second IHS, establish a third connection with the second IHS;

receive context information from the second IHS;

calculate a security target and a productivity target based upon the context information, wherein the security target is calculated, at least in part, based upon a participation of the first IHS in the authentication of the second IHS;

create a workspace definition based upon the security target and the productivity target; and

transmit the workspace definition to the second IHS via the third connection.

10. The memory storage device of claim 9 , wherein the program instructions, upon execution further cause the IHS to establish a trust relationship with the second IHS prior to the first connection.

11. The memory storage device of claim 9 , wherein the program instructions upon execution, further cause the IHS to:

transmit an orchestration code to the first IHS, wherein the first IHS is configured to transmit the orchestration code to the second IHS; and

receive device identification information and the orchestration code encrypted with a first key from the first IHS, wherein the first IHS is configured to forward the encrypted device identification information and orchestration code to the workspace orchestration service;

retrieve a second key corresponding to the first key; and

decrypt the encrypted device identification information and orchestration code using the second key.

12. The memory storage device of claim 9 , wherein the program instructions, upon execution, further cause the IHS to:

transmit Transport Layer Security (TLS) or Secure Sockets Layer (SSL) data to the first IHS, wherein the first IHS is configured to transmit the TLS or SSL data to the second IHS; and

establish the third connection using the TLS or SSL data.

13. The memory storage device of claim 9 , wherein the database comprises a software entitlement database.

14. The memory storage device of claim 9 , wherein the second IHS is configured to instantiate a workspace based upon the workspace definition.

15. A method, comprising:

establishing, by a first Information Handling System (IHS), a first connection with a second IHS;

obtain device identification information from the second IHS via the first connection;

transmitting, by the first IHS, the device identification information obtained from the second IHS to a workspace orchestration service over a second connection, wherein the first IHS is managed by the workspace orchestration service;

in response to a successful authentication of the device identification information of the second IHS by the workspace orchestration service against a database provided by a manufacturer of the second IHS, receive, by the first IHS, Transport Layer Security (TLS) or Secure Sockets Layer (SSL) from the workspace orchestration service; and

transmit, by the first IHS, the TLS or SSL data to the second IHS, wherein the second IHS is configured to:

establish a third connection with the workspace orchestration service using the TLS or SSL data; and

transmit context information to the workspace orchestration service; and

wherein the workspace orchestration service is configured to:

receive the context information from the second IHS;

calculate a security target and a productivity target based upon the context information, wherein the security target is calculated, at least in part, based upon a participation of the first IHS in the authentication of the second IHS;

create a workspace definition based upon the security target and the productivity target; and

transmit the workspace definition to the second IHS over the third connection.

Assignments (9)

Continuity (1)

Cited By (1)

US 12,204,464