![]()
Some checks are pending
pre-commit / pre-commit (push) Waiting to run
* origin/topic/timw/merge-3rdparty-repo-into-main: (30 commits) Ignore src/3rdparty for pre-commit src/3rdparty: Port doctest fix for including <ciso646> from upstream src/3rdparty: Update doctest to v2.4.12 src/3rdparty: Move jthread/stop_token out of std namespace to prevent collisions src/3rdparty: Fix clang-tidy bugprone-casting-through-void warning src/3rdparty: Add jthread and stop_token headers src/3rdparty: Update SQLite to 3.47.1 src/3rdparty: Upgrade sqlite3 to 3.45.0 src/3rdparty: modp: Disable deprecation warning for sprintf src/3rdparty: Update SQLite to 3.41.2 src/3rdparty: Handle zeek-inet-ntop snprintf() return value correctly src/3rdparty: Rework inet-ntop change to build on Windows src/3rdparty: Use snprintf in zeek_inet_ntop.c to silence macOS compiler warnings src/3rdparty: Use snprintf in patricia.cc to silence macOS compiler warnings src/3rdparty: Update ConvertUTF Unicode license as per request from LLVM upstream src/3rdparty: Update doctest to 2.4.9 and sqlite to 3.39.4 src/3rdparty: Fix rampant off-by-one error in last change src/3rdparty: numeric conversion functions now return the number of characters added src/3rdparty: Fix GCC 12.2 warning in access to patricia_t members src/3rdparty: Rebase patricia.{h,c} on upstream version ... |
||
---|---|---|
.github/workflows | ||
auxil | ||
ci | ||
cmake@d51c699044 | ||
cmake_templates | ||
doc@2731def915 | ||
docker | ||
man | ||
scripts | ||
src | ||
testing | ||
tools | ||
.cirrus.yml | ||
.clang-format | ||
.clang-tidy | ||
.cmake-format.json | ||
.dockerignore | ||
.git-blame-ignore-revs | ||
.gitattributes | ||
.gitignore | ||
.gitmodules | ||
.pre-commit-config.yaml | ||
.typos.toml | ||
.update-changes.cfg | ||
CHANGES | ||
CMakeLists.txt | ||
CODE_OF_CONDUCT.md | ||
configure | ||
CONTRIBUTING.md | ||
COPYING | ||
COPYING-3rdparty | ||
INSTALL | ||
Makefile | ||
NEWS | ||
README | ||
README.md | ||
ruff.toml | ||
SECURITY.md | ||
vcpkg.json | ||
VERSION | ||
zeek-path-dev.in |
The Zeek Network Security Monitor
A powerful framework for network traffic analysis and security monitoring.
Key Features — Documentation — Getting Started — Development — License
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.
- Clang-Tidy
- Coverity
- PVS-Studio - static analyzer for C, C++, C#, and Java code.