Skip to content
Commitpedia
Log in Join & edit

Zeek: network security monitoring that turns traffic into logs

Zeek, formerly Bro, watches network traffic and writes structured logs of every connection, DNS query, HTTP request and certificate it sees. Analysts search those logs to understand what happened on the network.

Drafted with AI from official documentation. Scripts were run in a test environment and repository links verified. Awaiting a human check. Did it work for you? Last edited Outdated?

Edit history of Zeek: network security monitoring that turns traffic into logs: 1 recorded edit
Edit history · 1 edit
Type
Repo
Edits
1
Editors
1
First issued
15 Oct 2026
Last edit
15 Oct 2026
Source
zeek/zeek

zeek/zeek

Stars
8.1k
Forks
1.4k
Language
C++
Licence
NOASSERTION
Last push
15 Oct 2026

On GitHub: Zeek is a powerful network analysis framework that is much different from the typical IDS you may know.

Open on GitHub

Zeek (about 8,100 stars on GitHub) is an open source network analysis framework that has been in continuous development since Vern Paxson began it at Lawrence Berkeley National Laboratory in 1995. It was called Bro until 2018. Today it is maintained by the Zeek Project under the Linux Foundation with core developers employed by Corelight, a company founded by the original authors, and by research institutions. The code is C++ with a custom scripting language.

What it does

Where a signature based IDS such as Suricata answers the question “did anything known to be bad go past?”, Zeek answers “what exactly happened?”. It passively watches traffic and produces a set of tab separated or JSON log files, one per protocol: conn.log for every connection, dns.log, http.log, ssl.log, files.log and many more. Each line is a compact summary with timestamps, addresses, sizes, durations and protocol specific fields. These logs are small compared with full packet capture but rich enough to reconstruct an incident months later, which is why Zeek is the standard source of network evidence in many security operations centres. Its scripting language lets you add your own analysis, from simple notices to full protocol analysers.

Who it is for

  • Security analysts who need a searchable record of network activity for investigations and threat hunting.
  • Network administrators who want visibility into which services, certificates and software versions are actually in use.
  • Researchers and universities, which have used Zeek for decades as a platform for traffic analysis.
  • Operators of SIEM platforms, since Zeek logs ship directly into Elastic, Splunk, Loki and similar tools.

How to install it

Binary packages are available from the project for Debian, Ubuntu, Fedora, Red Hat based distributions and openSUSE, and Zeek is in Homebrew for macOS. A quick test reads a packet capture file instead of a live interface:

zeek --version
zeek -r capture.pcap
ls *.log

For a permanent sensor the zeekctl tool manages a cluster of workers on one or more machines. The documentation has a getting started guide and a complete log reference. Zeek is also included in Security Onion.

Credit

Zeek was created by Vern Paxson and is maintained by the Zeek Project leadership team and community, with the Linux Foundation as its home. It is released under a BSD style licence; see the COPYING file in the repository.

Did this work for you?

No votes yet. Be the first.

If it did not work, the report form below tells the editors what went wrong.

See also

  • 0193 Linux logs reference: journalctl, journald storage, logrotate and centralized logging Read and filter systemd journal logs, keep their disk use in check, rotate classic log files with logrotate, and understand when to… Intermediate · Cheat sheet · Linux Article Linux administration · Logs 15 Oct 2026
  • 0291 What is a log? A log is a running record of what a program did and when, written to a file so you can look back… Beginner · Explains an idea · Any system Article Logs 15 Oct 2026
  • 0323 Fix: Failed to start service, how to read systemctl status and journalctl Job for x.service failed tells you only that the service did not start. The real reason is in systemctl status and journalctl… Beginner · Fixes an error · Linux Article Logs · Services & systemd 15 Oct 2026
  • 0371 Where are the logs? journalctl, /var/log and container logs A practical map of where Linux programs write their logs and the commands to read them: journalctl filters, the classic files under… Beginner · Step by step · Linux Article Logs 15 Oct 2026
  • 0373 Loki: ship and search logs Run Loki, Grafana Alloy and Grafana with Docker Compose, collect the systemd journal and /var/log files with a short Alloy configuration, and… Intermediate · Step by step · Linux Article Logs 15 Oct 2026
  • 0432 Try Sigma rules against your own logs Install the sigma-cli converter, take a rule from the public SigmaHQ library, convert it into a query for a log tool you… Intermediate · Step by step · Linux, macOS Article Logs · Security resources & detection 15 Oct 2026

History

Every saved edit is kept. The plot on the sleeve draws one line per edit. Open any edit to see exactly what changed.

  1. Dominik +2,431 chars

Report a problem

Something wrong, unsafe or copied? Tell the editors.
What is wrong?