CC detecting-lateral-movement-with-zeek
Detect lateral movement in network traffic using Zeek (formerly Bro) log analysis. Parses conn.log, smb_mapping.log, smb_files.log, dce_rpc.log, kerberos.log, and ntlm.log to identify SMB file transfers, NTLM account spray activity, remote service execution, and anomalous internal connections.
Detect lateral movement in network traffic using Zeek (formerly Bro) log analysis.
As a process C 57/100 · Has gaps — weak spots: result and completion, failures and branches, running it twice
How to improve
For the model run — optional
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 20
✓ No critical or high findings
Medium and low: 20
-
low Risky intent
intent-offensive-securityassets/template.md:1Offensive-security / dual-use content (legitimate for authorised testing; review intended use)# Lateral Movement Investigation Checklist
-
low Risky intent
intent-offensive-securityassets/template.md:10Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)| **Detection Source** | Zeek — lateral movement detection |
detector -
low Risky intent
intent-offensive-securityassets/template.md:15Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- [ ] Review Zeek notice.log for lateral movement alerts
-
low Risky intent
intent-offensive-securityassets/template.md:100Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)- [ ] Block lateral movement paths (firewall rules)
detector -
low Risky intent
intent-offensive-securityreferences/api-reference.md:1Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)# API Reference: Detecting Lateral Movement with Zeek
detector -
low Risky intent
intent-offensive-securityreferences/api-reference.md:27Offensive-security / dual-use content (legitimate for authorised testing; review intended use)## Lateral Movement Ports Tracked
-
low Risky intent
intent-offensive-securityreferences/api-reference.md:105Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- MITRE ATT&CK Lateral Movement: https://attack.mitre.org/tactics/TA0008/
-
low Risky intent
intent-offensive-securityreferences/standards.md:3Offensive-security / dual-use content (legitimate for authorised testing; review intended use)## MITRE ATT&CK — Lateral Movement (TA0008)
-
low Risky intent
intent-offensive-securityreferences/standards.md:19Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)- SANS: Detecting Lateral Movement with Zeek
detector -
low Risky intent
intent-offensive-securityreferences/standards.md:20Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)- Red Canary Threat Detection Report — Lateral Movement chapter
detector -
low Risky intent
intent-offensive-securityreferences/workflows.md:1Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)# Detection Workflow — Lateral Movement with Zeek
detector -
low Risky intent
intent-offensive-securityreferences/workflows.md:5Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)This document describes the end-to-end workflow for detecting lateral movement using Zeek network logs, from data collection through investigation and response.
detector -
low Risky intent
intent-offensive-securityreferences/workflows.md:103Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- Identify initial compromise, lateral movement, and objectives
-
low Risky intent
intent-offensive-securityreferences/workflows.md:109Offensive-security / dual-use content (legitimate for authorised testing; review intended use)| Confirmed lateral movement | Isolate affected hosts from network |
-
low Risky intent
intent-offensive-securityreferences/workflows.md:143Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- Test with red team exercises quarterly
-
low Risky intent
intent-offensive-securitySKILL.md:3Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)description: 'Detect lateral movement in network traffic using Zeek (formerly Bro)
detector -
low Risky intent
intent-offensive-securitySKILL.md:34Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)# Detecting Lateral Movement with Zeek
detector -
low Risky intent
intent-offensive-securitySKILL.md:36Offensive-security / dual-use content (legitimate for authorised testing; review intended use)Analyze Zeek network logs to identify lateral movement techniques including
-
low Risky intent
intent-offensive-securitySKILL.md:43Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- Hunting for lateral movement after an initial compromise indicator is found on one endpoint
-
low Risky intent
intent-offensive-securitySKILL.md:66Offensive-security / dual-use content (legitimate for authorised testing; review intended use)Confirm that Zeek is producing the required log files for lateral movement detection:
Files scanned: 8. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "domain" - note
frontmatter-keyunknown frontmatter key "subdomain" - note
frontmatter-keyunknown frontmatter key "nist_csf" - note
frontmatter-keyunknown frontmatter key "mitre_attack"
Process rating: all ten parameters 57/100
- 0Result and completion. Does not say what the result is
- 0Failures and branches. Linear process with no failure handling
- 30Running it twice. 5 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 19 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1765 tokens
- 100Progress reporting. Reports progress
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +3Output format is not stated: the model decides each time
- -43 reference files, but SKILL.md never points to them: the model will not open them
- -31 of 2 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 294: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 19 items
- +4Has examples (8 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.