%0 Conference Proceedings
%T Supporting Secure Provenance Update by Keeping “Provenance” of the Provenance
%+ Universitas Indonesia (UI )
%+ Kyushu University
%A Syalim, Amril
%A Nishide, Takashi
%A Sakurai, Kouichi
%Z Part 2: Asian Conference on Availability, Reliability and Security (AsiaARES)
%< avec comité de lecture
%( Lecture Notes in Computer Science
%B 1st International Conference on Information and Communication Technology (ICT-EurAsia)
%C Yogyakarta, Indonesia
%Y David Hutchison
%Y Takeo Kanade
%Y Madhu Sudan
%Y Demetri Terzopoulos
%Y Doug Tygar
%Y Moshe Y. Vardi
%Y Gerhard Weikum
%Y Khabib Mustofa
%Y Erich J. Neuhold
%Y A Min Tjoa
%Y Edgar Weippl
%Y Ilsun You
%Y Josef Kittler
%Y Jon M. Kleinberg
%Y Friedemann Mattern
%Y John C. Mitchell
%Y Moni Naor
%Y Oscar Nierstrasz
%Y C. Pandu Rangan
%Y Bernhard Steffen
%I Springer
%3 Information and Communicatiaon Technology
%V LNCS-7804
%P 363-372
%8 2013-03-25
%D 2013
%R 10.1007/978-3-642-36818-9_40
%K Provenance
%K Provenance Security
%K E-science
%K Data lineage
%Z Computer Science [cs]
%Z Humanities and Social Sciences/Library and information sciencesConference papers
%X Provenance of data is a documentation of the origin and processes that produce the data. Many researchers argue that the provenance should be immutable: once a provenance is submitted, it should not be changed or updated. A main reason is that the provenance represents the history of data, and the history should not be altered or changed because it represents the fact in the past. Provenance can be represented by a graph, where each node represents the process executed by a party and an edge represents the relationship between two nodes (i.e. a child node uses the outputs of the parent nodes). A method to ensure that the provenance has not been updated is by using signature chain, where the signatures of the parent nodes are recorded in the children nodes so that any changes to the parent nodes will raise inconsistencies between the parent and the children. However, sticking to the requirement that the provenance should be immutable requires unlimited data storage and also we have problems whenever we need to update the provenance for an accidental error. In this paper, we propose a method that allows updates in the signature chain-based secure provenance, while keeping the signature consistent. The main idea is by keeping the ”provenance” of the provenance itself, that is the history of update of the provenance, in the form of the signatures of the previous versions of the nodes. We implement the idea by keeping the signatures of the previous version in a signature tree similar to the Merkle-tree, where the a parent node in tree is the aggregate signature of the children. Using this method, the storage requirement to store signatures is always smaller than the number of updates.
%G English
%Z TC 5
%Z TC 8
%2 https://inria.hal.science/hal-01480195/document
%2 https://inria.hal.science/hal-01480195/file/978-3-642-36818-9_40_Chapter.pdf
%L hal-01480195
%U https://inria.hal.science/hal-01480195
%~ SHS
%~ IFIP-LNCS
%~ IFIP
%~ IFIP-TC
%~ IFIP-TC5
%~ IFIP-TC8
%~ IFIP-ICT-EURASIA
%~ IFIP-LNCS-7804