Description
NTFS permissions are handed out per user, but on your own machine you are the administrator, so there is nowhere to express "this one program must not touch that folder". Set the read-only attribute and any program clears it with a single SetFileAttributes call. EaseFilter File Protector moves the checkpoint into a kernel-mode file system filter driver, where the request is judged before it ever reaches the file system — user-mode code cannot step around it, and elevating does not help.
Rules combine four dimensions: file, folder, process and user. A directory can be openable by a named handful of processes only, certain files can be invisible to everything else, and writes and renames can be allowed while deletes are refused outright. The console lists every intercepted operation as it happens — the time, the user name, the process name and pid, the thread id, which I/O it was, which file it touched and what status came back, with refused rows marked AccessDenied in red.
Allow or block per operation: create, write, rename and delete are configured separately, so you can permit edits but forbid deletion, or enforce read-only while still allowing new files.
Authorise by process: in the same folder, your chosen application reads and writes normally while every other program cannot even enumerate the contents — the thing being kept out is other software on this machine, not just other users.
Hide files from selected processes: the file exists on disk, but for an unauthorised process the directory simply does not contain that entry, so not even its existence leaks.
Block copying data out: a program can be allowed to open and work with a file while the paths that would copy it elsewhere or push it off the machine stay closed.
Live I/O log: the console shows every access a rule matched, in order, with who, which process, what they did and how it ended — so diagnosing a permission problem is reading, not guessing.
Ships with SDK source: the program is a sample application of the EaseFilter filter driver SDK, and the package includes full C# and C++ demo source, so the same control logic can be lifted into your own product.
Rules combine four dimensions: file, folder, process and user. A directory can be openable by a named handful of processes only, certain files can be invisible to everything else, and writes and renames can be allowed while deletes are refused outright. The console lists every intercepted operation as it happens — the time, the user name, the process name and pid, the thread id, which I/O it was, which file it touched and what status came back, with refused rows marked AccessDenied in red.
Features
Allow or block per operation: create, write, rename and delete are configured separately, so you can permit edits but forbid deletion, or enforce read-only while still allowing new files.
Authorise by process: in the same folder, your chosen application reads and writes normally while every other program cannot even enumerate the contents — the thing being kept out is other software on this machine, not just other users.
Hide files from selected processes: the file exists on disk, but for an unauthorised process the directory simply does not contain that entry, so not even its existence leaks.
Block copying data out: a program can be allowed to open and work with a file while the paths that would copy it elsewhere or push it off the machine stay closed.
Live I/O log: the console shows every access a rule matched, in order, with who, which process, what they did and how it ended — so diagnosing a permission problem is reading, not guessing.
Ships with SDK source: the program is a sample application of the EaseFilter filter driver SDK, and the package includes full C# and C++ demo source, so the same control logic can be lifted into your own product.
