Abstract: A disclosed method provides a Device Integrity and Zero Trust (DIZ) protocol to implement proactive as well as reactive firmware vulnerability management. The DIZ protocol identifies device-level firmware versions and vulnerabilities and dynamically compiles appropriate firmware updates. The protocol may further construct a telemetry of the security vulnerability statistics for dynamic identification of Signs of Compromise (SoC) and collectively interpret various other platform telemetry stats for compiling vulnerability resolutions. An artificial intelligence (AI) based scalable and continuous Adaptive and Trust Assessment (ATA) method is employed for dynamic integration of partner solutions based on threat intelligence and remediation data. Disclosed solutions may further implement a geo location independent security adaption method. The identification and assessment of SoCs beneficially reduces an attacker's ability to breach an organization's IT systems.

Abstract: An information handling system is configured, during a pre-extensible firmware interface initialization phase of the information handling system, to learn capabilities of components of the information handling system, create a hand-off block for storage of a virtual graphical browser firmware volume payload, and store learned capabilities of the components of the information handling system in the hand-off block. During a driver execution environment phase, the information handling system may retrieve the learned capabilities of the components of the information handling system stored in the hand-off block, publish learned capabilities retrieved from the hand-off block, retrieve the virtual graphics browser firmware volume payload stored in the hand-off block, and dispatch a virtual graphics browser learning driver and a virtual graphics browser interpreter driver based on retrieved virtual graphics browser firmware volume payload.

Abstract: A pre-boot screen can be accessed remotely. A remote access BIOS module can be employed on a computing system to logically split a GPU into a local screen rendering part and a remote access part and to logically split GPU memory into a local screen memory region and a remote access memory region. The remote access part of the GPU can access a pre-boot screen that has been copied to the remote access memory region and create network packets with payloads containing the pre-boot screen. The remote access part can then cause the network packets to be transferred to a NIC for delivery to a remote computing system. A remote access application on the remote computing system can extract and display the pre-boot screen. The remote access application can relay any user input back to the remote access BIOS module which can then cause the user input to be implemented locally.

Abstract: An information handling system is configured, during a pre-extensible firmware interface initialization phase of the information handling system, to learn capabilities of components of the information handling system, create a hand-off block for storage of a virtual graphical browser firmware volume payload, and store learned capabilities of the components of the information handling system in the hand-off block. During a driver execution environment phase, the information handling system may retrieve the learned capabilities of the components of the information handling system stored in the hand-off block, publish learned capabilities retrieved from the hand-off block, retrieve the virtual graphics browser firmware volume payload stored in the hand-off block, and dispatch a virtual graphics browser learning driver and a virtual graphics browser interpreter driver based on retrieved virtual graphics browser firmware volume payload.

Abstract: An information handling system is configured, during a pre-extensible firmware interface initialization phase of the information handling system, to learn capabilities of components of the information handling system, create a hand-off block for storage of a virtual graphical browser firmware volume payload, and store learned capabilities of the components of the information handling system in the hand-off block. During a driver execution environment phase, the information handling system may retrieve the learned capabilities of the components of the information handling system stored in the hand-off block, publish learned capabilities retrieved from the hand-off block, retrieve the virtual graphics browser firmware volume payload stored in the hand-off block, and dispatch a virtual graphics browser learning driver and a virtual graphics browser interpreter driver based on retrieved virtual graphics browser firmware volume payload.

Abstract: An information handling system is configured, during a pre-extensible firmware interface initialization phase of the information handling system, to learn capabilities of components of the information handling system, create a hand-off block for storage of a virtual graphical browser firmware volume payload, and store learned capabilities of the components of the information handling system in the hand-off block. During a driver execution environment phase, the information handling system may retrieve the learned capabilities of the components of the information handling system stored in the hand-off block, publish learned capabilities retrieved from the hand-off block, retrieve the virtual graphics browser firmware volume payload stored in the hand-off block, and dispatch a virtual graphics browser learning driver and a virtual graphics browser interpreter driver based on retrieved virtual graphics browser firmware volume payload.

Abstract: A pre-boot screen can be accessed remotely. A remote access BIOS module can be employed on a computing system to logically split a GPU into a local screen rendering part and a remote access part and to logically split GPU memory into a local screen memory region and a remote access memory region. The remote access part of the GPU can access a pre-boot screen that has been copied to the remote access memory region and create network packets with payloads containing the pre-boot screen. The remote access part can then cause the network packets to be transferred to a NIC for delivery to a remote computing system. A remote access application on the remote computing system can extract and display the pre-boot screen. The remote access application can relay any user input back to the remote access BIOS module which can then cause the user input to be implemented locally.

Abstract: An example device comprises a plurality of components and a BIOS includes a non-volatile memory having instructions stored thereon that are executable by a processor of the device to cause the BIOS to determine a component identification (ID) of a component of the plurality of components, and fetch a plurality of recall component IDs. The instructions also are to cause the BIOS to compare the determined component ID with the plurality of recall component IDs. In response to a correspondence between the determined component ID and one recall component ID of the plurality of component IDs, the BIOS is to transmit signals representing a prompt to place the component of the plurality of components in a safety mode. The instructions also cause the BIOS to receive signals in response to the prompt and, responsive to the received signals, disable the component of the plurality of components.