Widely used DNA sequencer still doesn’t enforce Secure Boot
In 2012, an industry-wide coalition of hardware and software makers adopted Secure Boot to protect Windows devices against the threat of malware that could infect the BIOS and, later, its predecessor the UEFI, the firmware that loaded the operating system each time a computer booted up.
Firmware-dwelling malware raises the specter of malware that infects the devices before the operating system even loads, each time they boot up. From there, it can remain immune to detection and removal. Secure Boot uses public-key cryptography to block the loading of any code that isn’t signed with a pre-approved digital signature.
2018 calling for its BIOS
Since 2016, Microsoft has required all Windows devices to include a strong trusted platform module that enforces Secure Boot. To this day organizations widely regard Secure Boot as an important, if not essential, foundation of trust in securing devices in some of the most critical environments.
