mlsanityData to 14 Oct 2026

Assume but Verify: Deductive Verification of Leaked Information in Concurrent Applications (Extended Version)

arXiv 2309.03442 ↗First posted 7 Sep 2023cs.CRcited by 1

Not on the map. Why?

Abstract (arXiv)

We consider the problem of specifying and proving the security of non-trivial, concurrent programs that intentionally leak information. We present a method that decomposes the problem into (a) proving that the program only leaks information it has declassified via assume annotations already widely used in deductive program verification; and (b) auditing the declassifications against a declarative security policy. We show how condition (a) can be enforced by an extension of the existing program logic SecCSL, and how (b) can be checked by proving a set of simple entailments. Part of the challenge is to define respective semantic soundness criteria and to formally connect these to the logic rules and policy audit. We support our methodology in an auto-active program verifier, which we apply to verify the implementations of various case study programs against a range of declassification policies.

Key facts. Cited by 1 paper in the map (data through 14 Oct 2026). First posted on arXiv 7 Sep 2023.

Builds on

No reference list yet.

Built on by

Cited by year (2026 to 14 Oct)

Citing papers per year: 2026: 1.

1 paper.