Verified Secure Compilation for Mixed-Sensitivity Concurrent Programs
Robert Sison (1, 2, 3), Toby Murray (1) ((1) University of, Melbourne, (2) CSIRO's Data61, (3) UNSW Sydney)

TL;DR
This paper presents a verified compilation approach that ensures noninterference security properties are preserved from source code to assembly in mixed-sensitivity concurrent programs, addressing challenges of concurrency and shared memory.
Contribution
It introduces new refinement notions that support security-preserving compilation for concurrent programs with mixed sensitivities, verified using Isabelle/HOL.
Findings
Successfully verified a compiler preserving noninterference for concurrent programs.
Applied the approach to a real-world mixed-sensitivity program, ensuring security at assembly level.
Demonstrated the feasibility of security-preserving compilation in concurrent, shared-memory settings.
Abstract
Proving only over source code that programs do not leak sensitive data leaves a gap between reasoning and reality that can only be filled by accounting for the behaviour of the compiler. Furthermore, software does not always have the luxury of limiting itself to single-threaded computation with resources statically dedicated to each user to ensure the confidentiality of their data. This results in mixed-sensitivity concurrent programs, which might reuse memory shared between their threads to hold data of different sensitivity levels at different times; for such programs, a compiler must preserve the value-dependent coordination of such mixed-sensitivity reuse despite the impact of concurrency. Here we demonstrate, using Isabelle/HOL, that it is feasible to verify that a compiler preserves noninterference, the strictest kind of confidentiality property, for mixed-sensitivity concurrent…
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
