Security and Root of Trust

April 20, 2015, Trusted Compute Group, San Francisco—Paul Roberts from the Security Ledger talked with Amy Nelson from Dell and David Bossio from Microsoft about implementing the trusted processor modules (TPM) into products. Although the technology has been around for a while, the implementations and adoptions are still nascent.

Use at Dell and programming different versions?
Nelson acknowledged that implementation was hard at the start, but is getting easier as the hardware technologies improve. The main issues are at the customer sites and are related to basic operations like how to start and ensuring functionality. The latest version, TPM 2, has increased the overall functionality and the OS and apps now can acknowledge its existence. Unfortunately, the TPM 2 has a different command set, so it is not back compatible with older versions. The software support in the OS, apps, and firmware are all getting better.

In Windows?
Bossio noted early support for TPM and Bit Locker in Windows 7 and 8. The latest versions are getting better and now check on initial boot. They added more functionality in 8.1 to include smart card functions and two factor compliance assurance. The smart card functions because their enterprise users are seeing increased use of smart cards for more functions such as building access and computer authorization. Unfortunately, people leave their cards in machines, in bags, etc. and cause large issues with access and IT support for password recovery. With a TPM, IT can embed functions into the machine to reduce costs for support and replacements.

Dell partners?
Nelson declared that TPM functions are moving into the apps. The changes to the machine configurations help to harden or protect encryption keys. Some of the drive for adoption is from regulations. In the US, regulations like HIPPA and Sar-Box need FIT certification, which is augmented with the TPM.

Regulatory compliance versus real threats?
Bossio stated that the hardware protections in TPM improve Bit Locker smart card functions. These improvements help to protect against root kit attacks by ensuring secure and trusted boot. Earlier compliance levels allowed network access before authorization completion. Expect to see even more access and leverage of TPM in Windows 10.

Now, Win 10 will provide full TPM 2.0 support with provable identification for cloud services, which allows administrators to tie secrets to a machine for both PCs and phones. The TPM addresses password problems with a hardware-verified system and some second authorization.

Xbox as an example of a known device and the cloud?
Bossio commented that the fundamental hardware root of trust in the Xbox is integrated into the ASIC. The TPM provides for authentication and boot before any connections to the network. The system id de-virused before boot and connections. In the Xbox, malware is stopped before boot or any operations and the system also protects content and IP. The advent of streaming video, which the studios want, creates an issue with monetization, so the TPM assures that the key to the content is protected by the device.

Use cases and data at rest?
Nelson responded that data at rest is a big issue, but it depends on the company. The government regulations and concerns about the company reputation drive some companies to want assurance of protections. There are many use cases. For example, a laptop with crypto on the drive can assure protection even in cases where the devices was left on the seat of a cab.

Global export of TPM?
Nelson stated that TPM works with all geographies. The ISO standard for cryptography certifications allows for TPM hardware and allows for geography-specific TPM.

TPM in virtual machines?
Nelson acknowledged that this was very hard in version 1.2, but 2.0 addresses many issues with a library of functions.
Bossio added that Win 10 will integrate hypervisor use cases.

Datacenter role in virtual machines?
Bossio declared that Win 10 will provide access control via virtual TPM and Bit Locker containers.
Nelson stated that to the tools exist for VM and virtual TPM.

More end points with IoT?
Nelson responded that TPM and its secure boot will help. A lot of Linux implementations support TPM, so a user can use TPM in IoT. Developers need to emphasize the best practices management for IoT functions. All of the developments should strive to meet government standards for protection and develop a base level for root of trust.
Bossio suggested that the users need to get all devices to a common root of trust for any IoT device. Unfortunately, the low cost devices may not support TPM, so developers need to consider integrating the function into their ASIC.

Secure BIOS, boot, cryptography? How to change practices in the enterprise?
Bosssio opined that the added costs for TPM are less than the costs of a data loss.
Nelson declared that all of t heir commercial machines have TPM and the increased volumes reduce costs and increase adoption. Consumers are not adopting the technology, but will once the technology is transparent to the user. tPM protects the user credentials and encryption keys.

TPM depends on the rest of the system being secure, what about discrete devices?
Nelson answered that TPM has a process system to verify all components and can be embedded into other ICs. However, it is very hard to integrate in the CPU because those devices are too complex. Instead, it is better to verify all the existing resources as trusted before allowing CPU access. There is also the issue of locality, most are at level 0 and privileges change from level 0-5. There are fewer problems if you verify resources before use at each level.
Bossio added that the cloud forces you to decide what you trust, but something has to be the starting point.

HDD with a virus in the firmware?
Bossio said that it is possible to use a secure update process.
Nelson recognized this issue as a problem and is working on it. Using verified updates and a certified drive manager with TPM allows IT to focus on the host.