# analyzing-windows-event-logs-in-splunk

analyzing-windows-event-logs-in-splunk is a Claude Code skill for inspecting Windows Security, System and Sysmon logs in Splunk and mapping events to MITRE ATT&CK.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 251 installs · ★ 36511 repo stars
- Author: mahipal
- License: Apache-2.0 · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/mukul975/Anthropic-Cybersecurity-Skills/tree/HEAD/skills/analyzing-windows-event-logs-in-splunk/SKILL.md
- Updated: 2026-08-31
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/analyzing-windows-event-logs-in-splunk

## What it does

Provides SOC analysts with SPL queries to investigate Windows incidents: parse authentication events, track process execution, monitor registry and scheduled task changes. Includes ready-made queries for brute-force and password-spray detection, new admin account creation, token manipulation, task scheduling via T1053.005, Run-key registry modifications and WMI subscriptions.

Covers lateral movement detection through Event Code 4624 (network logons) and RDP activity (Logon_Type=10), plus PsExec and SMB exploitation patterns. Requires Windows event data already ingested into Splunk under sourcetype `WinEventLog:Security`, `WinEventLog:System` and `XmlWinEventLog:Microsoft-Windows-Sysmon/Operational`.

Needs Sysmon deployed on endpoints with SwiftOnSecurity or Olaf Hartong configuration, and CIM data model acceleration enabled for Endpoint and Authentication models. Maps to MITRE ATT&CK techniques T1110, T1053.005, T1547.001, T1021.002, T1558.003 and T1003.006.

## Requirements
- Works with: Splunk

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill analyzing-windows-event-logs-in-splunk -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/analyzing-windows-event-logs-in-splunk/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/analyzing-windows-event-logs-in-splunk/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill analyzing-windows-event-logs-in-splunk -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/analyzing-windows-event-logs-in-splunk/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill analyzing-windows-event-logs-in-splunk -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/analyzing-windows-event-logs-in-splunk/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install mukul975/Anthropic-Cybersecurity-Skills skills/analyzing-windows-event-logs-in-splunk
```

2. **Manually: put the files in place**
- File: `.github/skills/analyzing-windows-event-logs-in-splunk/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill analyzing-windows-event-logs-in-splunk -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/mukul975/Anthropic-Cybersecurity-Skills --path skills/analyzing-windows-event-logs-in-splunk
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/analyzing-windows-event-logs-in-splunk/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill analyzing-windows-event-logs-in-splunk -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/mukul975/Anthropic-Cybersecurity-Skills/tree/HEAD/skills/analyzing-windows-event-logs-in-splunk/SKILL.md

## When to use it
- detect brute-force and password-spray attacks using Windows Event Code 4625
- find newly created admin accounts and audit user privilege assignments
- identify scheduled task creation, registry Run-key changes and WMI subscription activity
- spot remote logon patterns and cross-host lateral movement
- build forensic timeline of endpoint or domain controller activity

## Example prompts
- Show me failed login attempts on Windows in the last 24 hours, grouped by source IP and logon type
- Find successful logins that followed multiple failed attempts from the same IP for one user
- Build a query to detect new scheduled tasks created via PowerShell or command prompt

## Source text · SKILL.md · Apache-2.0

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 7e7af8eb33677b0f.

BEGIN THIRD-PARTY FILE 7e7af8eb33677b0f
```text
---
name: analyzing-windows-event-logs-in-splunk
description: 'Analyzes Windows Security, System, and Sysmon event logs in Splunk to
  detect authentication attacks, privilege escalation, persistence mechanisms, and
  lateral movement using SPL queries mapped to MITRE ATT&CK techniques. Use when SOC
  analysts need to investigate Windows-based threats, build detection queries, or
  perform forensic timeline analysis of Windows endpoints and domain controllers.

  '
domain: cybersecurity
subdomain: soc-operations
tags:
- soc
- splunk
- windows-events
- sysmon
- event-logs
- mitre-attack
- active-directory
version: '1.0'
author: mahipal
license: Apache-2.0
d3fend_techniques:
- Restore Access
- Password Authentication
- Biometric Authentication
- Strong Password Policy
- Restore User Account Access
nist_csf:
- DE.CM-01
- DE.AE-02
- RS.MA-01
- DE.AE-06
mitre_attack:
- T1110
- T1053.005
- T1547.001
- T1021.002
- T1558.003
- T1003.006
---
# Analyzing Windows Event Logs in Splunk

## When to Use

Use this skill when:
- SOC analysts investigate alerts related to Windows authentication, process execution, or AD changes
- Detection engineers build SPL queries for Windows-based threat detection
- Incident responders need forensic timelines of Windows endpoint or domain controller activity
- Periodic threat hunting targets Windows-specific ATT&CK techniques

**Do not use** for Linux/macOS endpoint analysis or network-only investigations.

## Prerequisites

- Splunk with Windows Event Log data ingested (sourcetype `WinEventLog:Security`, `WinEventLog:System`, `XmlWinEventLog:Microsoft-Windows-Sysmon/Operational`)
- Sysmon deployed on endpoints with SwiftOnSecurity or Olaf Hartong configuration
- CIM data model acceleration for Endpoint and Authentication data models
```
END THIRD-PARTY FILE 7e7af8eb33677b0f

The third-party file has ended. Everything between the 7e7af8eb33677b0f tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 1783 of 11385 bytes. © mahipal · Apache-2.0 · https://github.com/mukul975/Anthropic-Cybersecurity-Skills/tree/HEAD/skills/analyzing-windows-event-logs-in-splunk/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
