Orchestration based on workspace component scores
Systems and methods for orchestration based on workspace component scores are described. In an illustrative, non-limiting embodiment, an Information Handling System (IHS) may include a processor and a memory coupled to the processor, the memory having program instructions stored thereon that, upon execution by the processor, cause the IHS to receive, at a local management agent from a workspace orchestration service, one or more files or policies configured to enable the local management agent to instantiate a workspace based upon a workspace definition, where the workspace comprises a plurality of workspace components, where the workspace definition is created based, at least in part, upon a security target, and where an aggregated security score for the plurality of workspace components meets the security target; and instantiate the workspace.
1 . An Information Handling System (IHS), comprising:
a processor; and
a memory coupled to the processor, the memory configured with program instructions stored thereon that, upon execution by the processor, cause the IHS to:
receive, at a local management agent from a workspace orchestration service, one or more files or policies configured to enable the local management agent to instantiate a workspace based upon a workspace definition, wherein the workspace comprises a plurality of workspace components, wherein the plurality of workspace components comprises at least one of: an application, a remote service, or a container, wherein the workspace definition is created based, at least in part, upon a security target, wherein an aggregated security score computed from a plurality of policy-weighted individual sub-scores for the plurality of workspace components meets the security target, wherein the aggregated security score is calculated based upon a combination of individual security scores, wherein each individual security score is associated with a respective workspace component, and wherein keys or digital certificates are delivered on-demand, based at least in part on the security target, to protect output data authenticity; and
instantiate the workspace.
2 . The IHS of claim 1 , wherein at least one of the individual security scores is determined, at least in part, based upon at least one of: an identity of the application, an identity of the remote service, or a type of container.
3 . The IHS of claim 1 , wherein at least one of the individual security scores is determined, at least in part, based upon at least one of: a source of data used by the application, a source of data used by the remote service, or a destination of data output from the container.
4 . The IHS of claim 1 , wherein at least one of the individual security scores is determined, at least in part, based upon at least one of: a data destination or storage for the application, a data destination or storage for the remote service, or a data destination or storage for the container.
5 . The IHS of claim 1 , wherein at least one of the individual security scores is determined, at least in part, based upon at least one of: execution of a workspace component in a Trusted Execution Environment (TEE), execution of a workspace component in a secondary processor or accelerator, use or type of encryption/decryption, use or type of input data authentication, or use or type of output data signing.
6 . The IHS of claim 1 , wherein the security target is calculated, at least in part, based upon at least one of: an identification of a software application requested by a user of the IHS, an identification of a datafile requested by the user of the IHS, an identification of a locale of the IHS, an identification of a user of the IHS, an identification of a network of the IHS, an identification of hardware of the IHS, or an identification of a storage system of the requested datafile.
7 . The IHS of claim 1 , wherein the aggregated security score is calculated, at least in part, based upon at least one of: a risk metric associated with a locale of the IHS, a risk metric associated with a user of the IHS, a risk metric associated with a network of the IHS, a risk metric associated with hardware of the IHS, a risk metric associated with a requested datafile, or a regulatory risk metric.
8 . The IHS of claim 1 , wherein the workspace definition comprises at least one of: a threat monitor 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.
9 . A memory storage device configured with program instructions stored thereon that, upon execution by one or more processors of an Information Handling System (IHS) of a workspace orchestration service, cause the IHS to:
create a workspace definition based upon a security target; and
transmit, to a client IHS, one or more files or policies configured to enable the client IHS to instantiate a workspace based upon the workspace definition, wherein the workspace comprises a plurality of workspace components, wherein the plurality of workspace components comprises at least one of: an application, a remote service, or a container, wherein an aggregated security score computed from a plurality of policy-weighted individual sub-scores for the plurality of workspace components meets the security target, wherein the aggregated security score is calculated based upon a combination of individual security scores associated with respective workspace components, and wherein keys or digital certificates are delivered on-demand, based at least in part on the security target, to ensure workload integrity.
10 . The memory storage device of claim 9 , wherein at least one of the individual security scores is determined, at least in part, based upon at least one of: an identity of the application, an identify of the remote service, a type of container, a source of data used by the application, a source of data used by the remote service, or a source of data used within the container, a data destination or storage for the application, a data destination or storage for the remote service, a data destination or storage for the container, execution of a workspace component in a Trusted Execution Environment (TEE), execution of a workspace component in a secondary processor or accelerator, use or type of encryption/decryption, use or type of input data authentication, or use or type of output data signing.
11 . The memory storage device of claim 9 , wherein the program instructions, upon execution by the one or more processors, further cause the IHS to, in response to a determination that the aggregated security score is below a threshold value, modify the workspace definition and transmit one or more additional files or policies to the client IHS, the one or more additional files or policies configured to enable the client IHS to modify the workspace based on the modified workspace definition.
12 . The memory storage device of claim 11 , wherein the modified workspace definition is configured to replace at least a first workspace component which has a first individual security score with a second workspace component which has a second individual security score smaller than the first individual security score.
13 . The memory storage device of claim 11 , wherein the modified workspace definition is configured to add or replace a key or digital certificate exchange for a particular workspace component configured to receive or output data.
14 . The memory storage device of claim 9 , wherein the security target is calculated, at least in part, based upon at least one of: an identification of a software application requested by a user of the client IHS or an identification of a datafile requested by the user of the client IHS, an identification of a locale of the client IHS, an identification of a user of the client IHS, an identification of a network of the client IHS, an identification of hardware of the client IHS, an identification of a requested datafile, an identification of a storage system of the requested datafile, a risk metric associated with a locale of the client IHS, a risk metric associated with a user of the client IHS, a risk metric associated with a network of the client IHS, a risk metric associated with hardware of the client IHS, a risk metric associated with a requested datafile, a regulatory risk metric, a threat monitor 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.
15 . A method, comprising:
creating a workspace definition, by a workspace orchestration service, based upon a security target; and
transmitting, by the workspace orchestration service to a local management agent of a client Information Handling System (IHS), one or more files or policies configured to enable the local management agent to instantiate a workspace based upon the workspace definition, wherein the workspace comprises a plurality of workspace components, wherein the plurality of workspace components comprises at least one of: an application, a remote service, or a container, wherein an aggregated security score computed from a plurality of policy-weighted individual sub-scores for the plurality of workspace components meets the security target, wherein the aggregated security score is calculated based upon a combination of individual security scores associated with corresponding workspace components, and wherein keys or digital certificates are delivered on-demand, based at least in part on the security target, to protect confidential data sources.
16 . The method of claim 15 , wherein at least one of the individual security scores is determined, at least in part, based upon at least one of: an identity of the application, an identity of the remote service, a type of container, a source of data used by the application, a source of data used by a remote service, a source of data used within the container, a data destination or storage for the application, a data destination or storage for the remote service, a data destination or storage for the container, execution of a workspace component in a Trusted Execution Environment (TEE), execution of a workspace component in a secondary processor or accelerator, use or type of encryption/decryption, use or type of input data authentication, or use or type of output data signing.