Data secrecy in distributed storage systems under exact repair

Sreechakra Goparaju, Salim El Rouayheb, Robert Calderbank, H. Vincent Poor

Research output: Chapter in Book/Report/Conference proceedingConference contribution

48 Scopus citations

Abstract

The problem of securing data against eavesdropping in distributed storage systems is studied. The focus is on systems that use linear codes and implement exact repair to recover from node failures. The maximum file size that can be stored securely is determined for systems in which all the available nodes help in repair (i.e., repair degree d = n-1, where n is the total number of nodes) and for any number of compromised nodes. Similar results in the literature are restricted to the case of at most two compromised nodes. Moreover, new explicit upper bounds are given on the maximum secure file size for systems with d < n - 1. The key ingredients for the contribution of this paper are new results on subspace intersection for the data downloaded during repair. The new bounds imply the interesting fact that the maximum amount of data that can be stored securely decreases exponentially with the number of compromised nodes. Whether this exponential decrease is fundamental or is a consequence of the exactness and linearity constraints remains an open question.

Original languageEnglish (US)
Title of host publication2013 International Symposium on Network Coding, NetCod 2013
DOIs
StatePublished - 2013
Event2013 International Symposium on Network Coding, NetCod 2013 - Calgary, AB, Canada
Duration: Jun 7 2013Jun 9 2013

Publication series

Name2013 International Symposium on Network Coding, NetCod 2013

Other

Other2013 International Symposium on Network Coding, NetCod 2013
Country/TerritoryCanada
CityCalgary, AB
Period6/7/136/9/13

All Science Journal Classification (ASJC) codes

  • Computer Networks and Communications
  • Software

Fingerprint

Dive into the research topics of 'Data secrecy in distributed storage systems under exact repair'. Together they form a unique fingerprint.

Cite this