A New Doctrine for Hardware Security

07/18/2020
by   Adam Hastings, et al.
0

In this paper, we promote the idea that recent woes in hardware security are not because of a lack of technical solutions but rather because market forces and incentives prevent those with the ability to fix problems from doing so. At the root of the problem is the fact that hardware security comes at a cost; Present issues in hardware security can be seen as the result of the players in the game of hardware security finding ways of avoiding paying this cost. We formulate this idea into a doctrine of security, namely the Doctrine of Shared Burdens. Three cases studies—Rowhammer, Spectre, and Meltdown—are interpreted though the lens of this doctrine. Our doctrine illuminates why these problems and exist and what can be done about them.

READ FULL TEXT

page 1

page 2

page 3

page 4

research
11/12/2016

Can Broken Multicore Hardware be Mended?

A suggestion is made for mending multicore hardware, which has been diag...
research
01/02/2018

Validation of Hardware Security and Trust: A Survey

With ever advancing in digital system, security has been emerged as a ma...
research
08/24/2020

Towards Flexible Security Testing of OT Devices

In the factory of the future traditional and formerly isolated Operation...
research
04/12/2023

Information Flow Coverage Metrics for Hardware Security Verification

Security graphs model attacks, defenses, mitigations, and vulnerabilitie...
research
06/20/2019

Defensive Routing: a Preventive Layout-Level Defense Against Untrusted Foundries

Since the inception of the integrated circuit (IC), the size of the tran...
research
10/19/2021

Holistic Hardware Security Assessment Framework: A Microarchitectural Perspective

Our goal is to enable holistic hardware security evaluation from the mic...
research
11/26/2020

Attacks on Lightweight Hardware-Based Security Primitives

In today's digital age, the ease of data collection, transfer, and stora...

Please sign up or login with your details

Forgot password? Click here to reset