The Third Extended File System with Copy-On-Write

The Third Extended File System with Copy-On-Write

Limiting Liability in a Federally Compliant File System Zachary N. J. Peterson The Johns Hopkins University Hopkins Storage Systems Lab, Department of Computer Science Regulatory Requirements z Data Maintenance Acts & Regulations – HIPAA, GISRA, SOX, GLB – 4,000+ State and Federal Laws and Regulations with regards to storage z Audit Trail – creating a “chain of trust” – Files are versioned over time – Authenticated block sharing (copy-on-write) between versions. z Disk Encryption – Privacy and Confidentiality – Non-repudiation Hopkins Storage Systems Lab, Department of Computer Science Secure Deletion in a Regulatory Environment z Desire to limit liability when audited – Records that go out of audit scope do so forever – When a disk is subpoenaed old or irrelevant data are inaccessible z Existing Techniques – Secure overwrite [Gutmann] – File key disposal in disk encrypted systems [Boneh & Lipton] z Existing solutions don’t work well in block- versioning file systems Hopkins Storage Systems Lab, Department of Computer Science Technical Problems z Secure overwriting of noncontiguous data blocks is slow and inefficient – When versions share blocks, data to be overwritten may be noncontiguous z Cannot dispose file keys in a versioning file system – Blocks encrypted with a particular key need to be available in future versions z User space tools are inadequate – Can’t delete metadata – Can’t be interposed between file operations – Truncate may leak data – Difficult to be synchronous Hopkins Storage Systems Lab, Department of Computer Science The Big Idea E (B ) → B˜ ,l Kx i i i ˜ Bi = Bi D (B˜ ,l ) → B Kx i i i z Encryption creates an encrypted block and a small 128-bit stub ( ) li z Securely deleting stub, securely deletes block Hopkins Storage Systems Lab, Department of Computer Science Features of our System z Stubs are stored with the inode z When a version is deleted, the inode and its stubs are securely overwritten – In effect securely removing all data associated with that version z Secure deletion with minimal secure overwriting – More efficient than securely overwriting noncontiguous data blocks – Versions may use the same encryption key – Does not increase key overhead Hopkins Storage Systems Lab, Department of Computer Science Interested? z We have a fully working (insecure) snapshot file system for the Linux 2.4 kernel (2.6 soon). – Time-shifting – Snapshot reclamation z Web site: www.ext3cow.com – Download the patch. – Read the technical report. – Join the mailing list. z Email: [email protected] Hopkins Storage Systems Lab, Department of Computer Science Hopkins Storage Systems Lab, Department of Computer Science The Law and Storage z Health Insurance z Sarbanes-Oxley (SOX) Portability and z Gramm-Leach-Bliley Accountability Act (GLB) (HIPAA) z PATRIOT Act z Government z Federal Records Act Information Security Reform Act (GISRA) z DoD Directive 5015.2 z 4,000+ State and z Federal Information Security Management Federal Laws and Act (FISMA) Regulations with regards to storage. Hopkins Storage Systems Lab, Department of Computer Science What are the requirements? z Authorization z Audit Trail – Access controls – Record of all changes (role-based z Secure Storage and authorizations) Transmission – Encryption (confidentiality) – More encryption? – Digital signatures z Integrity & Reliability (non-repudiation) – Unaltered records. z Authentication – Trusted content. Hopkins Storage Systems Lab, Department of Computer Science Introducing Ext3cow z A file system based on ext3 that supports file system snapshot with a time-shifting interface. – Creates immutable views of a file system as it appeared at a specific point in time. – Versions of a file are created with copy-on-write (cow) of blocks. – Snapshots are addressed with an epoch number that corresponds to a system time (gettimeofday). Hopkins Storage Systems Lab, Department of Computer Science Securing our COW file system z Challenges – How to encrypt files that share blocks between versions. – How to change permissions such that a user who had access to a file in the past is not able to access current versions. – Securely deleting files such that they are no longer able to be subpoenaed. Hopkins Storage Systems Lab, Department of Computer Science.

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    12 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us