Skip to content
Back to skills

Zeek Conn Log Analysis

ASecurity

Analyze Zeek (formerly Bro) `conn.log` files to hunt for malicious network behaviors, including C2 beaconing, long-lived anomalous connections, and data exfiltration patterns.

  • 22 stars
  • 0 votes
  • 0 copies
  • 4 views
  • Added September 12, 2026
ai-agentsgoshellbashgitsecuritydocumentation

Security analysis

A100/100

Pro scans all 3 files and shows the line behind each finding

Scanned September 12, 2026

npx -y skills add ShulkwiSEC/bb-huge --skill zeek-conn-log-analysis --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Zeek Conn Log Analysis?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Zeek Conn Log Analysis
[![Security: A β€” Skills Directory](https://www.skillsdirectory.com/api/skills/shulkwisec-zeek-conn-log-analysis/badge)](https://www.skillsdirectory.com/skills/shulkwisec-zeek-conn-log-analysis)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: zeek-conn-log-analysis
description: >
  Analyze Zeek (formerly Bro) `conn.log` files to hunt for malicious network behaviors, 
  including C2 beaconing, long-lived anomalous connections, and data exfiltration patterns.
domain: cybersecurity
subdomain: incident-response
category: Forensics
difficulty: intermediate
estimated_time: "2 hours"
mitre_attack:
  tactics: [TA0011, TA0010]
  techniques: [T1071, T1043]
platforms: [network, linux]
tags: [zeek, network-forensics, threat-hunting, dfir, c2-beaconing, packet-analysis]
tools: [zeek, awk, zeek-cut, jq]
version: "1.0"
author: CyberSkills-Elite
license: Apache-2.0
---

# 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

```bash
# 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)

```bash
# 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)

```bash
# 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

```bash
# 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 πŸ”€
```mermaid
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`](../_shared/references/elite-chaining-strategy.md) β€” Exploit chaining methodology and high-payout chain patterns
> - [`_shared/references/elite-report-writing.md`](../_shared/references/elite-report-writing.md) β€” HackerOne-optimized report writing, CWE quick reference
> - [`_shared/references/real-world-bounties.md`](../_shared/references/real-world-bounties.md) β€” Verified disclosed bounties by vulnerability class

## References
- Zeek Documentation: [Logging Framework](https://docs.zeek.org/en/current/frameworks/logging.html)
- Active Countermeasures: [RITA (Real Intelligence Threat Analytics)](https://github.com/activecm/rita)

Files in this skill

  • SKILL.md4.1 KB
  • evals/evals.json530 B
  • scripts/process.py7.8 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.