Explore chapters and articles related to this topic
Challenges in Designing Software Architectures for Web-Based Biomedical Signal Analysis
Published in Aboul Ella Hassanien, Nilanjan Dey, Surekha Borra, Medical Big Data and Internet of Medical Things, 2018
Alan Jovic, Kresimir Jozic, Davor Kukolja, Kresimir Friganovic, Mario Cifrek
One additional layer of security can be implemented on a server, even before transmission of data. That layer is the storage of files in an encrypted form. By implementing this layer, security is increased substantially because the only point left open to attack is the RAM. Encryption can be achieved in two ways, depending on the file systems used. On older file systems (e.g. FAT, ext2, ext3), which do not support encryption, a file is run through some encryption software or library and then stored as a regular file. On newer file systems, it is only necessary to enable encryption as the files are then encrypted on the fly before being stored. Most notable examples of the newest file systems are ZFS and APFS, which contain many other improvements in addition to file encryption [86]. The approach to use the newest file systems is the preferable method for encryption and it is very easy to implement, because a server administrator just needs to create a file system that supports encryptions and enable it.
RS3: An efficient retroactive security scheme on NAND flash memory based solid state disk
Published in Amir Hussain, Mirjana Ivanovic, Electronics, Communications and Networks IV, 2015
Wei Shi, Zhanye Wang, Dapeng Ju, Dongsheng Wang
Zhang et al. presented a storage-monitoring infrastructure as an IDS in Virtual Machine Introspection (VMI) environment (Zhang et al. 2006, Lee et al. 2013). However, their monitoring framework was only implemented for FAT32 file system, which is far less complex than NTFS and is rarely used in modern systems. Jiang et al. also implemented a VMI-IDS, called VMwatcher, which incorporated disk, memory, and kernel-level events (Jiang et al. 2007). They too could not analyze the ubiquitous NTFS file system, and instead required that Windows VMs use the Linux ext2/ext3 file system. The VMI-IDS of Joshi et al. detected intrusions before the vulnerability was disclosed (Joshi et al. 2005).
Find the right solution
Published in Jens Jacobsen, Tilman Schlenker, Lisa Edwards, Implementing a Digital Asset Management System, 2012
Jens Jacobsen, Tilman Schlenker, Lisa Edwards
File systems like those of Mac OS (HFS+), Windows (NTFS), or Linux (UFS, EXT3, ReiserFS, to name just a few) only work as the most basic asset management when a real person does most of the management part. The feature set is quite limited; they just save the assets and provide some fundamental metadata, like creation and modification date. This means that if you want to use file systems for DAM you need clear rules, virtually error-free working, and great discipline of all the team members. A file system is the DAM that everyone automatically starts with.
Analyzing execution path non-determinism of the Linux kernel in different scenarios
Published in Connection Science, 2023
Yucong Chen, Xianzhi Tang, Shuaixin Xu, Fangfang Zhu, Qingguo Zhou, Tien-Hsiung Weng
To examine the path variability on a Linux-based system depending on the configuration set, we investigated the impact of file system type on the execution path of an application. Therefore, to perform this non-determinism analysis, the application presented in Section 4 is executed in four file systems commonly found in Linux. The file systems that have been selected for this study are as follows: ramfs, ext2, ext3, and ext4. Ramfs is a file system based on ram under Linux whose structure is the simplest among the four file systems. Ext3 and ext4 are based on ext2 with more complex features and extends. Furthermore, ext4 is the default file system for the latest Linux kernel version. The application is based on reading and writing files so that we can record different paths because of the various file systems.