Abstract: Systems and methods for endpoint context-driven, dynamic workspaces are described.

Abstract: Systems and methods for securely deploying a collective workspace across multiple local management agents are described. In some embodiments, 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, cause the IHS to: receive, at a workspace orchestration service from a first local management agent, first context information and a first split key; receive, at the workspace orchestration service from a second local management agent, second context information and a second split key; determining, by the workspace orchestration service, that the first and second context information match a collaborative workspace policy; in response to the determination, authenticate the first and second split keys; and in response to the authentication, transmit a collaborative workspace definition to the first and second local management agents.

Abstract: Methods and systems are provided that may be implemented in an automated manner to distribute and integrate information regarding threat indicators as they occur in real time. The provided methods and systems may be implemented to combine threat indicator characteristic information in real time with application behavior patterns, information handling system types, and/or application types; and to automatically apply the resulting intelligence together to improve malicious attack defense at the application and information handling system level at scale.

Abstract: Examples described herein relate to apparatuses and methods of providing automated teller machine (ATM) status notifications. A method includes detecting a signal near an ATM, determining that the signal is indicative of the ATM being comprised, calculating a compromise score based at least on the determination that the signal is indicative of the ATM being compromised, and displaying an image on a user interface of the user device in a manner that reflects the compromise score.

Abstract: Systems and methods are provided for swapping computing architectures used by workspaces operating on an Information Handling System (IHS). A first workspace definition is generated for deployment of a workspace on the IHS using a first computing architecture. A timer is initiated upon deployment of the workspace on the IHS according to the first workspace definition. Upon expiration of the timer, a second workspace definition is generated for redeployment of the workspace using a second computing architecture. The workspace is then redeployed on the IHS according to the second workspace definition. The duration of the timer may be a randomized interval, or may be selected based on security and/or productivity metrics for the deployment of the workspace on the IHS. Through swapping of the computing architecture used by the workspace, the attack surface presented by the workspace is regularly altered, thus thwarting malicious actors attempting to compromise the workspace.

Abstract: Systems and methods for detecting security attacks using workspace orchestration logs are described. In some embodiments, a workspace orchestration server may include a processor and a memory coupled to the processor, the memory having program instructions stored thereon that, upon execution, may cause the server to: maintain a first workspace orchestration log, receive a second workspace orchestration log from a client Information Handling System (IHS), and identify the security attack, at least in part, in response to a discrepancy between the first and second workspace orchestration logs.

Abstract: Systems and methods for dynamic workspace targeting with crowdsourced user context are described. In some embodiments, an Information Handling System (IHS) of a workspace orchestration service 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: detect execution of an application in a workspace instantiated by a client IHS; validate the application based upon productivity context information and security context information received from the client IHS; and in response to the validation, distribute the validated application to another workspace instantiated by another client IHS.

Abstract: Systems and methods for hardware-based protection of Application Programming Interface (API) keys are described. In some embodiments, an endpoint 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: send an encrypted API key to a trusted controller; and receive a decrypted API key from the trusted controller.

Abstract: Disclosed herein are systems and methods for executing a transaction via a locker. A seller is provided initial access to the locker to deposit a good in the locker. The seller deposits the good in the locker. Following the seller depositing the good in the locker, the seller's access is revoked, and the buyer is provided access to the locker. The buyer may then arrive at the locker and provide authentication information to an authentication device. When the buyer is authenticated, the locker door (with the good inside the locker) is unlocked. The buyer can then inspect and accept the good. When the good is accepted, funds may be transferred from an account associated with the buyer to an account associated with the seller.

Abstract: Systems and methods for providing trusted local orchestration of workspaces are described. In some embodiments, an Information Handling System (IHS) may include a processor and a system memory coupled to the processor, the system memory having program instructions stored thereon that, upon execution, cause the IHS to: receive an orchestration code from a workspace orchestration service; record, using a trusted controller coupled to the processor, a log comprising: the orchestration code, and an indication of a sequence of operations performed during an instantiation of a workspace by the local management agent; provide a copy of the log to the workspace orchestration service; and establish a connection between the workspace and the workspace orchestration service in response to the workspace orchestration service's successful: (i) authentication of the orchestration code, and (ii) verification of the sequence of operations.

Abstract: A method implemented on a visual computing device to authenticate one or more users includes receiving a first three-dimensional pattern from a user. The first three-dimensional pattern is sent to a server computer. At a time of user authentication, a second three-dimensional pattern is received from the user. The second three-dimensional pattern is sent to the server computer. An indication is received from the server computer as to whether the first three-dimensional pattern matches the second three-dimensional pattern within a margin of error. When the first three-dimensional pattern matches the second three-dimensional pattern within the margin of error, the user is authenticated at the server computer. When the first three-dimensional pattern does not match the second three-dimensional pattern within the margin of error, user is prevented from being authenticated at the server computer.

Abstract: A firmware update method maintains a firmware resource table for multiple firmware modules. The table includes a globally unique identifier (GUID) of the module and current version information. A firmware capsule is delivered to a capsule delivery service (CDS) and pushed to a platform. The capsule includes a firmware update and firmware dependency components, indicating GUIDs and minimum current versions of one or more other firmware modules that must be found in the resource table before installing the firmware module being processed. An update may be perform for the particular firmware module responsive to confirming the current version information satisfies the dependency criteria. If the version information does not satisfy the dependency criteria, the firmware capsule may be staged to a platform store and GUID in the resource table may be removed. Conversely, successfully processing a previously staged firmware capsule may include restoring or otherwise updating the GUID.

Abstract: Systems and methods for endpoint context-driven, dynamic workspaces are described.

Abstract: Various embodiments, relate to a system of lockers including a plurality of tracks and a plurality of walls. At least two of the plurality of walls slidably coupled to at least two of the plurality of tracks. Four of the plurality of walls form four sides of a locker cavity. The system also includes a plurality of doors. Each of the plurality of doors are oriented perpendicular to the plurality of the walls. A first door of the plurality of doors is coupleable to a second door of the plurality of doors so as to form a third door, and at least one of the plurality of doors form one side of the locker cavity. The system also includes a back wall, which forms one side of the locker cavity. The system further includes a lock for securing positions of the plurality of walls and of the plurality of doors.

Abstract: A method performed by an issuer computing system includes receiving identification information for a customer from a retailer computing system. The customer is pre-approved for a payment account based on the identification information. A request to open the pre-approved payment account is received. Account registration information for opening the payment account and a mobile device identifier associated with the customer is received. The customer is approved for opening the payment account based on the account registration information. The payment account is established for the customer. Establishing the payment account includes generating a payment token for the payment account. In response to establishing the payment account, the payment token is automatically provisioned to a mobile wallet associated with the mobile device based on the mobile device identifier.

Abstract: Systems and methods for modernizing workspace and hardware lifecycle management in an enterprise productivity ecosystem are described.

Abstract: Systems and methods for providing trusted local orchestration of workspaces are described. In some embodiments, an Information Handling System (IHS) may include a processor and a system memory coupled to the processor, the system memory having program instructions stored thereon that, upon execution, cause the IHS to: receive an orchestration code from a workspace orchestration service; record, using a trusted controller coupled to the processor, a log comprising: the orchestration code, and an indication of a sequence of operations performed during an instantiation of a workspace by the local management agent; provide a copy of the log to the workspace orchestration service; and establish a connection between the workspace and the workspace orchestration service in response to the workspace orchestration service's successful: (i) authentication of the orchestration code, and (ii) verification of the sequence of operations.

Abstract: Systems and methods for creating and handling workspace indicators of compromise (IOC) based upon configuration drift are described. In some embodiments, a memory storage device may have 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: receive configuration information from a client IHS at a workspace orchestration service, where the configuration information represents a change in a configuration of a workspace executed by the client IHS, and where the workspace is instantiated based upon a workspace definition provided by the workspace orchestration service; determine, by the workspace orchestration service, that the configuration information matches an IOC; and transmit, from the workspace orchestration service to the client IHS, an instruction to perform an action responsive to the IOC.

Abstract: Systems and methods relating to a lockbox bank for currency drop-offs are provided. A lockbox bank includes one or more lockboxes, a safe coupled to the one or more lockboxes, and a terminal of a lockbox computing system. Each lockbox includes a receptacle configured to receive a currency drop-off and a locking mechanism. The terminal includes a network interface, a display device, one or more input/output devices, and a processing circuit including a processor and a memory. The memory is structured to store instructions that are executable by the processor and cause the processing circuit to receive a request from the customer to use a lockbox for a currency drop-off, receive access credentials, verify the access credentials, in response to successful verification, grant the customer access to a lockbox, and in response to determining that the drop-off has been completed, move the drop-off from the receptacle to the safe.