The bibliographic entry was discovered and compiled by a machine, and published without a person checking it against the publication. The publication itself is the authors' own work — this badge says nothing about it.

A Generic Framework to Develop and Verify Security Mechanisms at the Microarchitectural Level: Application to Control-Flow Integrity

The work

AuthorsMatthieu Baty; Pierre Wilke; Guillaume Hiet; Arnaud Fontaine; Alix Trieu
Editors
Typemisc
Year2023
Citekeybaty2023generic

Where it appeared

Published inProceedings - Computer Security Foundations Workshop/Proceedings
PublisherInstitute of Electrical and Electronics Engineers
Pages372--387

From OpenAlex, which stores abstracts as an index of words and their positions: what is shown is rebuilt from that, and reads fluently whether or not it is what the author wrote.

Abstract

In recent years, the disclosure of several significant security vulnerabilities has revealed the trust put in some presumed security properties of commonplace hardware to be misplaced. We propose to design hardware systems with security mechanisms, together with a formal statement of the security properties obtained, and a machine-checked proof that the hardware security mechanisms indeed implement the sought-for security property. Formally proving security properties about hardware systems might seem prohibitively complex and expensive. In this paper, we tackle this concern by designing a realistic and accessible methodology on top of the Kôlka Hardware Description Language for specifying and proving security properties during hardware development. Our methodology is centered around a verified compiler from high-level and inefficient to work with Kôlka models to an equivalent lower-level representation, where side effects are made explicit and reasoning is convenient. We apply this methodology to a concrete example: the formal specification and implementation of a shadow stack mechanism on an RV32I processor. We prove that this security mechanism is correct, i.e., any illegal modification of a return address does indeed result in the termination of the whole system. Furthermore, we show that this modification of the processor does not impact its behaviour in other, unexpected ways.

How it got here

How it got hereagent via openalex
Added2026-10-26 03:46 UTC
Not denied bya person 2026-10-29 17:12 UTC

Cite it as

@misc{baty2023generic,
  title        = {A Generic Framework to Develop and Verify Security Mechanisms at the Microarchitectural Level: Application to Control-Flow Integrity},
  author       = {Matthieu Baty and Pierre Wilke and Guillaume Hiet and Arnaud Fontaine and Alix Trieu},
  year         = {2023},
  journal      = {Proceedings - Computer Security Foundations Workshop/Proceedings},
  publisher    = {Institute of Electrical and Electronics Engineers},
  pages        = {372--387},
  doi          = {10.1109/csf57540.2023.00029},
}

This record lives at https://refs.drheap.org/baty2023generic/ and will keep doing so.