detecting-lateral-movement-with-splunk

mukul975/Anthropic-Cybersecurity-Skills · updated May 25, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills install mukul975/Anthropic-Cybersecurity-Skills/detecting-lateral-movement-with-splunk
0 commentsdiscussion
summary

Detect adversary lateral movement across networks using Splunk SPL queries against Windows authentication logs, SMB traffic, and remote service abuse.

skill.md
name
detecting-lateral-movement-with-splunk
description
Detect adversary lateral movement across networks using Splunk SPL queries against Windows authentication logs, SMB traffic, and remote service abuse.
domain
cybersecurity
subdomain
threat-hunting
tags
- threat-hunting - mitre-attack - lateral-movement - splunk - siem - proactive-detection - ta0008
version
'1.0'
author
mahipal
license
Apache-2.0
d3fend_techniques
- Application Protocol Command Analysis - Network Isolation - Network Traffic Analysis - Client-server Payload Profiling - Network Traffic Community Deviation
nist_csf
- DE.CM-01 - DE.AE-02 - DE.AE-07 - ID.RA-05

Detecting Lateral Movement with Splunk

When to Use

  • When hunting for adversary movement between compromised systems
  • After detecting credential theft to trace subsequent lateral activity
  • When investigating unusual authentication patterns across the network
  • During incident response to scope the breadth of compromise
  • When proactively hunting for TA0008 (Lateral Movement) techniques

Prerequisites

  • Splunk Enterprise or Splunk Cloud with Windows event data ingested
  • Windows Security Event Logs forwarded (4624, 4625, 4648, 4672, 4768, 4769)
  • Sysmon deployed for process creation and network connection data
  • Network flow data or firewall logs for SMB/RDP/WinRM correlation
  • Active Directory user and group membership reference data

Workflow

  1. Define Lateral Movement Scope: Identify which lateral movement techniques to hunt (RDP, SMB/Admin Shares, WinRM, PsExec, WMI, DCOM, SSH).
  2. Query Authentication Events: Use SPL to search for Type 3 (Network) and Type 10 (RemoteInteractive) logons across the environment.
  3. Build Authentication Graphs: Map source-to-destination authentication relationships to identify unusual connection patterns.
  4. Detect First-Time Relationships: Identify new source-destination pairs that have not been seen in the historical baseline.
  5. Correlate with Process Activity: Link authentication events to subsequent process creation on destination hosts.
  6. Identify Anomalous Patterns: Flag lateral movement to sensitive servers, unusual hours, service account misuse, or rapid multi-host access.
  7. Report and Contain: Document lateral movement path, affected systems, and coordinate containment response.

Key Concepts

ConceptDescription
T1021Remote Services (parent technique)
T1021.001Remote Desktop Protocol (RDP)
T1021.002SMB/Windows Admin Shares
T1021.003Distributed COM (DCOM)
T1021.004SSH
T1021.006Windows Remote Management (WinRM)
T1570Lateral Tool Transfer
T1047Windows Management Instrumentation
T1569.002Service Execution (PsExec)
Logon Type 3Network logon (SMB, WinRM, mapped drives)
Logon Type 10Remote Interactive (RDP)
Event ID 4624Successful logon
Event ID 4648Explicit credential logon (runas, PsExec)

Tools & Systems

ToolPurpose
Splunk EnterpriseSIEM for log aggregation and SPL queries
Splunk Enterprise SecurityThreat detection and notable events
Windows Event ForwardingCentralize Windows logs
SysmonDetailed process and network telemetry
BloodHoundAD attack path analysis
PingCastleAD security assessment

Common Scenarios

  1. PsExec Lateral Movement: Adversary uses PsExec to execute commands on remote systems via SMB, generating Type 3 logon with ADMIN$ share access.
  2. RDP Pivoting: Attacker RDPs to internal systems using stolen credentials, creating Type 10 logon events.
  3. WMI Remote Execution: Adversary uses WMIC process call create to spawn processes on remote hosts.
  4. WinRM PowerShell Remoting: Attacker uses Enter-PSSession or Invoke-Command to execute code on remote systems.
  5. Pass-the-Hash via SMB: Compromised NTLM hashes used to authenticate to remote systems without knowing the plaintext password.

Output Format

Hunt ID: TH-LATMOV-[DATE]-[SEQ]
Movement Type: [RDP/SMB/WinRM/WMI/DCOM/PsExec]
Source Host: [Hostname/IP]
Destination Host: [Hostname/IP]
Account Used: [Username]
Logon Type: [3/10/other]
First Seen: [Timestamp]
Event Count: [Number of events]
Risk Level: [Critical/High/Medium/Low]
Lateral Movement Path: [A -> B -> C -> D]
how to use detecting-lateral-movement-with-splunk

How to use detecting-lateral-movement-with-splunk on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add detecting-lateral-movement-with-splunk
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills install mukul975/Anthropic-Cybersecurity-Skills/detecting-lateral-movement-with-splunk

The skills CLI fetches detecting-lateral-movement-with-splunk from GitHub repository mukul975/Anthropic-Cybersecurity-Skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/detecting-lateral-movement-with-splunk

Reload or restart Cursor to activate detecting-lateral-movement-with-splunk. Access the skill through slash commands (e.g., /detecting-lateral-movement-with-splunk) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

Task Automation & Efficiency

Automate repetitive workflows and reduce manual effort

Example

Generate reports, summarize documents, draft communications

Save 3-5 hours per week on routine tasks

Knowledge Enhancement

Learn new skills, understand complex topics, get expert guidance

Example

Explain concepts, provide examples, suggest learning resources

Accelerate learning and skill development by 2x

Quality Improvement

Enhance output quality through reviews, suggestions, and refinements

Example

Review drafts, suggest improvements, catch errors

Improve work quality by 30-40% with less effort

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client with skill support
  • Clear understanding of task or problem to solve
  • Willingness to iterate and refine outputs

Time Estimate

15-45 minutes depending on use case complexity

Installation Steps

  1. 1.Install skill using provided installation command
  2. 2.Test with simple use case relevant to your work
  3. 3.Evaluate output quality and relevance
  4. 4.Iterate on prompts to improve results
  5. 5.Integrate into regular workflow if valuable

Common Pitfalls

  • Expecting perfect results without iteration
  • Not providing enough context in prompts
  • Using skill for tasks outside its intended scope
  • Accepting outputs without review and validation

Best Practices

✓ Do

  • +Start with clear, specific prompts
  • +Provide relevant context and constraints
  • +Review and refine all outputs before using
  • +Iterate to improve output quality
  • +Document successful prompt patterns

✗ Don't

  • Don't use without understanding skill limitations
  • Don't skip validation of outputs
  • Don't share sensitive information in prompts
  • Don't expect skill to replace human judgment

💡 Pro Tips

  • Be specific about desired format and style
  • Ask for multiple options to choose from
  • Request explanations to understand reasoning
  • Combine AI efficiency with human expertise

When to Use This

✓ Use When

Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.

✗ Avoid When

Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.

Learning Path

  1. 1Familiarize yourself with skill capabilities and limitations
  2. 2Start with low-risk, non-critical tasks
  3. 3Progress to more complex and valuable use cases
  4. 4Build expertise through regular use and experimentation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.669 reviews
  • Mia Flores· Dec 16, 2024

    Useful defaults in detecting-lateral-movement-with-splunk — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Dhruvi Jain· Dec 12, 2024

    Useful defaults in detecting-lateral-movement-with-splunk — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • William Ramirez· Dec 12, 2024

    Keeps context tight: detecting-lateral-movement-with-splunk is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Hana Singh· Dec 12, 2024

    detecting-lateral-movement-with-splunk is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Hiroshi White· Dec 4, 2024

    detecting-lateral-movement-with-splunk is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Diego Chawla· Dec 4, 2024

    detecting-lateral-movement-with-splunk reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Aarav Bansal· Nov 27, 2024

    We added detecting-lateral-movement-with-splunk from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Anaya Abebe· Nov 27, 2024

    detecting-lateral-movement-with-splunk fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Anaya Lopez· Nov 23, 2024

    detecting-lateral-movement-with-splunk reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Meera Okafor· Nov 23, 2024

    detecting-lateral-movement-with-splunk is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

showing 1-10 of 69

1 / 7