windows-ir

Detect Windows intrusions and document findings with incident response workflows.

1|1|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/chenchunrun/onyx-soc --skill windows-ir
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: windows-ir
Source: https://github.com/chenchunrun/onyx-soc/tree/main/skills/windows-ir
Command: npx skills add https://github.com/chenchunrun/onyx-soc --skill windows-ir

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires psutil, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Windows IR often requires rapid detection and forensic analysis across many endpoints to identify intrusions, preserve evidence, and guide containment.

Core Features & Use Cases

  • Phase-driven checks for log, process, and persistence analysis
  • Webshell detection workflow with references to efficiency
  • Automated reporting and evidence gathering for incident response playbooks

Quick Start

Run the Windows IR investigation workflow across endpoints by loading the included scripts and references.

Frequently Asked Questions about windows-ir

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect Windows intrusions through log analysis and process hunting?

Windows intrusion detection is performed through phase-driven checks for log, process, and persistence analysis. The workflow applies script-assisted automation to identify malicious activity and document findings with structured incident response playbooks.

What is the best way to check for persistence mechanisms on Windows endpoints during an incident response?

Checking for persistence mechanisms on Windows endpoints is handled through phase-driven checks within the incident response workflow. This process hunting approach identifies and documents malicious persistence techniques across affected Windows endpoints.

How do I detect webshells on Windows servers during threat hunting?

Webshell detection on Windows servers is executed using a dedicated workflow within the incident response process. This threat hunting workflow provides references to efficiently identify webshell activity and document findings for reporting.

Can I use psutil for process hunting and evidence collection across Windows endpoints?

Yes, psutil supports process hunting and evidence collection across Windows endpoints. The Skill leverages this dependency to automate script-assisted incident response tasks, gathering forensic evidence for structured reporting.

How do I automate incident response reporting and evidence gathering for Windows security incidents?

Automated incident response reporting and evidence gathering is achieved by loading the included scripts and references. This automates the collection and documentation of forensic findings into structured playbooks for Windows security incidents.

What are the limitations of phase-driven incident response workflows for Windows forensics?

The phase-driven workflow focuses specifically on Windows-based intrusions, log analysis, and process hunting. It requires the psutil dependency and is designed for incident responders performing endpoint forensics rather than real-time continuous monitoring.