Abstract: Control of a prompt for a credential to unlock a computer-readable storage device is provided. Some embodiments permit identifying a component that encrypted the computer-readable storage device and, depending on the identified component, prompting for such a credential. One embodiment can determine that a firmware encrypted the computer-readable storage device and can prompt for a password, for example, to unlock the computer-readable storage device during a boot-up process performed by the firmware. Other embodiments can determine that an operating system encrypted the computer-readable storage device, and can avoid the presentation of a prompt for a password, for example, during a boot-up process performed by the firmware. The computer-readable storage device can be a self-encrypting drive (SED) or another type of disk drive.

Abstract: A computing device includes a processor, a volatile memory, and a non-volatile memory. The computing device receives a firmware update that includes updated firmware runtime components, such as updated runtime interrupt handlers (e.g. SMI handlers). The computing device stores the updated firmware runtime components in the volatile memory (e.g. RAM) of the device. The computing device also causes the updated firmware runtime components stored in the volatile memory to be used during the runtime of the computing device instead of one or more other firmware runtime components previously stored in the volatile memory. For example, the contents of one or more interrupt routing tables can be adjusted such that updated runtime interrupt handlers stored in volatile memory are used instead of previously installed and potentially insecure runtime interrupt handlers. On a subsequent reboot of the computing device, updated firmware runtime components stored in the non-volatile memory will be utilized.

Abstract: Technologies are disclosed herein for saving data, such as state data, during boot-up of a computer system, such that that data may be retrieved at a later time and restored to its original locations. The data that is stored may be from a shared partition of system memory that is accessible by both firmware services and runtime services, as enabled by an operating system and/or applications running on the computer system. The data may be stored in a partition of the system memory that is only accessible by firmware. In some embodiments, due to the data of the shared partition of the system memory being restored, some functions of the boot-up may not be repeated prior to loading a second operating system on the computer system.

Abstract: Technologies are disclosed herein for blocking access to some firmware variables during runtime. These firmware variables may be disallowed from runtime access (e.g., read/write access), by placing an indication of the firmware variables on a runtime blocklist. Upon completion of booting, runtime firmware services may access the runtime blocklist to determine if a firmware variable is to be accessed during runtime. In some cases, a firmware variable may be disallowed from runtime access by inclusion in the runtime blocklist, even if that firmware variable has an attribute that indicates that it is runtime accessible. The runtime blocklist may be generated based at least in part on indications of the firmware variables to be blocked during runtime. Additionally, runtime accessible firmware variables may be exposed to higher-level software, such as an O/S, if the firmware variables are not included in the runtime blocklist.

Abstract: A method, system, and computer-readable medium for expediting initialization of a computing system are provided. According to one aspect of the invention, a computer-readable medium is provided having computer executable instructions stored thereon, which when executed by a computer, cause the computer to cache a portion of a firmware to a cache prior to initialization of a main memory. In particular, the computer-executable instructions cause the central processing unit of the computer to cache a range of memory addresses corresponding to the location of the portion of the firmware stored in a computer storage media to the cache prior to the initialization of the main memory. The firmware may be a BIOS and/or EFI firmware. The computer-executable instructions then cause the computer to execute the portion of the firmware from the cache until the main memory is initialized.

Abstract: A system and method for processing partially unstructured data relating to a financial security. The system and method resolve first- and second-identifying data from the partially unstructured data and determine whether a security is defined by the first-identifying data and the second-identifying data. Additionally, the system and method resolve trade information relating to the security identifier from the partially unstructured data. If a security is defined by the resolved identifying data, a security identifier representing the defined security, along with the trade information relating to the defined security, are output.

Abstract: A method and a system for allowing computer-executable applications to efficiently and securely obtain credentials required to access data from a protected Web service utilizes an ID token. The ID token is associated with an IP address of a user's computer, and is validated before providing the credentials to the user's computer.

Abstract: A system and method for processing partially unstructured data relating to a financial security. The system and method resolve first- and second-identifying data from the partially unstructured data and determine whether a security is defined by the first-identifying data and the second-identifying data. Additionally, the system and method resolve trade information relating to the security identifier from the partially unstructured data. If a security is defined by the resolved identifying data, a security identifier representing the defined security, along with the trade information relating to the defined security, are output.

Abstract: The control method names used in the advanced configuration and power management interface (ACPI) are modified to add control flexibility to the interface. The interface is between a basic programming system such as BIOS and an operating system, and the modification of the control method names controls the enabling of the control methods associated with control method names. During setup a user dialogs with the computing system and select settings for configuration and power management features for the system. The selected settings indicate the features corresponding to control method names to be modified. The control method names to be modified are searched for based upon the selected settings. The control method names found by the search based on the settings are modified so that the operating system will not recognize the control method names and the associated control method will not be enabled.