Back to catalog
Static reviewDevelopment

Skill dossier

detecting-lateral-movement-in-network

Source declaration

Identifies lateral movement techniques in enterprise networks by analyzing authentication logs, network flows, SMB traffic, and RDP sessions using Zeek, Velociraptor, and SIEM correlation rules to detect attackers moving between systems.

The author's original description, preserved in English. It describes intent, not verified performance.

Identifies lateral movement techniques in enterprise networks by analyzing authentication logs, network flows, SMB traffic, and RDP sessions using Zeek, Velociraptor, and SIEM correlation rules to detect attackers moving between systems.

developmentreferencesscripts

Research summary

Machine-generated analysis; pending human review

These observations come from deterministic source parsing, not a human security review or controlled task evaluation.

Identifies lateral movement techniques in enterprise networks by analyzing authentication logs, network flows, SMB traffic, and RDP sessions using Zeek, Velociraptor, and SIEM correlation rules to detect attackers moving between systems. This bilingual summary is generated deterministically from collected source text and file structure; it is pending human editorial review.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Workflow [Source statement; provisional, not tested. Evidence: skills/detecting-lateral-movement-in-network/SKILL.md:L57]
  • Step 1: Configure Log Collection for Lateral Movement Detection [Source statement; provisional, not tested. Evidence: skills/detecting-lateral-movement-in-network/SKILL.md:L59]
  • Step 2: Build Detection Rules for Common Lateral Movement Techniques [Source statement; provisional, not tested. Evidence: skills/detecting-lateral-movement-in-network/SKILL.md:L115]
  • Step 3: Network-Level Detection with Zeek [Source statement; provisional, not tested. Evidence: skills/detecting-lateral-movement-in-network/SKILL.md:L183]
  • Step 4: Threat Hunting for Lateral Movement Indicators [Source statement; provisional, not tested. Evidence: skills/detecting-lateral-movement-in-network/SKILL.md:L271]
  • Step 5: Automated Response and Containment [Source statement; provisional, not tested. Evidence: skills/detecting-lateral-movement-in-network/SKILL.md:L318]
  • Step 6: Build Detection Dashboard [Source statement; provisional, not tested. Evidence: skills/detecting-lateral-movement-in-network/SKILL.md:L349]

Limitations & scope

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Relevant for

  • Practitioners evaluating whether to inspect and install the source skill; this audience is inferred from the product context, not measured usage. [Evidence: skills/detecting-lateral-movement-in-network/SKILL.md:L1-L36]

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
4
Markdown files
2
scripts
1
references
1
Size
38.2 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/detecting-lateral-movement-in-network/LICENSEOther11 KB
skills/detecting-lateral-movement-in-network/references/api-reference.mdReference2.7 KB
skills/detecting-lateral-movement-in-network/scripts/agent.pyScript7.9 KB
skills/detecting-lateral-movement-in-network/SKILL.mdInstruction16.6 KB

SKILL.md frontmatter

{
  "name": "detecting-lateral-movement-in-network",
  "description": "Identifies lateral movement techniques in enterprise networks by analyzing authentication logs, network flows, SMB traffic, and RDP sessions using Zeek, Velociraptor, and SIEM correlation rules to detect attackers moving between systems.\n",
  "domain": "cybersecurity",
  "subdomain": "network-security",
  "tags": [
    "network-security",
    "lateral-movement",
    "threat-detection",
    "siem",
    "pass-the-hash"
  ],
  "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": [
    "PR.IR-01",
    "DE.CM-01",
    "ID.AM-03",
    "PR.DS-02"
  ],
  "mitre_attack": [
    "T1046",
    "T1040",
    "T1557",
    "T1071",
    "T1021"
  ]
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Decision

    When to Use

    Source-described decision candidate under “When to Use”; not verified execution.

  2. 02
    Action

    Workflow

    Source-described action candidate under “Workflow”; not verified execution.

  3. 03
    Action

    Step 1: Configure Log Collection for Lateral Movement Detection

    Source-described action candidate under “Step 1: Configure Log Collection for Lateral Movement Detection”; not verified execution.

  4. 04
    Action

    Step 2: Build Detection Rules for Common Lateral Movement Techniques

    Source-described action candidate under “Step 2: Build Detection Rules for Common Lateral Movement Techniques”; not verified execution.

  5. 05
    Action

    Step 3: Network-Level Detection with Zeek

    Source-described action candidate under “Step 3: Network-Level Detection with Zeek”; not verified execution.

  6. 06
    Action

    Step 4: Threat Hunting for Lateral Movement Indicators

    Source-described action candidate under “Step 4: Threat Hunting for Lateral Movement Indicators”; not verified execution.

Inspect all extracted workflow candidates (19 candidate steps)
  1. 07
    Action

    Step 5: Automated Response and Containment

    Source-described action candidate under “Step 5: Automated Response and Containment”; not verified execution.

  2. 08
    Action

    Step 6: Build Detection Dashboard

    Source-described action candidate under “Step 6: Build Detection Dashboard”; not verified execution.

  3. 09
    Action

    Key Concepts

    Source-described action candidate under “Key Concepts”; not verified execution.

  4. 10
    Action

    Tools & Systems

    Source-described action candidate under “Tools & Systems”; not verified execution.

  5. 11
    Action

    Common Scenarios

    Source-described action candidate under “Common Scenarios”; not verified execution.

  6. 12
    Input

    Query Splunk for Event ID 7045 (service creation) on 10.10.20.15 to confirm PsExec execution and identify the source IP (10.10.5.23)

    Source-described input candidate under “Scenario: Detecting a Ransomware Operator's Lateral Movement”; not verified execution.

  7. 13
    Action

    Trace authentication history for 10.10.5.23: find Event ID 4624 Type 3 logons, discovering the host authenticated to 8 servers in the past hour using NTLM (pass-the-hash pattern)

    Source-described action candidate under “Scenario: Detecting a Ransomware Operator's Lateral Movement”; not verified execution.

  8. 14
    Action

    Check Zeek conn.log for 10.10.5.23: identify SMB connections (port 445) to 12 internal hosts and large file transfers to an external IP

    Source-described action candidate under “Scenario: Detecting a Ransomware Operator's Lateral Movement”; not verified execution.

  9. 15
    Action

    Build the attack timeline: initial compromise via phishing at 1:15 AM, credential dumping at 1:25 AM, lateral movement to 8 servers between 1:30-2:00 AM

    Source-described action candidate under “Scenario: Detecting a Ransomware Operator's Lateral Movement”; not verified execution.

  10. 16
    Action

    Identify all compromised hosts by tracing authentication chains: 10.10.5.23 -> 10.10.20.15 -> 10.10.20.16 -> 10.10.20.17

    Source-described action candidate under “Scenario: Detecting a Ransomware Operator's Lateral Movement”; not verified execution.

  11. 17
    Action

    Contain by quarantining all identified hosts to VLAN 999, disabling the compromised account, and blocking the external C2 IP

    Source-described action candidate under “Scenario: Detecting a Ransomware Operator's Lateral Movement”; not verified execution.

  12. 18
    Output

    Report the complete attack chain with timeline, affected hosts, and detection gaps

    Source-described output candidate under “Scenario: Detecting a Ransomware Operator's Lateral Movement”; not verified execution.

  13. 19
    Output

    Output Format

    Source-described output candidate under “Output Format”; not verified execution.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Attention recommended

48 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useNot observed
Medium

Network access is mentioned

3 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 3 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Elevated privileges are referenced

6 occurrences

Privilege-elevation syntax is present. Confirm whether elevation is necessary and inspect every operation performed under it; static analysis cannot prove that elevation succeeded. This rule matched 6 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

39 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 39 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
Inspect the pinned source at https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/detecting-lateral-movement-in-network/SKILL.md and follow the source repository's installation instructions. No installation was performed or verified by this static analyzer. Source license: Apache-2.0.

Prerequisites

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Example prompts

Not provided

A decision, with its limits attached

Strengths

  • The snapshot contains 4 collected file(s), 2 Markdown file(s), and 1 script file(s), enabling source-level inspection. [Evidence: skills/detecting-lateral-movement-in-network/SKILL.md:L1]

Considerations

  • No functional, security, or model-quality result has been established. Human review must inspect source context and all cited findings before installation or publication.
Research conclusion

Provisional deterministic static inventory only; pending human editorial review and, separately, controlled evaluation. No install recommendation, security assurance, or effectiveness claim is made.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

mukul975Anthropic-Cybersecurity-Skillsskills/detecting-lateral-movement-in-network
Source type
Community
Commit
54a798831d2266a3ca61ce68a7acb80b81160d57
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
Apache-2.0
Repository stars
36,446
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.