Previous Topic: Restricting Access to Files and DirectoriesNext Topic: Protect Files


How File Protection Works

When the seosd daemon starts, it performs the UNIX stat command for each discrete file object defined in the database. It then builds a table in memory that contains an entry for each file object. In addition, for each discrete file, the table contains the file's inode and device; with this information, CA ControlMinder can also protect the hard links to the files because the protection is according to device and inode. The database does not keep information about a file's inode and device.

When creating a new file rule through CA ControlMinder:

When you delete a file, CA ControlMinder deletes its entry in the seosd file table, but the entry remains in the CA ControlMinder database in case you create it again.