You can define read protection and write protection rules to prevent unauthorized data access and changes.
Read protection rules prevent users from reading the content of files, directories, and volumes. When a directory or volume is read-protected, all files in it are read-protected. Any unauthorized attempt to read data from protected files is prevented and an event is generated. Writing to read-protected files is allowed.
Note
You cannot define read protection rules for registry keys.
Write protection rules prevent users from creating and changing existing files, registry keys, and directories. When a directory is included for write protection, all files in that directory and its subdirectories are write protected.
Note
You can also define additional rules to override the read or write protection that is in effect. You can choose programs or users to override read or write protection.
Order of precedence for protection rules
These considerations are used when protection rules are applied at the endpoint.
Exclude rules are given precedence over include rules.
For example, if you erroneously define an include and exclude rule for the same file, the exclude rule applies.
Longer paths are given precedence.
For example, if
C:\tempis included for write protection, andC:\temp\foo.cfgis excluded, the changes tofoo.cfgare permitted. Similarly, if you exclude theHKEY_LOCAL_MACHINEkey and include theHKEY_LOCAL_MACHINE\Systemkey for write protection, the changes to theHKEY_LOCAL_MACHINE\Systemkey are prevented.