Abstract: Systems and methods for providing a storage extension system and method for secure and seamless access by various boot architectures are described. In some embodiments, an Information Handling System (IHS) may include a processor and a BIOS coupled to the processor, the BIOS having program instructions that, upon execution, cause the IHS to receive a request to access a bios storage region of the IHS from a driver, determine whether the device associated with the driver is a platform boot device such that when the boot device is a platform boot device, facilitate access to a native bios storage region of the bios storage region by the driver, and when the boot device is not a platform boot device, facilitate access to an extended bios storage region of the bios storage region by the driver.

Abstract: A method for remediating an information handling system, wherein the method includes running a fault monitoring module during a runtime of the information handling system to detect field fault conditions, collect field fault data associated with field fault conditions, upload the field fault data to a remediation engine, and receive remediation objects from the remediation engine. The method further includes detecting a fault condition, receiving a remediation object corresponding to the fault condition wherein the remediating object includes one or more remediation templates, and providing notice of the fault condition to a remediation interface. The remediation interface is configured to boot the information handling system into a remediation mode and load and execute the remediation templates to resolve the field faults.

Abstract: Disclosed subject matter enables a recovery and resume of secure platform services based on indicator of attack for the UEFI boot path and UEFI drivers for any access to storage or network medium. Disclosed methods may employ an unsupervised learning model, based on information referred to herein as Indicator of Attack (IOA) information, and create a unique resilient BIOS access for UEFI drivers, file system, media and network. Disclosed teachings enable secure services for access to UEFI drivers, file systems, media, and network using a dynamic resilient layer to handle IOA. Dynamic methods to create runtime metadata for file system logical blocks for OEM nested file system partition and pre boot OEM authentication are also disclosed. Disclosed teachings support a UEFI file system interface that implements a runtime remap method for OEM-provided drivers.

Abstract: A system for network management comprising a silicon management system operating on a processor that causes the processor to load one or more algorithms stored in a non-transient data memory to cause the processor to identify a version for a plurality of silicon data processing devices and to implement an update to one or more of the silicon data processing devices, a chipset management system operating on a processor that causes the processor to load one or more algorithms stored in a non-transient data memory to cause the processor to identify a version for a plurality of chipsets, each chipset associated with one of the silicon data processing devices and to implement an update to one or more of the chipsets and a boot system configured to cause a system associated with the updated silicon data processing devices and the updated chipsets to reboot.

Abstract: An information handling system includes a memory and a processor. The memory stores a current basic input/output system (BIOS) firmware image. During a regular boot mode of the information handling, the processor creates a first set of tables associated with the current BIOS firmware image, stores the first tables to the memory, and receives a BIOS firmware update image. During a BIOS update boot mode of the information handling system, the processor creates a second plurality of tables associated with the BIOS firmware update image, and compares the first and second tables. In response to a difference being determined between the first and second tables, the processor aborts the BIOS update boot mode and generate an error log.

Abstract: An information handling system determines a difference between a first set of initialization information and a second set of initialization information during a pre-extensible firmware interface initialization phase of a boot process that is based on a first basic input/output system (BIOS), wherein the first set of initialization information is associated with the first BIOS and the second set of initialization information is associated with a second BIOS. The system also creates and publishes a hand-off block that includes an entry which describes the difference between the first set of initialization information and the second set of initialization information. The system parses the hand-off block during a driver execution environment phase to determine the difference between the first set of initialization information and the second set of initialization information, wherein the hand-off block is passed from the pre-extensible firmware interface initialization phase of the boot process.

Abstract: An information handling system may include a processor and first non-transitory computer-readable media communicatively coupled to the processor and having stored thereon a basic input/output system (BIOS) core comprising BIOS core firmware sufficient to execute features of a BIOS of the information handling system to a particular portion of BIOS execution and an extension agent. The extension agent may be configured to identify and enumerate a firmware volume of a second non-transitory computer-readable media communicatively coupled to the processor and having stored thereon a BIOS extension comprising BIOS extension firmware for executing completion of BIOS execution from the particular portion of BIOS execution and in response to unavailability of the firmware volume of the second non-transitory computer-readable media, failover to and recover the BIOS extension from extended firmware information stored on a networked storage resource communicatively coupled to the information handling system.

Abstract: An information handling system may determine an allocated space in an option read-only memory (ROM), and store a firmware module in the allocated space in the option ROM. The system may load basic input/output system firmware from a serial peripheral interface flash memory with the firmware module from the allocated space in the option ROM.

Abstract: A disclosed method installs an I/O trap protocol to provide an authentication callback function for handling I/O trap events. I/O trap events may include write operations accessing any of one or more identified I/O addresses. An I/O trap event may be registered with the authentication callback function for each of one or more identified I/O addresses. Original values of data may be stored in a memory resource. Any occurrences of an I/O trap event triggers the authentication callback function to perform I/O trap operations. The I/O trap operations may include determining whether the I/O trap event is associated with an approved driver and, if not, restoring data stored at the identified I/O address to an original value. Installing the I/O trap protocol may include installing the I/O trap protocol during a system management mode (SMM) phase of a UEFI boot sequence.

Abstract: An information handling system may include a processor and first non-transitory computer-readable media communicatively coupled to the processor and having stored thereon a basic input/output system (BIOS) core comprising BIOS core firmware sufficient to execute features of a BIOS of the information handling system to a particular portion of BIOS execution and an extension agent. The extension agent may be configured to identify and enumerate a firmware volume of a second non-transitory computer-readable media communicatively coupled to the processor and having stored thereon a BIOS extension comprising BIOS extension firmware for executing completion of BIOS execution from the particular portion of BIOS execution and in response to unavailability of the firmware volume of the second non-transitory computer-readable media, failover to and recover the BIOS extension from extended firmware information stored on a networked storage resource communicatively coupled to the information handling system.

Abstract: Systems and methods for providing a storage extension system and method for secure and seamless access by various boot architectures are described. In some embodiments, an Information Handling System (IHS) may include a processor and a BIOS coupled to the processor, the BIOS having program instructions that, upon execution, cause the IHS to receive a request to access a bios storage region of the IHS from a driver, determine whether the device associated with the driver is a platform boot device such that when the boot device is a platform boot device, facilitate access to a native bios storage region of the bios storage region by the driver, and when the boot device is not a platform boot device, facilitate access to an extended bios storage region of the bios storage region by the driver.

Abstract: An information handling system may include a processor and first non-transitory computer-readable media communicatively coupled to the processor and having stored thereon a basic input/output system (BIOS) core comprising BIOS core firmware sufficient to execute features of a BIOS of the information handling system to a particular portion of BIOS execution and an extension agent configured to identify and enumerate a firmware volume of a second non-transitory computer-readable media communicatively coupled to the processor and having stored thereon a BIOS extension comprising BIOS extension firmware for executing completion of BIOS execution from the particular portion of BIOS execution.

Abstract: An information handling system may detect an exception, create a hand-off block in an NVMe boot partition in an NVMe device during a pre-extensible firmware interface phase of a boot process, and update the hand-off block with information associated with the exception. The system may also load an exception table to the NVMe boot partition, wherein the exception table includes an index associated with the exception that is mapped to a vector associated with an exception handler, and load the exception handler to the NVMe boot partition, wherein the exception handler resolves the exception.

Abstract: An information handling system determines a difference between a first set of initialization information and a second set of initialization information during a pre-extensible firmware interface initialization phase of a boot process that is based on a first basic input/output system (BIOS), wherein the first set of initialization information is associated with the first BIOS and the second set of initialization information is associated with a second BIOS. The system also creates and publishes a hand-off block that includes an entry which describes the difference between the first set of initialization information and the second set of initialization information. The system parses the hand-off block during a driver execution environment phase to determine the difference between the first set of initialization information and the second set of initialization information, wherein the hand-off block is passed from the pre-extensible firmware interface initialization phase of the boot process.

Abstract: An information handling system may detect an exception, create a hand-off block in an NVMe boot partition in an NVMe device during a pre-extensible firmware interface phase of a boot process, and update the hand-off block with information associated with the exception. The system may also load an exception table to the NVMe boot partition, wherein the exception table includes an index associated with the exception that is mapped to a vector associated with an exception handler, and load the exception handler to the NVMe boot partition, wherein the exception handler resolves the exception.

Abstract: An information handling system may include a processor and a basic input/output system communicatively coupled to the processor and comprising a program of executable instructions configured to determine a context associated with a current boot session of the information handling system and based on user boot history stored during one or more previous boot sessions of the information handling system and the context, load one or more network drivers necessary to boot the information handling system in accordance with the context.

Abstract: A system for controlling a processor, comprising a processor configured to load one or more instructions into a register for execution, a non-volatile memory coupled to the processor and configured to store data in a format that can be read by the processor and a description file stored in the non-volatile memory, the description file further comprising a plurality of information files, wherein each information file includes two or more types of predetermined data.

Abstract: A capsule-based firmware update process is provided. After an operating system has provided a firmware update in the form of a capsule and the computing system is rebooted, a module can be loaded to locate a memory subsystem separate from the system memory. The module can initialize the separate memory subsystem and then identify a contiguous block of memory within the separate memory subsystem. The module can then cause the capsule to be coalesced from the system memory into the separate memory subsystem. Once the capsule is coalesced into the separate memory subsystem and the system memory is registered, the module can cause the coalesced capsule to be copied back into system memory where it can be accessed by other components that are subsequently loaded during the boot process.

Abstract: A system for controlling a processor, comprising a processor configured to load one or more instructions into a register for execution, a non-volatile memory coupled to the processor and configured to store data in a format that can be read by the processor and a description file stored in the non-volatile memory, the description file further comprising a plurality of information files, wherein each information file includes two or more types of predetermined data.

Abstract: A method for secure data communications using an insecure protocol, comprising generating a data message at a data processor client. Adding a security key to the data message using the data processor client. Transmitting the data message to a remote data processor receiver over a data network. Determining whether the data message is authentic at the remote data processor receiver. Automatically responding to the data message with a location where additional data can be obtained from the remote data processor receiver if it is determined by the remote data processor receiver that the data message is authentic.