Abstract: A BIOS/OS key provisioning system includes an NVMe storage device coupled to a server device via a network. The server device includes an operating system engine and a BIOS engine. Subsequent to a current initialization of the server device and prior to an immediately subsequent initialization of the server device, the BIOS engine retrieves a key from a key storage subsystem and stores the key in a BIOS memory subsystem. When the BIOS engine receives a current key request that identifies the key from the operating system engine and determines that the key stored in the BIOS memory system has not previously been accessed subsequent to the current initialization and prior to the subsequent initialization, it provides the key from the BIOS memory subsystem to the operating system, and prevents the key from being provided from the BIOS memory subsystem in response to any subsequent key request.

Abstract: A secure Basic Input/Output System (BIOS)-enabled passthrough system includes a computing device having a computing device component, and a BIOS subsystem in the computing device that is coupled to the computing device component. The BIOS subsystem enables primary access to the computing device component to BIOS drivers. The BIOS subsystem may receive a secondary access session start request from a first BIOS driver to start a secondary access session to use secondary access to the computing device component, it retrieves a first BIOS driver identifier for the first BIOS driver based on the secondary access session start request, determines that the first BIOS driver identifier is a secondary-access-authorized BIOS driver identifier and, in response, begins the first secondary access session and may performs secondary access operation(s) on the computing device component in response to receiving secondary access command(s) from the first BIOS driver during the secondary access session.

Abstract: Methods and systems for managing data for startup purposes in a distributed system are disclosed. The distributed system may include any number of clients operably connected to a storage system via a connection fabric. By virtue of the connection topology, any of the clients may interact with the storage system to gain access to storage resources of the storage system. When a client is provided access to storage resources by the storage system, other clients may not be able to access the storage resources of the storage system.

Abstract: Methods and systems for managing data for startup purposes in a distributed system are disclosed. The distributed system may include any number of clients operably connected to a storage system via a connection fabric. By virtue of the connection topology, any of the clients may interact with the storage system to gain access to storage resources of the storage system. When a client is provided access to storage resources by the storage system, other clients may not be able to access the storage resources of the storage system.

Abstract: A network initialization monitoring system includes a host device coupled to a storage system and a monitoring system via a network, and including an initialization subsystem coupled to ports. During network initialization of the host device via the storage system, the initialization subsystem provides a first instance of a communication protocol for monitored port(s), and provides a second instance of the communication protocol for a monitoring port. During the network initialization of the host device via the storage system, the first instance of the communication protocol provided for each monitored port provides copies of network initialization communications transmitted via that monitored port and the network to the second instance of the communication protocol provided for the monitoring port, and the second instance of the communication protocol provided for the monitoring port provides the copies of the network initialization communications to the monitoring system.

Abstract: A BIOS/OS key provisioning system includes an NVMe storage device coupled to a server device via a network. The server device includes an operating system engine and a BIOS engine. Subsequent to a current initialization of the server device and prior to an immediately subsequent initialization of the server device, the BIOS engine retrieves a key from a key storage subsystem and stores the key in a BIOS memory subsystem. When the BIOS engine receives a current key request that identifies the key from the operating system engine and determines that the key stored in the BIOS memory system has not previously been accessed subsequent to the current initialization and prior to the subsequent initialization, it provides the key from the BIOS memory subsystem to the operating system, and prevents the key from being provided from the BIOS memory subsystem in response to any subsequent key request.

Abstract: A microcode update system includes at least one memory device having a code region and a data region, and a microcode update engine that receives a microcode update, and writes the microcode update to the data region of the at least one memory device. Subsequent to writing the microcode update to the data region of the at least one memory device, the microcode update engine utilizes initialization code in the code region of the at least one memory device to perform initialization operations. During a microcode update portion of the initialization operations, the microcode update engine identifies the microcode update in the data region of the at least one memory device, and performs microcode update operations using the microcode update in the data region of the at least one memory device.

Abstract: A microcode update system includes at least one memory device having a code region and a data region, and a microcode update engine that receives a microcode update, and writes the microcode update to the data region of the at least one memory device. Subsequent to writing the microcode update to the data region of the at least one memory device, the microcode update engine utilizes initialization code in the code region of the at least one memory device to perform initialization operations. During a microcode update portion of the initialization operations, the microcode update engine identifies the microcode update in the data region of the at least one memory device, and performs microcode update operations using the microcode update in the data region of the at least one memory device.

Abstract: A boot process security system includes a processing system including a plurality of registers, and at least one memory system that includes instructions that, when executed by the processing system, cause the processing system to provide a BIOS. During a Driver eXecution Environment (DXE) sub-process that is included in a boot process and that occurs prior to passing control of the boot process to any third-party drivers, the BIOS programs at least one of the plurality of registers in order to configure at least one secure subsystem. The BIOS then verifies, during the boot process, that the at least one secure subsystem has been configured to provide a predetermined configuration, and locks the at least one secure subsystem. The BIOS then confirms that the at least one secure subsystem has been locked prior to passing control of the boot process to any third-party drivers.

Abstract: A boot process security system includes a processing system including a plurality of registers, and at least one memory system that includes instructions that, when executed by the processing system, cause the processing system to provide a BIOS. During a Driver eXecution Environment (DXE) sub-process that is included in a boot process and that occurs prior to passing control of the boot process to any third-party drivers, the BIOS programs at least one of the plurality of registers in order to configure at least one secure subsystem. The BIOS then verifies, during the boot process, that the at least one secure subsystem has been configured to provide a predetermined configuration, and locks the at least one secure subsystem. The BIOS then confirms that the at least one secure subsystem has been locked prior to passing control of the boot process to any third-party drivers.