800 PowerShell log · Pipeline Execution low severity medium volume

PowerShell Event ID 800 — Pipeline execution details

Pipeline execution details. Contains HostName, RunspaceId, and pipeline details for PowerShell v2/3 without module logging.

Why event 800 matters

Some execution details visible even without full module logging (Event 4103). May capture abbreviated command details.

How to detect it

Low priority when 4103/4104 are enabled. Use as fallback for environments without full PowerShell logging.

Log source
Microsoft-Windows-PowerShell/Operational
Enable PowerShell Module Logging and Script Block Logging via GPO (Administrative Templates → Windows PowerShell).
Fields to pivot on
ScriptBlockTextPathHostApplication

Detection queries

Starting points — adapt the log source, projected fields and thresholds for your environment.

Sentinel / Defender KQL
Event
| where EventLog == "Microsoft-Windows-PowerShell/Operational" and EventID == 800   // Pipeline execution details
// EventData holds: ScriptBlockText, Path, HostApplication
| project TimeGenerated, Computer, RenderedDescription
| sort by TimeGenerated desc
Splunk SPL
index=* sourcetype="WinEventLog:Microsoft-Windows-PowerShell/Operational" EventCode=800
| stats count earliest(_time) as first_seen latest(_time) as last_seen by ComputerName
| sort - count   `# Pipeline execution details — add EventData fields: ScriptBlockText, Path, HostApplication`
Hunt event 800 in Sentinel/Defender →
Build a KQL query for this event in the KQL Query Builder.
Search all event IDs →
Open the interactive Windows Event ID lookup.

Frequently asked questions

What is PowerShell Event ID 800?

Pipeline execution details. Pipeline execution details. Contains HostName, RunspaceId, and pipeline details for PowerShell v2/3 without module logging.

Which log records event 800?

Event 800 is written to the Microsoft-Windows-PowerShell/Operational channel by Microsoft-Windows-PowerShell. Enable PowerShell Module Logging and Script Block Logging via GPO (Administrative Templates → Windows PowerShell).

How do you detect activity around event 800?

Low priority when 4103/4104 are enabled. Use as fallback for environments without full PowerShell logging.