Easier deletion of file shadows

Products Endpoint Protector Ideas
, , ,
1

Which aspect of EPP are you submitting for?

Endpoint Protector Server

What is a one sentence summary of your feature request?

Allow file shadows to be deleted based on EPP user

Please describe your idea in detail. What is your problem, why do you feel this idea is the best solution, etc.

Say I have a user that has been sending and downloading a bunch of files. I have file shadowing enabled, and I can correlate file shadows to the file tracing logs using the file hash. Great!

I’ve now inspected the file shadows and determined that those related to this user can be safely deleted to free up space.
However, this currently entails manually deleting each file shadow…

I would like to be able to delete file shadows in a smarter way, e.g., by being able to select file shadows related to a user.
Since the same file could theoretically be related to several users, the selection of file shadows related to a user could take this into account and only select file shadows exclusive to that user.

In this way, the deletion of many file shadows could be done in a few clicks.

How do you currently solve the challenges you have by not having this feature?

Currently, the only solution I’ve found to deleting all user-related file shadows is to get all the file traces related to the user in question and then manually going through the list of file shadows and deleting them based on this list pulled from the file traces.

This is already tedious for even just a few files and would simply be too impractical for larger amounts of files.

2

I totally agree on this one. We need a better and easier way to manage file shadows, the current implementation is a disaster

3

Hi Niklas,

Thank you for the detailed write-up — you’ve described the problem clearly and I have to agree the use case makes a lot of sense. Being able to delete file shadows tied to a specific user, rather than hunting through the list and removing them one by one is a meaningful quality-of-life improvement.

We agree this is worth addressing and we’ll be logging it as a feature request for consideration in a future release. We can’t commit to a specific timeline just yet, but feedback like this — with a concrete workflow and a clear pain point — is exactly what helps us prioritize.

Thanks also for the additional confirmation. Good to know this resonates with more than one customer.

Regards,
Mihai

1 Like