history-independence · research · also History-independent storage

History independence

History independence limits what a stored representation reveals about prior operations beyond the abstract state permitted by its security model.

Observation model: Weak history independence considers one inspection; strong history independence considers repeated inspections. The protected representation and permitted observations must be specified. [1]

Different guarantees: Hiding a remote access trace does not automatically hide history after client compromise. In vORAM+HIRB, the HIRB structure is history independent but the combined system permits bounded recent-history leakage; its secure-deletion guarantee is separate. The model assumes an honest-but-curious server and locally erasable client memory. [2]

Relations

related
Oblivious RAM, Cryptographic erase, Flash translation layer (FTL)

Limitations

  • A property proved for one layer does not automatically cover the physical flash layout beneath it. [1]

Citations

  1. Chen and Sion. HiFlash: A History Independent Flash Device. arXiv:1511.05180v1 (2015), sections II, IV and VI. (accessed 2026-11-12)
  2. Roche, Aviv and Choi. A Practical Oblivious Map Data Structure with Secure Deletion and History Independence. arXiv:1505.07391v2, sections 1.2-1.3 and 3. (accessed 2026-11-12)

Further reading

  1. Hesela: Deleted content and historical traces are different targets (accessed 2026-11-12)

JSON: /data/terms/history-independence.json

Published by Hesela team · Updated

Report a correction · Editorial standards · Reuse guidance

Cite this page
Hesela team. History independence. Hesela. 2026-11-12. https://hesela.dev/terms/history-independence/