ZEEK(8)
π ZEEK(8) π
System Administration Utilities β¨ β okay bestie, this is the manual page for zeek(8), and we are gonna get you fluent in it, no cap.
πΈ NAME πΈ
zeek β your passive network traffic analyzer, and honestly? she's the main character of network security.
β¨ SYNOPSIS β¨
zeek [options] [file ...]
π¦ DESCRIPTION π¦
So like, Zeek is primarily a security monitor β she inspects all traffic on a link, in depth, looking for signs of suspicious activity. That's her whole vibe. But ngl, that's not all she does: Zeek supports a wide range of traffic analysis tasks even outside the security domain, including performance measurements and helping with trouble-shooting. Versatile queen π
Zeek comes with built-in functionality for a range of analysis and detection tasks, and here's the list, no skipping:
- detecting malware by interfacing to external registries
- reporting vulnerable versions of software seen on the network
- identifying popular web applications
- detecting SSH brute-forcing
- validating SSL certificate chains
- among others
β οΈ Real talk though: you must have the necessary permissions to access the files or interfaces specified. No permissions, no vibes. π
π OPTIONS π
<file>β policy file, or read stdin. Your call, bestie.
-a,--parse-onlyβ exit immediately after parsing scripts. Like, parse and dip. π«Ά-b,--bare-modeβ don't load scripts from thebase/directory. Strip it down, minimal aesthetic.-d,--debug-policyβ activate policy file debugging. π-e,--exec <zeek code>β augment loaded policies by given code.-f,--filter <filter>β tcpdump filter.-h,--help|-?β command line help. We love a helpful icon.-i,--iface <interface>β read from given interface.-p,--prefix <prefix>β add given prefix to policy file resolution.-r,--readfile <readfile>β read from given tcpdump file.-s,--rulefile <rulefile>β read rules from given file.-t,--tracefile <tracefile>β activate execution tracing.-w,--writefile <writefile>β write to given tcpdump file.-v,--versionβ print version and exit. Short and sweet, periodt.-x,--print-state <file.bst>β print contents of state file.-C,--no-checksumsβ okay so when this option is set, Zeek ignores invalid packet checksums and does process the packets. Furthermore, if this option is set Zeek also processes IP packets with a zero total length field, which is typically caused by TCP (TCP Segment Offloading) on the NIC. π€-F,--force-dnsβ force DNS.-I,--print-id <ID name>β print out given ID.-N,--print-pluginsβ print available plugins and exit (-NNfor verbose). Double the N, double the tea β-P,--prime-dnsβ prime DNS.-Q,--timeβ print execution time summary to stderr.-R,--replay <events.bst>β replay events. it's giving time travel π°οΈ-S,--debug-rulesβ enable rule debugging.-T,--re-level <level>β set'RE_level'for rules.-U,--status-file <file>β Record process status in file.-W,--watchdogβ activate watchdog timer. she's watching πΆ-X,--zeekygen <cfgfile>β generate documentation based on config file.--pseudo-realtime[=<speedup>]β enable pseudo-realtime for performance evaluation (default1).--load-seeds <file>β load seeds from given file.--save-seeds <file>β save seeds to given file.
The following option is available only when Zeek is built with the --enable-debug configure option:
-B,--debug <dbgstreams>β Enable debugging output for selected streams ('-B help'for help).
The following options are available only when Zeek is built with gperftools support (use the --enable-perftools and --enable-perftools-debug configure options):
-m,--mem-leaksβ show leaks.-M,--mem-profileβ record heap.
π ENVIRONMENT π
ZEEKPATHβ file search path.ZEEK_PLUGIN_PATHβ plugin search path.ZEEK_PLUGIN_ACTIVATEβ plugins to always activate.ZEEK_PREFIXESβ prefix list.ZEEK_DNS_FAKEβ disable DNS lookups.ZEEK_SEED_FILEβ file to load seeds from.ZEEK_LOG_SUFFIXβ ASCII log file extension.ZEEK_PROFILER_FILEβ Output file for script execution statistics.ZEEK_DISABLE_ZEEKYGENβ Disable Zeekygen (Broxygen) documentation support.
π OUTPUT FORMAT π
Output is written in multiple files depending on configuration. The default location is the current directory. π
The output written by Zeek can be formatted in multiple ways using the logging framework.
The default are files in human-readable (ASCII) format. The data is organized into columns (tab-delimited). The data can be processed using, e.g., the zeek-cut tool. Slay.
β EXAMPLES β
Read a capture file and generate the default logs:
# zeek -r test-capture.pcap
When running on live traffic, Zeek is usually started by running zeekctl. To configure Zeek with an initial configuration, install, and restart:
# zeekctl deploy
π Note: the zeekctl configuration may need to be updated before first use. Especially the network interface used should be the correct one. (Check it twice, bestie, fr fr.)
π SEE ALSO π
πΈ AUTHOR πΈ
zeek was written by The Zeek Project <info@zeek.org>.
okay that's the whole page, you ate that π
β this was zeek, from the System Administration Utilities manual, dated November 2014, version vibes included. Go forth and analyze some traffic, bestie π¦β¨
π¦ where this page comes from
- epel 9: zeek-core 4.2.0-1.el9 Β· ASL 2.0 and Boost and BSD and ISC and LGPLv3+ and MIT and NCSA
- fedora 43: zeek-core 6.0.4-1.fc41 Β· BSD-3-Clause AND Apache-2.0 AND BSL-1.0 AND ISC AND LGPL-3.0-or-later AND MIT AND NCSA
- fedora 44: zeek-core 6.0.4-1.fc41 Β· BSD-3-Clause AND Apache-2.0 AND BSL-1.0 AND ISC AND LGPL-3.0-or-later AND MIT AND NCSA
- nixos 26.05: zeek 8.0.10
- nixpkgs unstable: zeek 8.2.2
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms