 | This articleneeds additional citations forverification. Please helpimprove this article byadding citations to reliable sources. Unsourced material may be challenged and removed. Find sources: "Filesystem-level encryption" – news ·newspapers ·books ·scholar ·JSTOR(October 2024) (Learn how and when to remove this message) |
Filesystem-level encryption,[1] often calledfile-based encryption,FBE, orfile/folder encryption, is a form ofdisk encryption where individual files or directories areencrypted by thefile system itself.
This is in contrast to thefull disk encryption where the entire partition or disk, in which the file system resides, is encrypted.
Types of filesystem-level encryption include:
The advantages of filesystem-level encryption include:
Unlike cryptographic file systems orfull disk encryption, general-purpose file systems that include filesystem-level encryption do not typically encrypt file systemmetadata, such as the directory structure, file names, sizes or modification timestamps. This can be problematic if the metadata itself needs to be kept confidential. In other words, if files are stored with identifying file names, anyone who has access to the physical disk can know which documents are stored on the disk, although not the contents of the documents.
One exception to this is the encryption support being added to theZFS filesystem. Filesystem metadata such as filenames, ownership, ACLs, extended attributes are all stored encrypted on disk. The ZFS metadata relating to the storage pool is stored inplaintext, so it is possible to determine how many filesystems (datasets) are available in the pool, including which ones are encrypted. The content of the stored files and directories remain encrypted.
Another exception isCryFS replacement forEncFS.
Cryptographic file systems are specialized (not general-purpose) file systems that are specifically designed with encryption and security in mind. They usually encrypt all the data they contain – including metadata. Instead of implementing an on-disk format and their ownblock allocation, these file systems are often layered on top of existing file systems e.g. residing in a directory on a host file system. Many such file systems also offer advanced features, such asdeniable encryption, cryptographically secure read-onlyfile system permissions and different views of the directory structure depending on the key or user ...
One use for a cryptographic file system is when part of an existing file system issynchronized with 'cloud storage'. In such cases the cryptographic file system could be 'stacked' on top, to help protect data confidentiality.