How We Built Cedar: A Verification-Guided Approach

This paper presents verification-guided development (VGD), a software engineering process we used to build Cedar, a new policy language for expressive, fast, safe, and analyzable authorization. Developing a system with VGD involves writing an executable model of the system and mechanically proving p...

Full description

Saved in:
Bibliographic Details
Published inarXiv.org
Main Authors Disselkoen, Craig, Eline, Aaron, He, Shaobo, Headley, Kyle, Hicks, Michael, Hietala, Kesha, Kastner, John, Mamat, Anwar, McCutchen, Matt, Rungta, Neha, Shah, Bhakti, Torlak, Emina, Wells, Andrew
Format Paper
LanguageEnglish
Published Ithaca Cornell University Library, arXiv.org 01.07.2024
Subjects
Software engineering
Verification
Online AccessGet full text

Cover

More Information
Summary:This paper presents verification-guided development (VGD), a software engineering process we used to build Cedar, a new policy language for expressive, fast, safe, and analyzable authorization. Developing a system with VGD involves writing an executable model of the system and mechanically proving properties about the model; writing production code for the system and using differential random testing (DRT) to check that the production code matches the model; and using property-based testing (PBT) to check properties of unmodeled parts of the production code. Using VGD for Cedar, we can build fast, idiomatic production code, prove our model correct, and find and fix subtle implementation bugs that evade code reviews and unit testing. While carrying out proofs, we found and fixed 4 bugs in Cedar's policy validator, and DRT and PBT helped us find and fix 21 additional bugs in various parts of Cedar.
ISSN:2331-8422