No description
Find a file
2024-05-16 13:48:02 -07:00
.github/workflows github/generate-docs: Only commit if there are staged changes 2024-03-18 09:35:28 +01:00
auxil Updating CHANGES and VERSION, and bump Spicy and docs. 2024-05-07 10:03:17 +02:00
ci Revert "Install gcc9 on CentOS Stream 8" 2024-05-02 19:12:03 -07:00
cmake@1d793368ac Make sure that vcpkg isn't preferred if pcap_root_dir is passed in 2024-04-11 15:25:49 -07:00
cmake_templates Update version used by spicyz 2024-04-17 14:16:58 -07:00
doc@3ecd2d62d0 Update doc submodule [nomail] [skip ci] 2024-05-08 00:19:30 +00: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 Merge remote-tracking branch 'origin/topic/christian/private_address_clarification' 2024-05-07 10:26:50 -07:00
src bug fixes 2024-05-16 13:48:02 -07:00
testing better printing of expressions 2024-05-16 13:45:11 -07:00
.cirrus.yml Add Opensuse leap 15.6 to CI 2024-04-16 10:00:01 +01: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 Drop zeek-archiver submodule 2024-04-19 12:10:52 -07:00
.pre-commit-config.yaml Format JSON with clang-format 2023-10-30 09:41:13 +01:00
.style.yapf Format Python scripts with yapf. 2021-11-24 23:13:24 +01:00
.typos.toml retention of superseded AST elements to prevent pointer mis-aliasing 2023-11-10 11:06:16 +01: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/3417-packet-analysis-detail' 2024-05-08 09:55:16 -07:00
CMakeLists.txt Remove zeek-archiver from build config, deprecate --disable-archiver in configure 2024-04-19 12:10:55 -07:00
configure Remove zeek-archiver from build config, deprecate --disable-archiver in configure 2024-04-19 12:10:55 -07: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 Fix usage of realpath on macOS, instead preferring grealpath 2023-06-13 15:51:47 -07:00
NEWS Merge remote-tracking branch 'origin/topic/robin/gh-3440-file-handles' 2024-05-07 09:44:41 +02: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 Merge remote-tracking branch 'origin/topic/timw/3417-packet-analysis-detail' 2024-05-08 09:55:16 -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.