The consequences of decentralized security in a cooperative storage system

Douglas Thain, Christopher Moretti, Paul Madrid, Philip Snowberger, Jeffrey Hemmes

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

2 Scopus citations

Abstract

Traditional storage systems have considered security as a problem to be solved at the perimeter: once a user is authenticated, each device internal to the system trusts the decision made elsewhere. However, as storage systems become ever more distributed, shared, and dynamic, it becomes necessary to enforce security at the boundaries of each storage device, rather than around the system as a whole. This form of decentralized security presents several new challenges in the design and implementation of distributed storage systems. We explore challenges in distributed file systems, third party transfer, active storage, and group management in the context of a 200-node cooperative storage system deployed at the University of Notre Dame. These explorations result in three recommendations for future system designs.

Original languageEnglish (US)
Title of host publicationProceedings - Third IEEE International Security in Storage Workshop, SISW 2005
Pages71-82
Number of pages12
DOIs
StatePublished - 2005
Event3rd IEEE International Security in Storage Workshop, SISW 2005 - San Francisco, CA, United States
Duration: Dec 13 2005Dec 13 2005

Publication series

NameProceedings - Third IEEE International Security in Storage Workshop, SISW 2005
Volume2005

Conference

Conference3rd IEEE International Security in Storage Workshop, SISW 2005
CountryUnited States
CitySan Francisco, CA
Period12/13/0512/13/05

All Science Journal Classification (ASJC) codes

  • Engineering(all)

Keywords

  • Access control
  • Active storage
  • Decentralized security
  • Distributed file systems
  • Third party transfer

Fingerprint Dive into the research topics of 'The consequences of decentralized security in a cooperative storage system'. Together they form a unique fingerprint.

Cite this