Flexible dynamic information flow control in the presence of exceptions

Deian Stefan, David Mazières, John C. Mitchell, Alejandro RussoJ. Funct. Program 2017 · OpenReview

TL;DR

This paper introduces LIO, a novel dynamic information flow control (IFC) system implemented as a Haskell library. LIO uses a "floating label" approach, where a computation's current label dynamically adjusts to reflect observed sensitive data, and a "clearance" to restrict access, offering a flexible yet secure way to manage information flow in complex software.

What Problem Does This Paper Address?

Managing information flow in complex software systems is crucial for security. Traditional static IFC methods can be too rigid for dynamic environments where new data types and users emerge at runtime. Dynamic IFC approaches, while more flexible, often struggle with safely handling exceptions and preventing covert channels. This paper addresses the challenge of building a flexible, dynamic IFC system that can be implemented as a library, offering robust security guarantees, including safe exception handling and discretionary access control, without requiring language runtime modifications.

Methods

LIO employs a floating-label approach, where a single, mutable "current label" is associated with the entire computation's context. This label dynamically rises to match the highest label of any data observed. This current label then restricts writes to data with lower labels. To maintain flexibility, LIO also introduces labeled values, allowing programmers to explicitly tag data with labels, and a mechanism to encapsulate computations that might otherwise raise the current label. A key innovation is the current clearance, which acts as an upper bound on the current label, enabling discretionary access control and helping to prevent covert channels. LIO also integrates exception handling, where exceptions are labeled with the current label at the point of their occurrence, allowing for safe recovery from IFC violations without compromising security.

Datasets

Not discussed in the paper.

Key Insights and Ideas

  • Floating Labels as a Core Abstraction: The idea of a single, dynamic "current label" for an entire computation simplifies IFC management while providing a powerful mechanism for dynamic security enforcement.
  • Clearance for Discretionary Access Control: Introducing a "clearance" alongside the current label is a clever way to implement discretionary access control, allowing specific code regions to have a defined boundary for accessing sensitive information. This is crucial for preventing covert channels.
  • Labeled Values and Encapsulation: The ability to explicitly label values and encapsulate sensitive computations is vital for maintaining fine-grained control and preventing unintended label creep, especially when dealing with complex data structures or external libraries.
  • Safe Exception Handling for Dynamic IFC: Integrating exception handling directly into the IFC model, where exceptions carry security labels, is a significant step towards making dynamic IFC practical. It allows programs to gracefully recover from security violations without leaking information.
  • Library-Based IFC: Implementing IFC as a library in a language like Haskell, rather than modifying the language itself, makes the approach more accessible and easier to integrate into existing codebases.

Key Results

The paper presents a formal semantics for LIO using a λ-calculus extended with IFC features. They prove key security properties:

  • Non-interference: Confidential information does not leak to observable outputs.
  • Confinement: Computations cannot modify data below their current label or access data above their clearance. They also demonstrate the practical application of LIO through a conference reviewing system (Chair), showcasing how it can manage integrity and confidentiality in a dynamic, multi-user environment.

Limitations and Future Work

The authors acknowledge that while their approach is dynamic and flexible, determining the appropriate label for toLabeled calls might require non-trivial static analysis in some cases. They also mention that their current formalization is limited to a single exception type. Future work could explore extending LIO to handle concurrency and more complex scenarios, as well as investigating more sophisticated static analysis techniques to aid in label management.

Summary updated

Abstract

We describe a language-based, dynamic information flow control (IFC) system called LIO. Our system presents a new design point for IFC, influenced by the challenge of implementing IFC as a Haskell library, as opposed to the more typical approach of modifying the language runtime system. In particular, we take a coarse-grained, floating-label approach, previously used by IFC Operating Systems, and associate a single, mutable label—the current label—with all the data in a computation's context. This label is always raised to reflect the reading of sensitive information and it is used to restrict the underlying computation's effects. To preserve the flexibility of fine-grained systems, LIO also provides programmers with a means for associating an explicit label with a piece of data. Interestingly, these labeled values can be used to encapsulate the results of sensitive computations which would otherwise lead to the creeping of the current label. Unlike other language-based systems, LIO also bounds the current label with a current clearance, providing a form of discretionary access control that LIO programs can use to deal with covert channels. Moreover, LIO provides programmers with mutable references and exceptions. The latter, exceptions, are used in LIO to encode and recover from monitor failures, all while preserving data confidentiality and integrity—this addresses a longstanding concern that dynamic IFC is inherently prone to information leakage due to monitor failure.
BibTeX
@article{stefan2017flexible,
  author = {Deian Stefan and David Mazières and John C. Mitchell and Alejandro Russo},
  title = {{Flexible dynamic information flow control in the presence of exceptions}},
  journal = {J. Funct. Program.},
  year = {2017},
  url = {https://openreview.net/forum?id=o-hK2bt2-82},
}
Figure