Systems and methods for protected local backup
Systems and methods for protected local backup. In an illustrative, non-limiting embodiment, an Information Handling System (IHS) may include one or more processors and a memory coupled to the one or more processors, the memory including program instructions stored thereon that, upon execution by the one or more processors, cause the IHS to: receive, via a file system filter driver, a request targeting a file system within a storage device, wherein the file system filter driver is owned by a backup application; and reject the request, via the file system filter driver, in response to the request having been issued by an application other than the backup application.
1. An Information Handling System (IHS), comprising:
one or more processors; and
a memory coupled to the one or more processors, the memory including program instructions stored thereon that, upon execution by the one or more processors, cause the IHS to:
receive, via a file system filter driver located at the lowest level of a filter driver stack implemented by an Operating System (OS) executed by an Information Handling System (IHS), a first request and a second request targeting a file system within a storage device coupled to the IHS via a Universal Serial Bus (USB) port, wherein the file system filter driver is owned by a backup application, wherein the filter driver stack includes an encryption filter driver, and wherein the OS is configured to load the encryption filter driver before loading the file system filter driver;
in response to the first request being a write request issued by any application other than the backup application, provide to the application, by the file system filter driver, an indication that the write request was fulfilled and reject the write request; and
in response to the second being a read request issued by a selected application other than the backup application, allow the read request.
2. The IHS of claim 1 , wherein the storage device is coupled to the IHS via a Universal Serial Bus (USB) port.
3. The IHS of claim 1 , wherein the file system filter driver is applied to all storage devices belonging to a same class of devices as the storage device.
4. The IHS of claim 1 , wherein the file system filter driver is applied only to the storage device, and not applied to another storage device in a same class of devices as the storage device.
5. The IHS of claim 1 , wherein the program instructions, upon execution, further cause the IHS to allow another write request issued by the OS.
6. The IHS of claim 1 , wherein at least one of the first or second requests is issued by a user with administrative privileges.
7. A memory device having program instructions stored thereon that, upon execution by an Information Handling System (IHS), cause the IHS to:
receive, via a file system filter driver located at the lowest level of a filter driver stack implemented by an Operating System (OS) executed by an Information Handling System (IHS), a first request and a second request targeting a file system within a storage device coupled to the IHS via a Universal Serial Bus (USB) port, wherein the file system filter driver is owned by a backup application, wherein the filter driver stack includes an encryption filter driver, and wherein the OS is configured to load the encryption filter driver before loading the file system filter driver;
in response to the first request being a read request issued by a selected application other than the backup application, allow the read request; and
in response to the second request being a write request issued by any application other than the backup application, provide to the application, by the file system filter driver, an indication that the write request was fulfilled and reject the write request.
8. The memory device of claim 7 , wherein the file system filter driver is applied to all storage devices belonging to a same class of devices as the storage device.
9. The memory device of claim 7 , wherein the file system filter driver is applied only to the storage device, and not to another storage device in a same class of devices as the storage device.
10. The memory device of claim 7 , wherein the storage device is coupled to the IHS via a Universal Serial Bus (USB) port.
11. The memory device of claim 7 , wherein the file system filter driver is applied to all storage devices belonging to a same class of devices as the storage device.
12. The memory device of claim 7 , wherein the file system filter driver is applied only to the storage device, and not applied to another storage device in a same class of devices as the storage device.
13. The memory device of claim 7 , wherein the program instructions, upon execution, further cause the IHS to allow another write request issued by the OS.
14. The memory device of claim 7 , wherein at least one of the first or second requests is issued by a user with administrative privileges.
15. The memory device of claim 7 , wherein the storage device is coupled to the IHS via a Universal Serial Bus (USB) port.
16. A method, comprising:
receiving, via a file system filter driver located at the lowest level of a filter driver stack implemented by an Operating System (OS) executed by an Information Handling System (IHS), a first request and a second request targeting a file system within a storage device coupled to the IHS via a Universal Serial Bus (USB) port, wherein the file system filter driver is owned by a backup application, wherein the filter driver stack includes an encryption filter driver, and wherein the OS is configured to load the encryption filter driver before loading the file system filter driver;
in response to the first request being a write request issued by any application other than the backup application, providing to the application, by the file system filter driver, an indication that the write request was fulfilled and rejecting the write request; and
in response to the second request being a read request issued by a selected application other than the backup application, allowing the read request.
17. The method of claim 16 , wherein the file system filter driver is applied to all storage devices belonging to a same class of devices as the storage device.
18. The method of claim 16 , wherein the file system filter driver is applied only to the storage device, and not applied to another storage device in a same class of devices as the storage device.
19. The method of claim 16 , wherein the program instructions, upon execution, further cause the IHS to allow another write request issued by the OS.
20. The method of claim 16 , wherein at least one of the first or second requests is issued by a user with administrative privileges.