Skip to main navigation Skip to search Skip to main content

Towards a Rust SDK for Keystone Enclave Application Development

    Research output: Chapter in Book/Report/Conference proceeding › Conference article in proceedings › Scientific › peer-review

    Abstract

    Secure enclaves are commonly used for securing sensitive data and computation. However, an enclave can only be trusted if the software running in the enclave is secure. Nevertheless, enclave software is often written in low-level languages that are prone to vulnerabilities. As the number of enclave application developers grows, more attention must be paid to secure software development. The use of safe programming languages could be one step towards more secure trusted software. In this paper, we discuss our work towards a Rust programming language SDK for Keystone enclave application development. In addition, we present early performance measurements of the SDK compared to the original Keystone SDK written in the C/C++ languages.
    Original languageEnglish
    Title of host publicationProceedings of the 9th International Conference on Information Systems Security and Privacy, ICISSP
    EditorsPaolo Mori, Gabriele Lenzini, Steven Furnell
    PublisherSciTePress
    Pages29-37
    Number of pages9
    Volume1
    ISBN (Print)978-989-758-624-8
    DOIs
    Publication statusPublished - 2023
    MoE publication typeA4 Article in a conference publication
    Event9th International Conference on Information Systems Security and Privacy, ICISSP - Lisbon, Portugal
    Duration: 22 Feb 2023 → 24 Feb 2023

    Conference

    Conference9th International Conference on Information Systems Security and Privacy, ICISSP
    Country/TerritoryPortugal
    CityLisbon
    Period22/02/23 → 24/02/23

    Keywords

    • Trusted Execution Environments
    • Enclave
    • Rust
    • Security
    • Software Development

    Fingerprint

    Dive into the research topics of 'Towards a Rust SDK for Keystone Enclave Application Development'. Together they form a unique fingerprint.

    Cite this