Definition
Initiating a host's reboot sequence to terminate all running processes.
How It Works
Host reboot can either be initiated in the physical presence of the device using the power functions or remotely using the provided user interface or an installed EDR agent (with the available function). This process may allow for the removal of specific types of malware, such as fileless malware, and can also prevent further damage, for example, if the system is part of a botnet.
Considerations
- If the attacker has achieved persistence techniques, this technique may not be effective
- Compromised systems may not respond to remote commands to shutdown or reboot, requiring physical intervention.
- Shutting down a system will usually result in the memory losing its state which can be useful in forensic activities so this should be considered when deciding to shutdown.
- Shutting down or rebooting systems may disrupt access to computer resources for legitimate users.
Implementation perspective
Host Reboot should be treated as a technical defensive capability rather than a product checkbox. In practice, teams should define the protected scope, the conditions under which the technique acts, and the observable evidence that demonstrates the intended behavior. For this technique, likely engineering context includes Process.
Use the technique to remove adversary access, malicious objects, processes, credentials, or persistence from the defended environment.
Questions to ask
- What evidence or decision threshold authorizes eviction?
- Which sessions, credentials, processes, objects, or dependencies must be removed together?
- How is business impact controlled while preventing the adversary from retaining access?
- What validation confirms that persistence and alternate access paths no longer remain?
Evidence and validation
- Approved containment and eviction procedures
- Case records showing the trigger, authorization, and actions taken
- Credential, session, object, or process invalidation records
- Post-action scans and monitoring showing that access did not recur
Common failure patterns
- Visible symptoms are removed while credentials, persistence, or alternate paths remain.
- Eviction begins before the scope is understood and causes the adversary to change behavior prematurely.
- Recovery and business restoration occur without post-eviction validation.
This implementation perspective is original Bare Metal Cyber educational content. It does not replace the official D3FEND definition or establish that a specific product implements the technique.
Technique hierarchy
Top-level family
Parent techniques
Direct child techniques
None listed at this level.
Artifacts and ontology entities
These relationships describe how D3FEND connects a defensive technique to artifacts or other ontology entities. They describe graph semantics, not a product certification.
Explicit technique relationships
Show inferred artifact relationship paths (1)
Offensive-technique relationships
These relationships are generated from D3FEND graph paths and are explicitly experimental. They should be treated as hypotheses for defensive analysis—not as proof that the technique prevents, detects, or removes an offensive behavior.
ATT&CK Enterprise (14)
ATT&CK for ICS (7)
Authoritative sources
- Open this technique on the official D3FEND website ↗
- Open the official ontology resources ↗
- Near-Memory & In-Memory Detection of Fileless Malware ↗Marcus Botacin, André Grégio, Marco Antonio Zanata Alves · AcademicPaperReference
Bare Metal Cyber is an independent educational publisher and is not affiliated with or endorsed by The MITRE Corporation. MITRE D3FEND™ and the D3FEND logo are trademarks of The MITRE Corporation. MITRE ATT&CK® and ATT&CK® are registered trademarks of The MITRE Corporation. Use of D3FEND source material is subject to the official Terms of Use.