An attack chain is the sequence of steps an attacker completes to reach an objective, such as stealing data. Persistence is the step that allows the attacker to keep access to a device after it restarts. Without persistence, malware stops running at the next restart and doesn’t start again on its own.
Reboot-to-Restore discards changes made to the drives it protects each time a device restarts, including any changes malware makes so it can start again. Malware can still run during a session, which is the period between two restarts. It can’t use those drives to carry itself into the next session. Below, we explain how this works, stage by stage.
How Reboot-to-Restore Removes Persistence
Reboot-to-Restore is an endpoint protection method that returns a device to a baseline each time it restarts. The baseline is the approved configuration an administrator sets for the device. This method removes persistence in three stages.
-
Persistence Interception
Persistence interception keeps persistence mechanisms out of the baseline. A persistence mechanism is a file or setting that makes a program start automatically. Common examples on Windows include:
- Registry run keys and Startup folders: Windows launches the programs they reference when a user signs in.
- Scheduled tasks: Task Scheduler runs a program at system startup or on a recurring schedule.
- Windows services: Services are background programs that Windows can start automatically at boot.
- WMI event subscriptions: Windows Management Instrumentation (WMI) runs code when a specified event occurs.
Each of these mechanisms is saved to the device’s drive. Reboot-to-Restore redirects anything written to a protected drive into a separate storage area, leaving the drive’s original contents intact. The mechanism is created in that area but never reaches the baseline. Because every write is redirected, interception doesn’t depend on identifying the malware. Â
Fileless techniques are intercepted as well. They avoid ordinary files, but the registry and WMI repository they write to are stored as files on the drive.
-
Session Containment
Session containment limits malware’s presence on a device to the session in which it runs. During that session, the device works normally. Users can install software and change settings, and malware can run and use the persistence mechanisms it created. All of these changes exist only in the redirected storage area.
How long a session lasts depends on when the device restarts. Shorter sessions give malware less time to act. Restarts can be scheduled for set times or triggered when a user signs out. Restarting at sign-out limits each session to one user. As a result, a startup entry created during one user’s session can’t launch malware when the next user signs in.
Containment applies only to the device’s protected drives, meaning it doesn’t reverse actions that reach beyond them. A restart doesn’t recover data copied off the device during the session. Credentials the malware captured can still be used to access other systems.
-
Reboot Discard
Reboot discard removes the session’s changes when the device restarts. The restart ends any malware running in memory, and the redirected data is no longer referenced. The device starts from its baseline, without the malware files or the persistence mechanisms created to launch them. There’s no need to find and remove each mechanism individually.
With nothing to start it, the malware doesn’t run again. To regain access, an attacker has to compromise the device again by repeating the earlier steps of the attack chain. Any new foothold is limited to a single session in the same way.
Legitimate changes are discarded too, so approved updates and software are installed during maintenance periods. Protection is suspended for the length of each period, and changes made during it become part of the baseline. Locations excluded from protection, such as a separate drive reserved for user data, keep everything written to them, including malicious files.
Discover Faronics Deep Freeze
Faronics Deep Freeze applies Reboot-to-Restore to Windows and Mac computers. IT teams define the baseline each computer returns to and decide when restarts occur, including when users sign out. Windows updates can be applied during scheduled maintenance periods and added to the baseline.
Discover Faronics Deep Freeze.
FAQs
What Is Malware Persistence?
Malware persistence refers to the techniques attackers use to keep access to a device across restarts and other interruptions. On Windows, examples include registry run keys and scheduled tasks that start malware automatically.
Does Reboot-to-Restore Stop Malware From Running?
No. Malware can run during a session. Reboot-to-Restore discards the changes it makes to protected drives at the next restart, which removes any persistence it established on those drives.
What Persistence Does Reboot-to-Restore Not Remove?
Reboot-to-Restore doesn’t remove persistence stored outside the protected drives. Examples include malicious code in system firmware and files saved to locations excluded from protection. It also doesn’t affect accounts or stolen credentials an attacker uses to access other systems.
Does Reboot-to-Restore Replace Antivirus Software?
No. Reboot-to-Restore doesn’t detect or block threats. It complements tools that prevent malware from running or detect it during a session.




