Configuring Windows VSS for Rollback

07/29/2021 26 12412

DESCRIPTION:

This Article explains about how to configure VSS on windows computers for capture client rollback feature to work 

The capture client (Advanced) Rollback feature uses the Microsoft Windows Volume Shadow Copy Service (VSS). This service saves a snapshot of the endpoint drives (physical and logical). The service saves changes of the drive to a new snapshot on an interval.

Note: VSS does not save copies of mapped network shares.

RESOLUTION:

Getting started

VSS start options are set on the endpoint OS.

1. If the service is disabled on endpoints, shadow copies are not saved and Rollback will not work.
   Note:  On Windows Server 2008 R2, the Agent always starts the service and saves shadow copies.
2. If the service is set to Manual or Automatic start, the SentinelOne Agent makes sure that shadow copies are saved. 
   Important:  If the service is disabled on an endpoint, and you change it to Manual or Automatic, the Agent does not take a snapshot until the endpoint is rebooted.
3. Shadow copies are protected from accidental delete when the Agent is installed.
   Note: once you change/enable VSS service to Manual or Automatic, the Agent does not take a snapshot until the endpoint is rebooted.

To see shadow copies and add copies on an endpoint:

1. On the endpoint, start cmd with Run as Administrator.
2. Run:  vssadmin list shadows
3. In the output, see the shadow copies of the Agent. The Type is:  ApplicationRollback
4. If there are no copies, enable the service:
   vssadmin Add ShadowStorage /For=drive /On=storage_drive /MaxSize=percent%
   For example:  vssadmin Add ShadowStorage /For=C: /On=C: /MaxSize=10%

If there are no copies, please verify if Volume Shadow Copy Service has been enabled/running, if not, enable the service. As the shadow copies will not be saved and Rollback will not work if the VSS service is disabled on endpoints, hence make sure VSS service has been enabled and shadow copies are saved periodically. 

Note: Shadow copies can take up huge space on your hard drive. This is especially important on virtual systems. We recommend you to set the minimum VSS percent disk utilization to 10% and not to be less than 5%. VSS space configuration changes the number of stored copies. When the allocated space is filled, the next VSS snapshot replaces older copies.

To see used space in Windows 7 and higher:

1. Open System and Security >  System.
2. Click System protection.
3. In the System Properties window, open the System Protection tab.
   Make sure the drives you want to be able to rollback are selected. The SentinelOne Agent creates a new snapshot (restore point) when the endpoint shuts down or starts. If you want to make a new snapshot for this drive on this endpoint, click Create.
4. Click Configure.
   The System Protection for drive window opens. See the Current Usage and Max Usage.

To configure Windows for optimal disk space:

Shadow copies can take up space. This is especially important on virtual systems. We recommend that you set the minimum VSS percent disk utilization to 10%. We highly recommend that it not be less than 5%. VSS space configuration changes the number of stored copies. When the allocated space is filled, the next VSS snapshot replaces older copies.

The Agent respects the limits set by the operating system and does not change the VSS configuration. It does not exceed the allocated space or maximum limit of stored copies (512).

1. On the endpoint, start cmd with Run as Administrator.
2. Run:  vssadmin List ShadowStorage
   
   The last line of the output shows the maximum storage in GB and in percent of the total.
   
   
3. Change the space allocation for VSS:
   
   vssadmin Resize ShadowStorage /For=<drive> /On=<storage_drive> /MaxSize=<percent>%
   Example: vssadmin Resize ShadowStorage /For=C: /On=C: /MaxSize=10%
   
   Space allocation impacts security!
   Imagine that you set the Windows allocated space for shadow copies to 1% of the disk space of an endpoint. Your Agent is set to save a copy every 4 hours. The endpoint is attacked successfully by ransomware. You must mitigate with Rollback in less than 4 hours - 4 hours from the last copy, not 4 hours from the attack. If you wait too long, the good copies (before the attack) are replaced with copies of the encrypted drive or files. If the attack happens just before the interval roll, your security team has almost no chance with 1% space.
   
   The minimum recommended space allocation of 5 to 10 percent is enough to give you time to respond with a successful mitigation.

• On the endpoint, start cmd with Run as Administrator.
  Go to the SentinelOne directory: 
  cd c:\program files\sentinelone\sentinel agent <version>\
  
  
• Turn off the Agent self-protection. With the passphrase that you copied, run:
  sentinelctl.exe unprotect -k "<passphrase>"
  The unprotect command is necessary to change the configuration of the Agent. Complete this procedure quickly. Do not leave the Agent vulnerable for longer than necessary.
• Run the command to change the interval.
  sentinelctl.exe configure -p agent.snapshotIntervalMinutes -v <minutes>
  The output shows the interval. For example:240 = every 4 hours .
  
  Note: If the output is 0, no shadow copies are saved. This is for specific environment limitations that require you temporarily turn off VSS snapshots for some Agents. If other programs use VSS and take snapshots, Rollback will work. It will depend on the frequency of the other programs and how quickly mitigation is run. 

To disable VSS protection completely:

1. Turn off the Agent self-protection. With the passphrase that you copied, run: sentinelctl.exe unprotect -k "<passphrase>"
2. Turn off VSS protection: sentinelctl config -p agent.vssConfig.vssProtection -v falsesentinelctl config -p agent.vssSnapshots -v false
3. Turn on the Agent self-protection: sentinelctl.exe protect
4. Reboot the endpoint.

To delete snapshots:

Important:  This procedure uses vssadmin, which is a Microsoft tool. For help with vssadmin specific issues, please contact Microsoft.

1. Turn off the Agent self-protection.
   With the passphrase that you copied, run: sentinelctl.exe unprotect -k "<passphrase>"
2. Disable deletion-protection for shadow copies.
   Run: sentinelctl config -p vssConfig.vssProtection -v false
3. Open cmd or powershell as administrator and run the relevant command:
   • To delete all shadow copies:  vssadmin delete shadows /all 
   • To delete the oldest:  vssadmin delete shadows /For=C:/Oldest
   • To select shadow copies to delete, get a list of the shadow copy IDs and then delete by ID:
     vssadmin list shadows
     vssadmin delete shadows /shadow=<ShadowID>
   • If you see this error:
     "Error: Snapshots were found, but they were outside of your allowed context.  Try removing them with the backup application which created them."
     • Log in as an administrator. Membership in the local Administrators group, or equivalent, is required to run DiskShadow.
     • Start DiskShadow:  Diskshadow
     • Run:  delete shadows all
4. Turn on the Agent self-protection:
   sentinelctl.exe protect