Windows Event ID 5034: The Windows Firewall Driver was stopped
Written when the Windows Firewall driver stops. It means the substance of filtering halts, leading to loss of protection.
Overview
The subcategory is Audit Other System Events. It is generated when the firewall kernel driver stops. Paired with start 5033, it captures the filtering functionality’s uptime window.
How it is triggered
- A stop due to driver unload and so on (it is not logged during operating system shutdown).
Security review points
- Stopping the driver means packet filtering ceases. Like service stop 5025, note it in the defense-evasion context and investigate stops outside business hours or unplanned.
- Check whether a start 5033 follows the stop (recovery), and whether suspicious communication occurred while stopped.
Notes for log review
- It is not logged during operating system shutdown, so an occurrence means the driver stopped while the system was running. Match the stop time against operational plans.
- Note situations where a stop is not accompanied by a start.
MITRE ATT&CK mapping
| Technique | Tactic | What this event shows |
|---|---|---|
| T1686.003 Windows Host Firewall | Defense Impairment | Stopping the driver disables packet filtering |
Mapping as of ATT&CK v19.2. To search by technique, see the ATT&CK reverse lookup.
Key fields
| Field | Meaning |
|---|---|
Computer / TimeCreated | The host and time of the stop |