MITRE ATT&CK T1529: System Shutdown/Reboot
When to use this skill
Use this skill when the task involves T1529, System Shutdown/Reboot, enterprise ATT&CK, TTP mapping, detection engineering, hunting, incident-response enrichment, control validation, or authorized adversary-emulation planning. Treat it as a defensive analysis aid: keep outputs focused on understanding, detecting, mitigating, and safely validating this ATT&CK technique.
Technique context
- ATT&CK domain: enterprise
- ATT&CK ID: T1529
- Technique name: System Shutdown/Reboot
- Type: technique
- ATT&CK URL: https://attack.mitre.org/techniques/T1529
- Tactics: impact
- Platforms: ESXi, Linux, macOS, Network Devices, Windows
- Required permissions: Not specified
- Effective permissions: Not specified
- Defenses bypassed: Not specified
ATT&CK description
Adversaries may shutdown/reboot systems to interrupt access to, or aid in the destruction of, those systems. Operating systems may contain commands to initiate a shutdown/reboot of a machine or network device. In some cases, these commands may also be used to initiate a shutdown/reboot of a remote computer or network device via Network Device CLI (e.g. reload).(Citation: Microsoft Shutdown Oct 2017)(Citation: alert_TA18_106A) They may also include shutdown/reboot of a virtual machine via hypervisor / cloud consoles or command line tools.
Shutting down or rebooting systems may disrupt access to computer resources for legitimate users while also impeding incident response/recovery.
Adversaries may also use Windows API functions, such as InitializeSystemShutdownExW or ExitWindowsEx, to force a system to shut down or reboot.(Citation: CrowdStrike Blog)(Citation: Unit42 Agrius 2023) Alternatively, the NtRaiseHardErroror ZwRaiseHardError Windows API functions with the ResponseOption parameter set to OptionShutdownSystem may deliver a “blue screen of death” (BSOD) to a system.(Citation: SonicWall)(Citation: NtRaiseHardError)(Citation: NotMe-BSOD) In order to leverage these API functions, an adversary may need to acquire SeShutdownPrivilege (e.g., via Access Token Manipulation).(Citation: Unit42 Agrius 2023)
In some cases, the system may not be able to boot again.
Adversaries may attempt to shutdown/reboot a system after impacting it in other ways, such as Disk Structure Wipe or Inhibit System Recovery, to hasten the intended effects on system availability.(Citation: Talos Nyetya June 2017)(Citation: Talos Olympic Destroyer 2018)
Agent workflow
- Clarify scope: identify the system, asset class, log sources, cloud or endpoint platform, and whether the user wants triage, detection, coverage assessment, or safe emulation planning.
- Load bundled resources as needed: use
references/technique-profile.json for structured metadata, references/detection-and-mitigation.md for triage and telemetry guidance, references/known-threat-context.md for ATT&CK relationship context, and templates/ for repeatable outputs.
- Map observations to ATT&CK: compare the user's evidence to the ATT&CK description, tactics, platforms, and known procedure patterns before asserting a match.
- Produce defensive outputs: prioritize hypotheses, telemetry requirements, detection logic ideas, validation steps, containment guidance, and mitigations.
- Preserve uncertainty: distinguish confirmed evidence, plausible indicators, assumptions, and gaps. Recommend what to collect next.
- Stay safe: do not provide malware, credential theft, persistence, evasion, destructive automation, or unauthorized exploitation instructions. For adversary emulation, keep steps bounded to approved lab or control-validation contexts and omit operational abuse details.
Bundled resources
references/technique-profile.json: machine-readable ATT&CK metadata for this technique.
references/detection-and-mitigation.md: detection notes, telemetry checklist, triage questions, mitigation candidates, and false-positive considerations.
references/known-threat-context.md: ATT&CK relationship context with attribution cautions.
templates/detection-brief.md: detection engineering brief template.
templates/hunt-plan.md: threat hunt plan template.
templates/incident-response-note.md: incident response note template.
templates/coverage-assessment.md: ATT&CK coverage assessment template.
scripts/render_brief.py: local helper that renders a Markdown defensive brief from technique-profile.json.
assets/output-schema.json: JSON schema for structured technique analysis outputs.
To generate a quick brief, run python scripts/render_brief.py --output brief.md from inside this skill directory, or adapt the templates directly.
Detection guidance
No ATT&CK detection guidance was present in the source STIX object.
Useful telemetry and data sources
- Not specified in the STIX object.
Mitigations to consider
- No ATT&CK mitigation relationships were present in the source STIX bundle.
Known threat context
Use these examples only as contextual leads, not as proof that an observed event is this technique:
- 2025 Poland Wiper Attacks (campaign)
- APT37 (intrusion-set)
- APT38 (intrusion-set)
- AcidPour (malware)
- AcidRain (malware)
- Apostle (malware)
- AvosLocker (malware)
- BFG Agonizer (malware)
- Black Basta (malware)
- CHIMNEYSWEEP (malware)
- DCSrv (malware)
- DarkGate (malware)
- DynoWiper (malware)
- HermeticWiper (malware)
- KillDisk (malware)
- Latrodectus (malware)
- Lazarus Group (intrusion-set)
- LockerGoga (malware)
- LookBack (malware)
- Maze (malware)
Recommended output pattern
When responding with this skill, structure the answer as:
- Assessment: whether the evidence supports this ATT&CK mapping and why.
- Evidence: specific indicators, logs, behaviors, and assumptions.
- Detection: telemetry sources, analytic logic, and tuning considerations.
- Response: containment, eradication, recovery, and validation actions.
- Coverage gaps: missing logs, sensors, controls, or environmental details.
- References: include the ATT&CK URL and any user-provided evidence references.
ATT&CK contributors
- Austin Clark, @c2defense
- Hubert Mank
- Janantha Marasinghe
1---2name: attack-ent-t1529-system-shutdown-reboot3description: "Analyze MITRE ATT&CK T1529 System Shutdown/Reboot in the enterprise matrix. Use for TTP triage, detection engineering, hunting, defensive emulation planning, mitigations, incident response mapping, ATT&CK coverage, or questions mentioning T1529, System Shutdown/Reboot, or enterprise ATT&CK. Adversaries may shutdown/reboot systems to interrupt access to, or aid in the destruction of, those systems."4license: MITRE ATT&CK Terms of Use apply to ATT&CK-derived content. See https://attack.mitre.org/resources/terms-of-use/5metadata:6 source: https://skillmd.com/skills/santosomar/attack-ent-t1529-system-shutdown-reboot7 upstream: mitre-attack/attack-stix-data8 domain: enterprise9 attack_id: T152910 attack_stix_id: attack-pattern--ff73aa03-0090-4464-83ac-f89e233c02bc11 attack_version: "1.5"12 attack_modified: "2025-10-24T17:49:40.145Z"13---1415# MITRE ATT&CK T1529: System Shutdown/Reboot1617## When to use this skill1819Use this skill when the task involves T1529, System Shutdown/Reboot, enterprise ATT&CK, TTP mapping, detection engineering, hunting, incident-response enrichment, control validation, or authorized adversary-emulation planning. Treat it as a defensive analysis aid: keep outputs focused on understanding, detecting, mitigating, and safely validating this ATT&CK technique.2021## Technique context2223- ATT&CK domain: enterprise24- ATT&CK ID: T152925- Technique name: System Shutdown/Reboot26- Type: technique27- ATT&CK URL: https://attack.mitre.org/techniques/T152928- Tactics: impact29- Platforms: ESXi, Linux, macOS, Network Devices, Windows30- Required permissions: Not specified31- Effective permissions: Not specified32- Defenses bypassed: Not specified3334## ATT&CK description3536Adversaries may shutdown/reboot systems to interrupt access to, or aid in the destruction of, those systems. Operating systems may contain commands to initiate a shutdown/reboot of a machine or network device. In some cases, these commands may also be used to initiate a shutdown/reboot of a remote computer or network device via [Network Device CLI](https://attack.mitre.org/techniques/T1059/008) (e.g. <code>reload</code>).(Citation: Microsoft Shutdown Oct 2017)(Citation: alert_TA18_106A) They may also include shutdown/reboot of a virtual machine via hypervisor / cloud consoles or command line tools.3738Shutting down or rebooting systems may disrupt access to computer resources for legitimate users while also impeding incident response/recovery.3940Adversaries may also use Windows API functions, such as `InitializeSystemShutdownExW` or `ExitWindowsEx`, to force a system to shut down or reboot.(Citation: CrowdStrike Blog)(Citation: Unit42 Agrius 2023) Alternatively, the `NtRaiseHardError`or `ZwRaiseHardError` Windows API functions with the `ResponseOption` parameter set to `OptionShutdownSystem` may deliver a “blue screen of death” (BSOD) to a system.(Citation: SonicWall)(Citation: NtRaiseHardError)(Citation: NotMe-BSOD) In order to leverage these API functions, an adversary may need to acquire `SeShutdownPrivilege` (e.g., via [Access Token Manipulation](https://attack.mitre.org/techniques/T1134)).(Citation: Unit42 Agrius 2023)41 In some cases, the system may not be able to boot again. 4243Adversaries may attempt to shutdown/reboot a system after impacting it in other ways, such as [Disk Structure Wipe](https://attack.mitre.org/techniques/T1561/002) or [Inhibit System Recovery](https://attack.mitre.org/techniques/T1490), to hasten the intended effects on system availability.(Citation: Talos Nyetya June 2017)(Citation: Talos Olympic Destroyer 2018)4445## Agent workflow46471. Clarify scope: identify the system, asset class, log sources, cloud or endpoint platform, and whether the user wants triage, detection, coverage assessment, or safe emulation planning.482. Load bundled resources as needed: use `references/technique-profile.json` for structured metadata, `references/detection-and-mitigation.md` for triage and telemetry guidance, `references/known-threat-context.md` for ATT&CK relationship context, and `templates/` for repeatable outputs.493. Map observations to ATT&CK: compare the user's evidence to the ATT&CK description, tactics, platforms, and known procedure patterns before asserting a match.504. Produce defensive outputs: prioritize hypotheses, telemetry requirements, detection logic ideas, validation steps, containment guidance, and mitigations.515. Preserve uncertainty: distinguish confirmed evidence, plausible indicators, assumptions, and gaps. Recommend what to collect next.526. Stay safe: do not provide malware, credential theft, persistence, evasion, destructive automation, or unauthorized exploitation instructions. For adversary emulation, keep steps bounded to approved lab or control-validation contexts and omit operational abuse details.5354## Bundled resources5556- `references/technique-profile.json`: machine-readable ATT&CK metadata for this technique.57- `references/detection-and-mitigation.md`: detection notes, telemetry checklist, triage questions, mitigation candidates, and false-positive considerations.58- `references/known-threat-context.md`: ATT&CK relationship context with attribution cautions.59- `templates/detection-brief.md`: detection engineering brief template.60- `templates/hunt-plan.md`: threat hunt plan template.61- `templates/incident-response-note.md`: incident response note template.62- `templates/coverage-assessment.md`: ATT&CK coverage assessment template.63- `scripts/render_brief.py`: local helper that renders a Markdown defensive brief from `technique-profile.json`.64- `assets/output-schema.json`: JSON schema for structured technique analysis outputs.6566To generate a quick brief, run `python scripts/render_brief.py --output brief.md` from inside this skill directory, or adapt the templates directly.6768## Detection guidance6970No ATT&CK detection guidance was present in the source STIX object.7172## Useful telemetry and data sources7374- Not specified in the STIX object.7576## Mitigations to consider7778- No ATT&CK mitigation relationships were present in the source STIX bundle.7980## Known threat context8182Use these examples only as contextual leads, not as proof that an observed event is this technique:8384- 2025 Poland Wiper Attacks (campaign)85- APT37 (intrusion-set)86- APT38 (intrusion-set)87- AcidPour (malware)88- AcidRain (malware)89- Apostle (malware)90- AvosLocker (malware)91- BFG Agonizer (malware)92- Black Basta (malware)93- CHIMNEYSWEEP (malware)94- DCSrv (malware)95- DarkGate (malware)96- DynoWiper (malware)97- HermeticWiper (malware)98- KillDisk (malware)99- Latrodectus (malware)100- Lazarus Group (intrusion-set)101- LockerGoga (malware)102- LookBack (malware)103- Maze (malware)104105## Recommended output pattern106107When responding with this skill, structure the answer as:108109- Assessment: whether the evidence supports this ATT&CK mapping and why.110- Evidence: specific indicators, logs, behaviors, and assumptions.111- Detection: telemetry sources, analytic logic, and tuning considerations.112- Response: containment, eradication, recovery, and validation actions.113- Coverage gaps: missing logs, sensors, controls, or environmental details.114- References: include the ATT&CK URL and any user-provided evidence references.115116## ATT&CK contributors117118- Austin Clark, @c2defense119- Hubert Mank120- Janantha Marasinghe