31 Dec 2026

Varonis is pulling the plug on on-prem. ProLion isn’t.

Learn how to keep your data →
Capability
Industries
Healthcare

Put back what was hit. Nothing else.

The audit trail already knows which files the blocked account touched. Those are the files that come back — individually or in bulk, from the snapshots that are already being taken.

In ProLion DataDefense
NetApp

Syslog CEF and REST, into the tool you already run

A full restore is not a recovery plan.

Rolling a volume back to last night returns every untouched file as well, and everyone loses a morning’s work to clean up after one account. The question is not whether you have snapshots. It is whether you know exactly which files to take out of them.

  • Which files did that account actually change?
  • Can you restore those, and only those?
  • How long would a full-volume rollback cost everyone else?
  • Who authorized the restore, and is that on record?

What it does.

Single-file restore
Restore one file, or a list of them, from an existing snapshot.
Snapshot-based cleanup
Roll back everything a blocked user changed. Unaffected data stays untouched.
The list comes from the audit trail
The same record that caught the attack says which files to restore, with user, path and timestamp.
Four-eyes principle
Every data-protection action can be put behind two sets of credentials, so no one acts alone.

Let’s solve your data challenges.

Connect with our engineers to find the right approach for your infrastructure.

It works with the snapshots you already have.

Recovery reads the snapshots that are already being taken — no second copy, no separate restore product, and no rollback of data that was never touched.

Talk to an engineer who knows your data.

Four fields, and somebody who knows ONTAP, PowerScale and what FPolicy does. Not a qualification call.

Four fields. No hidden newsletter.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.