First IEEE International Workshop on Information Assurance, 2003. IWIAS 2003. Proceedings. 2003
DOI: 10.1109/iwias.2003.1192462
|View full text |Cite
|
Sign up to set email alerts
|

Protecting the integrity of an entire file system

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
4

Citation Types

0
4
0

Year Published

2004
2004
2014
2014

Publication Types

Select...
5
3

Relationship

0
8

Authors

Journals

citations
Cited by 15 publications
(4 citation statements)
references
References 4 publications
0
4
0
Order By: Relevance
“…There exist many systems that protect mass data [2,3,4,5,6,7,8,9]. But nearly all of them have certain limitations.…”
Section: Introductionmentioning
confidence: 99%
See 1 more Smart Citation
“…There exist many systems that protect mass data [2,3,4,5,6,7,8,9]. But nearly all of them have certain limitations.…”
Section: Introductionmentioning
confidence: 99%
“…But nearly all of them have certain limitations. For example, Tripwire [2] cannot prevent from replay attack; TDB [5] needs to write a big map containing hash tree to disk at a time to incur performance degradation; Arbre [6] inherits limitations of tree-structured file systems to make synchronization performs poorly; BitLocker [8] only makes pseudo authentication; authenticated encryption of IEEE P1619.x [9] cannot directly prevent from replay attack.…”
Section: Introductionmentioning
confidence: 99%
“…Among them, SFSRO [3] uses a hash of a file-data block as the block identifier to guarantee the integrity of content data; SUNDR [4] uses a hash of a block as the block identifier and a hash tree to provide data integrity at the file system level; TDB [5] describes a database in which it integrates encryption and hashing with a low-level data model that protects data and metadata uniformly; PFS [6] protects data integrity at the block level without tightly integrated into the file system design; Arbre [7] builds hash tree into file system design tightly to protect integrity of the entire file system; many others system can be listed here, such as Sirius [8] and Plutus [9]; two most recent publications are Pletka et al [10] and Oprea et al [11], and one most remarkable endeavor to establish standard of storage device protection is IEEE P1619.x [12]. These works make promising progresses in data storage security; however, there still exist some problems that hold back data applications in real world.…”
Section: Introductionmentioning
confidence: 99%
“…Cryptfs [4] encrypt file data; Tripwire [5] uses the principle of MAC to check the integrity of files, while trusted computing system like NGSCB [6] verifying "program hashes" is similar; SFSRO [7] uses hash of a file-data block to guarantee the integrity of content data; SUNDR [8] uses a hash of a block and hash tree to provide file system integrity; PFS [9] protects data integrity at the block level without integrated into the file system, while Arbre [10] builds hash tree into file system tightly. Recently, several important techniques to protect the locally connected hard disk have appeared; for examples: Windows-Vista BitLocker [11], IEEE P1619.x [12] and Seagate Momentus 5400 FDE.2 Hard Drives [13].…”
Section: Introductionmentioning
confidence: 99%