Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Operations

10/21/2019
04:15 PM
Connect Directly
Twitter
LinkedIn
Google+
RSS
E-Mail
50%
50%

Microsoft Aims to Block Firmware Attacks with New Secured-Core PCs

Partnerships with Intel, Qualcomm, and AMD will bring a new layer of device security that alters the boot process to detect firmware compromise.

Microsoft is teaming up with Windows device manufacturers to tighten firmware security in a new initiative called Secure-Core PCs, which are built to defend against firmware-level attacks.

Its announcement arrives as attackers take greater aim at firmware, the level of software that is closest to the hardware and controls the functions of devices and systems. Firmware is an appealing target because it has a higher level of access and privilege than the operating system kernel and hypervisor. The National Vulnerabilities Database reports 414 firmware bugs have been reported in 2019, compared with 476 in 2018, 401 in 2017, and seven in 2016.

"Firmware is the most privileged software running on the device," says David Weston, partner director of OS security at Microsoft. "You can basically do anything." Because firmware isn't always centrally updated, he continues, it's more likely to be outdated and vulnerable.

When firmware vulnerabilities are exploited by sophisticated groups such as Strontium/APT28, which has been spotted using this type of attack, the infection is difficult to detect and remove. Firmware attacks can weaken security functionalities like Windows' Secure Boot; because many endpoint detection and response (EDR) tools have limited visibility at the firmware level, it's easier for attackers to slip past them. If the firmware is assumed breached, the security of the whole machine is potentially at risk.

Secure Boot is a feature designed to make sure that when a device boots up, it's only using software trusted by the OEM. When a computer starts, the firmware checks the signature of each component in the boot software. If the signatures are valid, the machine starts running. Secure Boot assumes firmware can be trusted – a major problem if it has been compromised. On its own, the secure measure doesn't protect against malware that exploits firmware bugs.

New security requirements in Secured-Core PCs are intended to help users boot securely, protect devices from firmware flaws, and prevent unauthorized access to devices and data. Secured-Core PCs remove the need to trust firmware as part of the bootup process. Instead, they place the root of trust at the CPU level with new chipsets from AMD, Intel, and Qualcomm.

"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," Weston writes in a blog post on today's news. If the CPU decides the firmware was compromised, it can transmit a signal to indicate foul play.

This limits the trust placed in firmware, protects against firmware attacks, and maintains the integrity of the virtualization-based security (VBS) functionality, implemented by the hypervisor. Securing VBS is critical, Weston says, because it's used in key OS security capabilities like Windows Defender Credential Guard and Hypervisor-protected Code Integrity (HVCI), which ensures a code integrity policy is enforced and kernel code is verified.

The extra layer of security will arrive in new Windows 10 devices, starting with the Surface Pro X. Other devices will follow from Dell, HP, Lenovo, Panasonic, and Dynabook. Most of the Secured-Core devices launching are laptops, says Weston, with the exception of Surface Pro X.

While anyone can buy a Secured-Core PC – a sticker will inform them whether it meets the security requirements – Weston notes these are specifically designed for people who work in verticals like government or financial services, where sensitive information is often targeted.

"If you think about who is likely to suffer a really advanced, targeted firmware attack, it's going to be people in those highly targeted verticals," he adds.

Related Content:

This free, all-day online conference offers a look at the latest tools, strategies, and best practices for protecting your organization’s most sensitive data. Click for more information and, to register, here.

Kelly Sheridan is the Staff Editor at Dark Reading, where she focuses on cybersecurity news and analysis. She is a business technology journalist who previously reported for InformationWeek, where she covered Microsoft, and Insurance & Technology, where she covered financial ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Navigating Security in the Cloud
Diya Jolly, Chief Product Officer, Okta,  12/4/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Navigating the Deluge of Security Data
In this Tech Digest, Dark Reading shares the experiences of some top security practitioners as they navigate volumes of security data. We examine some examples of how enterprises can cull this data to find the clues they need.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-16772
PUBLISHED: 2019-12-07
The serialize-to-js NPM package before version 3.0.1 is vulnerable to Cross-site Scripting (XSS). It does not properly mitigate against unsafe characters in serialized regular expressions. This vulnerability is not affected on Node.js environment since Node.js's implementation of RegExp.prototype.to...
CVE-2019-9464
PUBLISHED: 2019-12-06
In various functions of RecentLocationApps.java, DevicePolicyManagerService.java, and RecognitionService.java, there is an incorrect warning indicating an app accessed the user's location. This could dissolve the trust in the platform's permission system, with no additional execution privileges need...
CVE-2019-2220
PUBLISHED: 2019-12-06
In checkOperation of AppOpsService.java, there is a possible bypass of user interaction requirements due to mishandling application suspend. This could lead to local information disclosure no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVers...
CVE-2019-2221
PUBLISHED: 2019-12-06
In hasActivityInVisibleTask of WindowProcessController.java there?s a possible bypass of user interaction requirements due to incorrect handling of top activities in INITIALIZING state. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction ...
CVE-2019-2222
PUBLISHED: 2019-12-06
n ihevcd_parse_slice_data of ihevcd_parse_slice.c, there is a possible out of bounds write due to a missing bounds check. This could lead to remote code execution with no additional execution privileges needed. User interaction is needed for exploitation.Product: AndroidVersions: Android-8.0 Android...