Compositional security definitions for higher-order where declassification

Fuente: arXiv
Enregistré dans:
Détails bibliographiques
Auteurs principaux: Menz, Jan, Hirsch, Andrew K., Li, Peixuan, Garg, Deepak
Format: Preprint
Publié: 2026
Sujets:
Accès en ligne:
Tags: Ajouter un tag
Pas de tags, Soyez le premier à ajouter un tag!
_version_ 1866908980279771136
author Menz, Jan
Hirsch, Andrew K.
Li, Peixuan
Garg, Deepak
author_facet Menz, Jan
Hirsch, Andrew K.
Li, Peixuan
Garg, Deepak
contents To ensure programs do not leak private data, we often want to be able to provide formal guarantees ensuring such data is handled correctly. Often, we cannot keep such data secret entirely; instead programmers specify how private data may be declassified. While security definitions for declassification exist, they mostly do not handle higher-order programs. In fact, in the higher-order setting no compositional security definition exists for intensional information-flow properties such as where declassification, which allows declassification in specific parts of a program. We use logical relations to build a model (and thus security definition) of where declassification. The key insight required for our model is that we must stop enforcing indistinguishability once a \emph{relevant declassification} has occurred. We show that the resulting security definition provides more security than the most related previous definition, which is for the lower-order setting. This paper is an extended version of the paper of the same name published at OOPSLA 2023 ([21]).
format Preprint
id arxiv_https___arxiv_org_abs_2604_18300
institution arXiv
publishDate 2026
record_format arxiv
spellingShingle Compositional security definitions for higher-order where declassification
Menz, Jan
Hirsch, Andrew K.
Li, Peixuan
Garg, Deepak
Programming Languages
Cryptography and Security
To ensure programs do not leak private data, we often want to be able to provide formal guarantees ensuring such data is handled correctly. Often, we cannot keep such data secret entirely; instead programmers specify how private data may be declassified. While security definitions for declassification exist, they mostly do not handle higher-order programs. In fact, in the higher-order setting no compositional security definition exists for intensional information-flow properties such as where declassification, which allows declassification in specific parts of a program. We use logical relations to build a model (and thus security definition) of where declassification. The key insight required for our model is that we must stop enforcing indistinguishability once a \emph{relevant declassification} has occurred. We show that the resulting security definition provides more security than the most related previous definition, which is for the lower-order setting. This paper is an extended version of the paper of the same name published at OOPSLA 2023 ([21]).
title Compositional security definitions for higher-order where declassification
topic Programming Languages
Cryptography and Security
url https://arxiv.org/abs/2604.18300