![]() ![]() Also, discussed will be the required UEFI interfaces for the embedded space when the separation of the device and OS development is desired. This session will discuss the ARM-related interfaces defined in the latest UEFI and ACPI specifications, the requirements of the UEFI and ACPI interfaces for the SBBR Specification, and the use of UEFI SCT and FWTS in the SBBR compliance test. This session focuses on four common software SMI vulnerabilities and how to change your UEFI firmware and applications to avoid them.Īdvances of UEFI Technologies in ARM Systems (ARM) ![]() ![]() Heavy customization, tight deadlines and poor code implementation can accidentally allow malware to abuse the power of SMM. Device manufacturers customize UEFI firmware using new runtime interfaces that are implemented using software SMIs. ![]() Strategies for Stronger Software SMI Security in UEFI Firmware (Insyde)Īvoid design errors and software coding pitfalls when implementing SMI handlers. UEFI Firmware – Security Concerns and Best Practices (Phoenix) This session discusses “last mile” gaps for 16-bit compatibility and identifies UEFI capabilities that the industry can promote as alternatives, including HTTPS Boot, OS Recovery, and Signed Capsule Update. Intel has identified maintaining compatibility as an issue for platform security and validation costs, and plans to eliminate legacy BIOS elements in our 2020 data center platforms. These legacy corner cases are a barrier to completing the transition to modern firmware standards. While UEFI has become a dominant standard since its introduction in 2005, many use cases still rely on compatibility with PC/AT Legacy BIOS. “Last Mile” Barriers to Removing Legacy BIOS (Intel) The presentation abstracts are below, see the full itenary for speaker bios. The Fall UEFI Plugfest is happening, a week of interop testing with UEFI vendors, along with some presentations. Insyde Software security updates for Windows 10 It is a shame that the spreadsheet doesn’t have a column with more useful info, eg: URL to the vendor’s spec, perhaps which HW/OS it is valid for, which version of ACPI it requires, flag if table has FWTS test, license of vendor’s spec (eg, click-through EULA required for some ARM/MSFT/TCG docs), etc. Here’s the list of new ACPI specs for 2017 (so far), 2 new entries in November, first update since Summer:įor the 2 new entries, I can’t find any data on what their ACPI tables do, nor where their specs are: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |