No description
Find a file
Tim Wojtulewicz cd356ce45d Add zeek-namespaced alias for jthread
Apple Clang (as of version 17.0.0) does not support jthread unless
you enable experimental libcpp features by defining
_LIBCPP_ENABLE_EXPERIMENTAL or passing -fexperimental_library to
the compiler. Even if you don't do those, our 3rdparty jthread
library fails to build because of a bunch of namespace/naming
collisions. I moved our 3rdparty one to the `nonstd` namespace, and
am using an alias under __APPLE__ to avoid the collisions.
2025-07-10 14:07:07 -07:00
.github/workflows CI: Add PR label for skipping all CI jobs 2025-05-30 10:29:02 -07:00
auxil Update submodules to C++20-enabled versions 2025-07-10 14:07:07 -07:00
ci Stop suppressing stdout during Zeekygen docs generation 2025-06-05 17:12:16 -07:00
cmake@53a2d51b25 Update submodules to C++20-enabled versions 2025-07-10 14:07:07 -07:00
cmake_templates Deprecate BRO_PLUGIN_INSTALL_PATH constant 2025-06-23 08:35:25 -07:00
doc@5a385599ce Update doc submodule [nomail] [skip ci] 2025-07-10 00:18:59 +00:00
docker docker: Add net-tools and procps dependencies 2025-06-06 09:17:01 +02:00
man Use the same rules as cmake submodule to reformat Zeek 2023-05-09 08:31:43 -07:00
scripts Modify known-services policy script to add storage framework support 2025-07-10 08:55:01 -07:00
src Add zeek-namespaced alias for jthread 2025-07-10 14:07:07 -07:00
testing Modify known-services policy script to add storage framework support 2025-07-10 08:55:01 -07:00
.cirrus.yml Enable Spicy SSL analyzer in nightly CI job against Spicy HEAD 2025-06-18 11:00:18 +02:00
.clang-format Update COPYING date to now and fix some [skip CI] 2025-01-09 08:38:45 -05:00
.clang-tidy Make clang-tidy warnings report as errors to cause CI build to fail 2025-06-30 14:19:06 -07:00
.cmake-format.json Always break lines when formatting spicy_add_analyzer 2025-03-03 11:24:20 +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 IXWebSocket: Point at upstream, bump to v11.4.6 2025-05-15 16:37:09 +02:00
.pre-commit-config.yaml Bump spicy-format pre-commit hook 2025-07-09 11:40:25 +02:00
.typos.toml scripts: Use tpe instead of type_, again 2025-07-03 20:25:34 +02:00
.update-changes.cfg Add script to update external test repo commit pointers 2019-04-05 17:09:01 -07:00
CHANGES Merge remote-tracking branch 'origin/topic/timw/known-services-with-storage-framework' 2025-07-10 08:55:49 -07:00
CMakeLists.txt Include RequireCXXStd.cmake from main CMakeLists.txt 2025-07-10 14:07:07 -07:00
CODE_OF_CONDUCT.md Add code of conduct and contributing to repo. 2025-03-06 13:11:17 +00:00
configure Deprecate --with-binpac/--with-bifcl configure options 2025-06-24 12:50:35 -07:00
CONTRIBUTING.md Add code of conduct and contributing to repo. 2025-03-06 13:11:17 +00:00
COPYING Update COPYING date to now and fix some [skip CI] 2025-01-09 08:38:45 -05:00
COPYING-3rdparty COPYING-3rdparty: Add some missing submodules [skip ci] 2025-04-23 14:57:51 +02:00
INSTALL Update documentation to include "Book of Zeek" revisions 2021-02-01 15:54:36 -08:00
Makefile Fix warning about grealpath when running 'make dist' on Linux 2024-07-11 13:45:14 -07:00
NEWS Merge branch 'topic/jgras/connection-packet-threshold' of https://github.com/J-Gras/zeek 2025-07-08 17:54:27 +02:00
README Add tooling section to README 2023-01-27 13:03:52 -07:00
README.md Fix dead links in README 2025-02-17 08:32:04 -07:00
ruff.toml Swap pre-commit yapf for ruff/ruff-format, fix findings 2024-12-11 11:08:37 -07:00
SECURITY.md Add SECURITY.md, pointing at the website 2025-01-13 08:21:28 -07:00
vcpkg.json Switch all of the conan configuration to vcpkg 2024-02-02 14:52:16 -07:00
VERSION Merge remote-tracking branch 'origin/topic/timw/known-services-with-storage-framework' 2025-07-10 08:55:49 -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.