Back to catalog
Static reviewDevelopment

Skill dossier

detecting-network-anomalies-with-zeek

Source declaration

Deploy and configure Zeek (formerly Bro) to passively analyze network traffic, generate structured connection/DNS/HTTP/SSL/file logs, detect anomalous behavior, and write custom scripts for organization-specific threats. Use for passive monitoring at network choke points, feeding SIEM/threat hunting with protocol metadata, or retrospective log analysis during incident response; not a substitute for inline IDS/IPS or host agents.

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

Deploy and configure Zeek (formerly Bro) to passively analyze network traffic, generate structured connection/DNS/HTTP/SSL/file logs, detect anomalous behavior, and write custom scripts for organization-specific threats. Use for passive monitoring at network choke points, feeding SIEM/threat hunting with protocol metadata, or retrospective log analysis during incident response; not a substitute for inline IDS/IPS or host agents.

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.

Deploy and configure Zeek (formerly Bro) to passively analyze network traffic, generate structured connection/DNS/HTTP/SSL/file logs, detect anomalous behavior, and write custom scripts for organization-specific threats. Use for passive monitoring at network choke points, feeding SIEM/threat hunting with protocol metadata, or retrospective log analysis during incident response; not a substitute for inline IDS/IPS or host agents. 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-network-anomalies-with-zeek/SKILL.md:L46]
  • Step 1: Install and Configure Zeek [Source statement; provisional, not tested. Evidence: skills/detecting-network-anomalies-with-zeek/SKILL.md:L48]
  • Step 2: Understand and Navigate Zeek Logs [Source statement; provisional, not tested. Evidence: skills/detecting-network-anomalies-with-zeek/SKILL.md:L94]
  • Step 3: Write Custom Detection Scripts [Source statement; provisional, not tested. Evidence: skills/detecting-network-anomalies-with-zeek/SKILL.md:L122]
  • Step 4: Load Custom Scripts and Deploy [Source statement; provisional, not tested. Evidence: skills/detecting-network-anomalies-with-zeek/SKILL.md:L236]
  • Step 5: Threat Hunting Queries on Zeek Logs [Source statement; provisional, not tested. Evidence: skills/detecting-network-anomalies-with-zeek/SKILL.md:L270]
  • Step 6: Integrate with SIEM and Set Up Alerting [Source statement; provisional, not tested. Evidence: skills/detecting-network-anomalies-with-zeek/SKILL.md:L301]

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-network-anomalies-with-zeek/SKILL.md:L1-L25]

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.8 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/detecting-network-anomalies-with-zeek/LICENSEOther11 KB
skills/detecting-network-anomalies-with-zeek/references/api-reference.mdReference2.5 KB
skills/detecting-network-anomalies-with-zeek/scripts/agent.pyScript11.1 KB
skills/detecting-network-anomalies-with-zeek/SKILL.mdInstruction14.1 KB

SKILL.md frontmatter

{
  "name": "detecting-network-anomalies-with-zeek",
  "description": "Deploy and configure Zeek (formerly Bro) to passively analyze network traffic, generate structured connection/DNS/HTTP/SSL/file logs, detect anomalous behavior, and write custom scripts for organization-specific threats. Use for passive monitoring at network choke points, feeding SIEM/threat hunting with protocol metadata, or retrospective log analysis during incident response; not a substitute for inline IDS/IPS or host agents.",
  "domain": "cybersecurity",
  "subdomain": "network-security",
  "tags": [
    "network-security",
    "zeek",
    "network-monitoring",
    "anomaly-detection",
    "threat-hunting"
  ],
  "version": "1.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "nist_csf": [
    "PR.IR-01",
    "DE.CM-01",
    "ID.AM-03",
    "PR.DS-02"
  ],
  "mitre_attack": [
    "T1046",
    "T1040",
    "T1557",
    "T1071"
  ]
}

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: Install and Configure Zeek

    Source-described action candidate under “Step 1: Install and Configure Zeek”; not verified execution.

  4. 04
    Action

    Step 2: Understand and Navigate Zeek Logs

    Source-described action candidate under “Step 2: Understand and Navigate Zeek Logs”; not verified execution.

  5. 05
    Output

    Step 3: Write Custom Detection Scripts

    Source-described output candidate under “Step 3: Write Custom Detection Scripts”; not verified execution.

  6. 06
    Action

    Create a script for detecting DNS tunneling:

    Source-described action candidate under “Step 3: Write Custom Detection Scripts”; not verified execution.

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

    Create a script for detecting beaconing:

    Source-described action candidate under “Step 3: Write Custom Detection Scripts”; not verified execution.

  2. 08
    Input

    Step 4: Load Custom Scripts and Deploy

    Source-described input candidate under “Step 4: Load Custom Scripts and Deploy”; not verified execution.

  3. 09
    Action

    Step 5: Threat Hunting Queries on Zeek Logs

    Source-described action candidate under “Step 5: Threat Hunting Queries on Zeek Logs”; not verified execution.

  4. 10
    Action

    Step 6: Integrate with SIEM and Set Up Alerting

    Source-described action candidate under “Step 6: Integrate with SIEM and Set Up Alerting”; not verified execution.

  5. 11
    Action

    Key Concepts

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

  6. 12
    Action

    Tools & Systems

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

  7. 13
    Action

    Common Scenarios

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

  8. 14
    Action

    Deploy Zeek on a network tap at the internet egress point with AFPACKET for high-throughput capture

    Source-described action candidate under “Scenario: Detecting Command-and-Control Beaconing in Enterprise Traffic”; not verified execution.

  9. 15
    Action

    Enable the custom beacon detection script with thresholds tuned for 60-second intervals over 1-hour observation windows

    Source-described action candidate under “Scenario: Detecting Command-and-Control Beaconing in Enterprise Traffic”; not verified execution.

  10. 16
    Action

    Query conn.log for connections to external IPs with consistent duration and inter-connection timing: filter connections where the standard deviation of inter-arrival times is less than 5 seconds

    Source-described action candidate under “Scenario: Detecting Command-and-Control Beaconing in Enterprise Traffic”; not verified execution.

  11. 17
    Action

    Cross-reference suspicious destination IPs against threat intelligence feeds loaded into Zeek's Intel framework

    Source-described action candidate under “Scenario: Detecting Command-and-Control Beaconing in Enterprise Traffic”; not verified execution.

  12. 18
    Action

    Examine ssl.log for the associated TLS certificates -- check for self-signed certificates, unusual issuer names, or certificates with short validity periods

    Source-described action candidate under “Scenario: Detecting Command-and-Control Beaconing in Enterprise Traffic”; not verified execution.

  13. 19
    Input

    Generate a notice for each identified beaconing source and feed into the SIEM for SOC triage

    Source-described input candidate under “Scenario: Detecting Command-and-Control Beaconing in Enterprise Traffic”; not verified execution.

  14. 20
    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

61 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 useObserved
Medium

Network access is mentioned

4 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 4 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.

High

Elevated privileges are referenced

17 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 17 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

Credential or secret material is referenced

This line resembles a credential literal or reads a sensitive environment value. Do not expose its contents; verify whether it is a placeholder, required secret, or accidentally committed material. This rule matched 1 location(s) in the collected text; 1 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-network-anomalies-with-zeek/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-network-anomalies-with-zeek/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-network-anomalies-with-zeek
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.