Microsoft’s ‘secured-core PC initiative’ aims to protect Windows 10 machines from firmware attacks

Microsoft plans to put more of an emphasis on the security of its Windows users moving forward, via the newly-announced “Secured-core PC” initiative. The initiative aims to offer Windows customers a better form of protection against “targeted firmware” attacks.

These attacks, according to Microsoft, are becoming more common in recent years. This is largely due to the ever-improving security features built into operating systems and their “connected services.” Better security means more challenges for hackers to overcome, and reduced incentive for them to attempt to break into a system using software vulnerabilities; thus leading them to focus on firmware instead.

To address the growing threat that firmware-based attacks present, Microsoft has partnered up with various PC manufacturing and silicon partners to produce the secured-core PC defense. This defense’s primary component is “System Guard Secure Launch,” a device requirement that protects a PC’s boot process from firmware attacks.

Microsoft’s full explanation of how this concept works is quite technical in nature, but here’s a summary, in the company’s own words:

System Guard uses the Dynamic Root of Trust for Measurement (DRTM) capabilities that are built into the latest silicon from AMD, Intel, and Qualcomm to enable the system to leverage firmware to start the hardware and then shortly after re-initialize the system into a trusted state by using the OS boot loader and processor capabilities to send the system down a well-known and verifiable code path.

Put simply, Secure Launch acts as a sort of gatekeeper between system start-up (or, more specifically, BIOS/UEFI initialization) and actual Windows 10 operation. Using the power of newer CPUs, Secure Launch can ensure everything is running as planned, and no malicious code is attempting to latch itself onto your system before log-in.

Source : www.techspot.com

Leave a Reply

Your email address will not be published. Required fields are marked *