Folder Guard lets you control access not only to individual files and/or folders, but also to the whole classes of files. For example, if you need to set up some general access rights to the Excel files, you can use Folder Guard to create a filter that would apply to the Excel files only (that, to the files with the extension .XLS), and then assign the desired access attribute to such a filter, that would make the attribute to apply to any Excel file, no matter where it is located.
Let us explain in more detail. A filter is a set of data that defines which files it applies to (according to the names of the files, the folders they are located in, and programs that are accessing the files). You may define several different filters, or have no filters at all, depending on how exactly you want your computer to be protected.
After you have set up the filters and enabled the protection, Folder Guard begins to monitor the events of accessing the files on your computer. Whenever a program attempts to access a file, Folder Guard users the list of filters you've set up to determine whether the file name, the name of the folder where the file is located, and the name of the program that is accessing the file match any of the filters. If Folder Guard finds such a filter, it uses its attribute (full access, read-only, or no access) to allow or deny access to the file. It no match is detected, the access attribute of the folder where the file is located is used to determine whether to allow or deny the access to the file.
Folder Guard comes with a pre-loaded set of filters (discussed below). To see the currently defined filters, use the command View - Filters. When you choose this command, Folder Guard hides the list of folders, and shows the list of filters instead:
You can create new filters or modify the existing ones using the commands on the Filter menu. (This menu appears on the menu bar only when the filter list is displayed in the main window of Folder Guard). To return back to the list of folders, use the command View - Folders.
Note that only the access attributes may be applied to the filters; the visibility of the files defined by the filters is always determined by the visibility attributes of the appropriate folders where the files are located.
Folder Guard comes with several pre-configured filters, some of which are discussed below. You can use them as they are, or you can modify them to better suit your needs, delete them or create the new ones. If you don't want the filters to be used, you can reset their attributes with the Attributes - Reset command.
Example 1: Windows files.
This is a very simple filter that is designed to restrict access to the files system.ini and protocol.ini, located in the Windows folder (which is usually C:\Windows):
If you don't want users to modify these files (directly, or by installing other programs that may modify these files), assign the read-only attribute to this filter:
If you want only some of your users to be restricted from modifying these files, select each user's name in the User List of Folder Guard and apply the read-only attribute to this filter for each such user, one user at a time.
Note that if you want to restrict access to specific files (as in this case), you could also do so by adding the files in question to the folder list of Folder Guard (using the Protect - Add File command) and assigning appropriate attributes to such files.
Example 2: Restrict Install.
Suppose you don't want other users to install any new software on your computer without your permission (assuming that users have access to the floppy disk drive (A:) and to the CD-ROM drive (E:)). One solution could be to assign the no access attribute to the root folders of the A: and E: drives with Folder Guard, however that would also prevent the users from saving their work on the floppies, and from using any CD-ROMs.
This is a typical situation where filters provided by Folder Guard offer a more effective solution. Since installing new software usually involves running the Setup.exe or Install.exe program (and using the autorun.inf files from CD-ROMs), you want to prevent users from running such programs while allowing them to access other files on the floppy and CD-ROM drives.
To achieve this result, consider the Restrict Install filter with the following properties:
This filter would be applied only to the files named Setup.exe, Install.exe, or autorun.inf, and only if they are located on the A: or E: drives (in the root folders or any of the subfolders). Now assign the no access attribute to this filter for all users whose access to these files you want restrict:
If you want yourself to be able to run Setup.exe and Install.exe, assign the full access attribute to this filter while your user name is selected in the User List.
Example 3: Restrict run from floppy.
Suppose you don't want other users to run programs from the floppy drive. Yet, you would like them to be able to open from and save their documents to the floppy disks.
To achieve this result, consider the Restrict run from floppy filter with the following properties:
This filter would apply only to the program files (since their file names have the extensions .exe, .com, and .bat), and only if they are located on the A: drive (in the root folder or any of its the subfolders). Now assign the no access attribute to this filter for all users whose access to these files you want to be restricted. If you want yourself to be able to run programs from the floppy disks, assign the full access attribute to this filter while your user name is selected in the User List.
Example 4: Run only allowed applications.
Suppose you don't want other users to run any programs other than MS Word and Excel. Consider the following filter:
This filter would apply to all program files (that is the files with extensions .exe, .com, and .bat), but not to the files winword.exe (MS Word) and excel.exe (MS Excel). Also, this filter would not apply to the files located in the folders that begin with C:\Windows (since these folders contain system files, which should always be accessible in order for Windows to work properly). The programs located in the folder "C:\Program Files\Folder Guard" would also be exempt from this filter, since you want to be able to run Folder Guard files to change or disable the protection as needed.
Now, if you assign the no access attribute to this filter for a particular user, that user would not be able to run any programs other than MS Word and Excel, and the programs located in the Windows folder, or its subfolders.
Example 5: Internet Explorer data.
Suppose you want your users to be able to use Internet Explorer (IE), however you don't want then to be able to delete their Internet cookies. An obvious approach to set this up would be to assign the read-only attribute to the folder where IE stores the cookie files (such as C:\Windows\Cookies), but that may cause IE to fail, since it expects such a folder to be fully accessible.
The solution is also set up a filter that would grant IE fill access rights to the files in these folders:
If you assign the full access attribute to this filter, then Folder Guard would allow IE to write data into the cookie files, (because they would be accessed by the IE program, iexplore ). If a user uses some other program to delete the cookie files, the filter would not be applied to such operations, and the read-only attribute you have assigned to this folder would restrict such operations.
Note: The Trusted Programs list has a higher priority than the list of the filters. That is, a trusted program can access all files unconditionally, even if you have set up a filter that restrict access to certain files for that program.
Example 6: Restricting Internet Explorer downloads.
If you want your users to be able to use Internet Explorer (IE) for web browsing, but not to be able to download the executable files onto your computer, you could create a filter that would enforce such a restriction.
The idea of the protection is based on the fact that when Internet Explorer is downloading a file, it stores it in its Temporary Internet Files folder, along with the images and other files necessary to display the web pages when browsing. Only after the file has been successfully downloaded into the temporary folder, Internet Explorer moves it to the destination folder for your choice. This gives us an idea of how to prevent the downloads: we need to prevent Internet Explorer from being able to create program files (such as the EXE and ZIP files) in the temporary folder. However, we must still allow Internet Explorer to store files of other types (such as image files), to be able to display the web pages properly when browsing the Internet. This is just the type of a problem that can be easily solved using the filters of Folder Guard.
To achive this, we need to set up a filter that would apply to the *.exe and *.zip files, to the Temporary Internet Files folder, and to the Internet Explorer module iexplore :
If you assign the no access attribute to this filter, it will prevent IE from writing EXE and ZIP files to its temporary folder, and that would effectively stop it from being able to download such files. Note that we have entered the masks of only two most popular file formats for the programs, *.exe and *.zip. There are, however, other formats for distributing programs via the Internet, for