infrastructure
The Trusted Enclave Still Needed a Fresh Disk
ShieldFS extends ZFS so a hostile storage stack cannot silently roll back, replay or fork persistent state.
Summary
ShieldFS extends ZFS so a hostile storage stack cannot silently roll back, replay or fork persistent state.
The design keeps succinct commitments inside trusted execution environments and a lightweight registry, while authenticating the write-ahead log and storage pool with hash chains and an embedded Merkle tree. Reads verify freshness and integrity without application changes; the paper reports performance comparable to other evaluated filesystems, but the security claim remains conditioned on its confidential-computing threat model and trusted registry.
Why it matters
ShieldFS extends ZFS so a hostile storage stack cannot silently roll back, replay or fork persistent state.
Limits and context
No additional limitation was separately recorded.
Key claims
ShieldFS extends ZFS so a hostile storage stack cannot silently roll back, replay or fork persistent state.
Evidence: source-2026-08-23-014
Sources
- arXiv preprint 2608.19924arXiv · primary research
Corrections
No corrections have been recorded for this story.