We use a few cookies

Essential cookies keep the library working. With your permission, we'd also like to use analytics to see what's useful and improve the experience. Read our Privacy Policy or Cookie Policy.

Skip to main content
Home/e-Resources/Cyber Security/Contract-Aware Secure Compilation
PeriodicalsCyber Security

Contract-Aware Secure Compilation

arXiv2020

Checking your access to this record.

Abstract & Overview

Microarchitectural attacks exploit the abstraction gap between the Instruction Set Architecture (ISA) and how instructions are actually executed by processors to compromise the confidentiality and integrity of a system. To secure systems against microarchitectural attacks, programmers need to reason about and program against these microarchitectural side-effects. However, we cannot -- and should not -- expect programmers to manually tailor programs for specific processors and their security guarantees. Instead, we could rely on compilers (and the secure compilation community), as they can play a prominent role in bridging this gap: compilers should target specific processors microarchitectural security guarantees and they should leverage these guarantees to produce secure code. To achieve this, we outline the idea of Contract-Aware Secure COmpilation (CASCO) where compilers are parametric with respect to a hardware/software security-contract, an abstraction capturing a processor's security guarantees. That is, compilers will automatically leverage the guarantees formalized in the contract to ensure that program-level security properties are preserved at microarchitectural level.

Cite this record

Marco Guarnieri, Marco Patrignani (2020). Contract-Aware Secure Compilation. arXiv. https://library.shubhaarti.in/content/22759f1f-3c65-4be0-9aae-98e6bb9d72f1

Copy in another style

Guarnieri, M., & Patrignani, M. (2020). Contract-Aware Secure Compilation. arXiv. https://library.shubhaarti.in/content/22759f1f-3c65-4be0-9aae-98e6bb9d72f1
Author names are used as deposited, so check their order before you submit.

Metadata is harvested from open-access indexes and can be incomplete. Check a citation against the published version before relying on it — see our open access & attribution policy.