| name | T0816_device-restartshutdown |
| description | Adversaries may forcibly restart or shutdown a device in an ICS environment to disrupt and potentially negatively impact physical processes. |
| category | business-logic |
| version | 18.1 |
| author | cyberstrike-official |
| tags | ["mitre-attack","ics","t0816","inhibit-response-function"] |
| technique_id | T0816 |
| tactic | inhibit-response-function |
| all_tactics | ["inhibit-response-function"] |
| platforms | ["ICS"] |
| mitre_url | https://attack.mitre.org/techniques/T0816 |
| tech_stack | ["ics"] |
| cwe_ids | ["CWE-400"] |
| chains_with | [] |
| prerequisites | [] |
| severity_boost | {} |
T0816 Device Restart/Shutdown
High-Level Description
Adversaries may forcibly restart or shutdown a device in an ICS environment to disrupt and potentially negatively impact physical processes. Methods of device restart and shutdown exist in some devices as built-in, standard functionalities. These functionalities can be executed using interactive device web interfaces, CLIs, and network protocol commands.
Unexpected restart or shutdown of control system devices may prevent expected response functions happening during critical states.
A device restart can also be a sign of malicious device modifications, as many updates require a shutdown in order to take effect.
Kill Chain Phase
- Inhibit Response Function (TA0107)
Platforms: ICS
What to Check
How to Test
Identify Attack Surface
Determine if the target ICS/SCADA environment is susceptible to Device Restart/Shutdown by examining operational technology systems and network architecture.
Assess Existing Defenses
Review whether mitigations for T0816 are in place. If defenses are absent or misconfigured, this technique may be exploitable in the ICS environment.
Remediation Guide
M0807 Network Allowlists
Use host-based allowlists to prevent devices from accepting connections from unauthorized systems. For example, allowlists can be used to ensure devices can only connect with master stations or known management/engineering workstations.
M0804 Human User Authentication
All field controllers should require users to authenticate for all remote or local management sessions. The authentication mechanisms should also support Account Use Policies, Password Policies, and User Account Management.
M0930 Network Segmentation
Segment operational network and systems to restrict access to critical system functions to predetermined management systems.
M0802 Communication Authenticity
Protocols used for control functions should provide authenticity through MAC functions or digital signatures. If not, utilize bump-in-the-wire devices or VPNs to enforce communication authenticity between devices that are not capable of supporting this (e.g., legacy controllers, RTUs).
