Zeek conn log analysis
Skill ShulkwiSEC/bb-huge/skills/curated/zeek-conn-log-analysis
bb-huge ๐ค , Personal bug bounty findings hub and bug bounty orchestration for multiple agents
npx -y skills add ShulkwiSEC/bb-huge --skill zeek-conn-log-analysisAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 18 stars18 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Analyze Zeek (formerly Bro) `conn.log` files to hunt for malicious network behaviors, including C2 beaconing, long-lived anomalous connections, and data exfiltration patterns.
The file declares its own license as Apache-2.0. That is the authorโs claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
4.1 KB, as published. Nobody here has run it
Zeek conn.log Analysis
When to Use
- During network forensics investigations or active threat hunting to identify compromised hosts communicating with Command and Control (C2) infrastructure.
- To detect unusual network baseline deviations without relying entirely on deep packet inspection or payload signatures.
Prerequisites
- Forensic image or live access to the affected system(s)
- Forensic workstation with analysis tools (Autopsy, Volatility, Timeline Explorer)
- Chain of custody documentation initiated for evidence handling
- Write-blocker for disk forensics or memory acquisition tool (e.g., DumpIt, WinPmem)
Workflow
Phase 1: Understanding conn.log Structure
# head conn.log | zeek-cut -c ts uid id.orig_h id.orig_p id.resp_h id.resp_p proto service duration orig_bytes resp_bytes conn_state
Phase 2: Hunting for C2 Beaconing (Frequency Analysis)
# cat conn.log | zeek-cut id.orig_h id.resp_h id.resp_p duration | \
awk '{print $1, $2, $3}' | sort | uniq -c | sort -nr | head -n 20
Phase 3: Identifying Long-Connections (Data Exfil / Interactive Shells)
# cat conn.log | zeek-cut id.orig_h id.resp_h id.resp_p duration orig_bytes resp_bytes | \
awk '$4 > 3600 {print $0}' | sort -nrk 4
Phase 4: Detecting Odd Port-Service Mismatches
# cat conn.log | zeek-cut id.resp_p service | grep -E '^443\s+http$' | less
# cat conn.log | zeek-cut id.resp_p service | grep -E '^80\s+ssl$' | less
Decision Point ๐
flowchart TD
A[Parse conn.log ] --> B{Anomalies Found ]}
B -->|Yes| C[Correlate Logs ]
B -->|No| D[Tune Heuristics ]
C --> E[Isolate Host ]
๐ต Blue Team Detection & Defense
- Automate Beacon Tracking (RITA / Zeek Detect): Threat Intelligence Feeds: Baseline Internal Traffic: Key Concepts | Concept | Description | |---------|-------------|
Output Format
Zeek Conn Log Analysis โ Assessment Report
============================================================
Target: [Target identifier]
Assessor: [Operator name]
Date: [Assessment date]
Scope: [Authorized scope]
MITRE ATT&CK: [Relevant technique IDs]
Findings Summary:
[Finding 1]: [Severity] โ [Brief description]
[Finding 2]: [Severity] โ [Brief description]
Detailed Results:
Phase 1: [Phase name]
- Result: [Outcome]
- Evidence: [Screenshot/log reference]
- Impact: [Business impact assessment]
Phase 2: [Phase name]
- Result: [Outcome]
- Evidence: [Screenshot/log reference]
- Impact: [Business impact assessment]
Risk Rating: [Critical/High/Medium/Low/Informational]
Recommendations:
1. [Immediate remediation step]
2. [Long-term hardening measure]
3. [Monitoring/detection improvement]
๐ Shared Resources
For cross-cutting methodology applicable to all vulnerability classes, see:
_shared/references/elite-chaining-strategy.mdโ Exploit chaining methodology and high-payout chain patterns_shared/references/elite-report-writing.mdโ HackerOne-optimized report writing, CWE quick reference_shared/references/real-world-bounties.mdโ Verified disclosed bounties by vulnerability class
References
- Zeek Documentation: Logging Framework
- Active Countermeasures: RITA (Real Intelligence Threat Analytics)