No description
Find a file
Arne Welzel e712461719 broker/main: Adapt enum values to agree with comm.bif
Logic to detect this error already existed, but due to enum identifiers
not having a value set, it never triggered before.

Should probably backport this one.

(cherry picked from commit 6bc36e8cf8)
2025-05-05 12:54:42 -07:00
.github/workflows Merge remote-tracking branch 'origin/topic/bbannier/fix-docs-ci-again' 2024-10-18 17:15:51 -07:00
auxil Update zeekctl submodule to fix a couple btests 2025-03-19 13:04:31 -07:00
ci CI: Force rebuild of tumbleweed docker image 2025-03-18 16:33:45 -07:00
cmake@a10c95c9df Update cmake submodule [nomail] 2025-05-05 12:16:39 -07:00
cmake_templates Update version used by spicyz 2024-04-17 14:16:58 -07:00
doc@6377b714f2 Update docs submodule to fix RTD [nomail] [skip ci] 2025-03-20 13:48:45 -07:00
docker Update build script 2024-04-17 14:16:55 -07:00
man Use the same rules as cmake submodule to reformat Zeek 2023-05-09 08:31:43 -07:00
scripts broker/main: Adapt enum values to agree with comm.bif 2025-05-05 12:54:42 -07:00
src Merge remote-tracking branch 'origin/topic/awelzel/2311-load-plugin-bare-mode' 2025-03-18 16:16:39 -07:00
testing Update core/vntag-in-vlan baseline to remove ip_proto field for 7.0 2025-03-18 17:03:05 -07:00
.cirrus.yml Merge remote-tracking branch 'origin/topic/timw/ci-macos-sequoia' 2025-03-18 16:21:13 -07:00
.clang-format Format JSON with clang-format 2023-10-30 09:41:13 +01:00
.clang-tidy Disable annoying bugprone-easily-swappable-parameters clang-tidy check [skip ci] 2022-10-07 16:15:47 -07:00
.cmake-format.json Format JSON with clang-format 2023-10-30 09:41:13 +01:00
.dockerignore Add .dockerignore to suppress btest artifacts 2021-09-24 17:04:26 -07:00
.git-blame-ignore-revs Update .git-blame-ignore-revs 2023-10-30 09:42:39 +01:00
.gitattributes GH-1497: Support CRLF line-endings in Zeek scripts and signature files 2021-04-08 20:32:30 -07:00
.gitignore Update .gitignore to add Emacs and Vim temp files 2024-02-07 12:12:58 -07:00
.gitmodules Switch to zeek fork of prometheus-cpp 2024-06-04 14:14:58 -07:00
.pre-commit-config.yaml Merge remote-tracking branch 'origin/topic/vern/ZAM-field-assign-in-op' 2025-03-18 16:13:01 -07:00
.style.yapf Format Python scripts with yapf. 2021-11-24 23:13:24 +01:00
.typos.toml Allowlist a name for typos check 2024-07-31 15:06:47 +02:00
.update-changes.cfg Add script to update external test repo commit pointers 2019-04-05 17:09:01 -07:00
CHANGES broker/main: Adapt enum values to agree with comm.bif 2025-05-05 12:54:42 -07:00
CMakeLists.txt CMakeLists: Ensure Threads::Threads target exists 2024-07-04 15:42:52 +02:00
configure Fix for --display-cmake in configure 2024-07-08 19:24:40 -06:00
COPYING Update COPYING to 2023 2023-01-03 12:10:03 -07:00
COPYING-3rdparty Rename COPYING.3rdparty to COPYING-3rdparty 2023-01-03 12:10:03 -07:00
INSTALL Update documentation to include "Book of Zeek" revisions 2021-02-01 15:54:36 -08:00
Makefile Merge remote-tracking branch 'origin/topic/timw/grealpath-make-dist-warning' 2024-07-12 09:47:38 -07:00
NEWS Update CHANGES, VERSION, and NEWS for 7.0.6 release 2025-03-20 12:24:26 -07:00
README Add tooling section to README 2023-01-27 13:03:52 -07:00
README.md Update link to slack in README.md 2023-06-01 14:21:44 +02:00
vcpkg.json Switch all of the conan configuration to vcpkg 2024-02-02 14:52:16 -07:00
VERSION broker/main: Adapt enum values to agree with comm.bif 2025-05-05 12:54:42 -07:00
zeek-path-dev.in Move CMake template files to separate directory 2023-06-26 13:39:59 -07:00

Zeek Logo

The Zeek Network Security Monitor

A powerful framework for network traffic analysis and security monitoring.

Key FeaturesDocumentationGetting StartedDevelopmentLicense

Follow us on Twitter at @zeekurity.

Coverage Status Build Status

Slack Discourse

Key Features

  • In-depth Analysis Zeek ships with analyzers for many protocols, enabling high-level semantic analysis at the application layer.

  • Adaptable and Flexible Zeek's domain-specific scripting language enables site-specific monitoring policies and means that it is not restricted to any particular detection approach.

  • Efficient Zeek targets high-performance networks and is used operationally at a variety of large sites.

  • Highly Stateful Zeek keeps extensive application-layer state about the network it monitors and provides a high-level archive of a network's activity.

Getting Started

The best place to find information about getting started with Zeek is our web site www.zeek.org, specifically the documentation section there. On the web site you can also find downloads for stable releases, tutorials on getting Zeek set up, and many other useful resources.

You can find release notes in NEWS, and a complete record of all changes in CHANGES.

To work with the most recent code from the development branch of Zeek, clone the master git repository:

git clone --recursive https://github.com/zeek/zeek

With all dependencies in place, build and install:

./configure && make && sudo make install

Write your first Zeek script:

# File "hello.zeek"

event zeek_init()
    {
    print "Hello World!";
    }

And run it:

zeek hello.zeek

For learning more about the Zeek scripting language, try.zeek.org is a great resource.

Development

Zeek is developed on GitHub by its community. We welcome contributions. Working on an open source project like Zeek can be an incredibly rewarding experience and, packet by packet, makes the Internet a little safer. Today, as a result of countless contributions, Zeek is used operationally around the world by major companies and educational and scientific institutions alike for securing their cyber infrastructure.

If you're interested in getting involved, we collect feature requests and issues on GitHub here and you might find these to be a good place to get started. More information on Zeek's development can be found here, and information about its community and mailing lists (which are fairly active) can be found here.

License

Zeek comes with a BSD license, allowing for free use with virtually no restrictions. You can find it here.

Tooling

We use the following tooling to help discover issues to fix, amongst a number of others.