![]() The added test cases around function/event invocations report the following flurry of errors when only the first one is relevant and actionable. There's little use in reporting a mismatch with "error". Squelch them. error in <...>/function-invoke-mismatch-error.zeek, line 8: identifier not defined: MyEnumTypo error in <...>/function-invoke-mismatch-error.zeek, line 12 and error: type mismatch (M::MY_ENUM_A and error) error in <...>/function-invoke-mismatch-error.zeek, line 12: argument type mismatch in function call (M::to_string(M::MY_ENUM_A)) error in <...>/function-invoke-mismatch-error.zeek, line 16 and error: type mismatch (M::MY_ENUM_B and error) error in <...>/function-invoke-mismatch-error.zeek, line 16: argument type mismatch in function call (M::to_string(M::MY_ENUM_B)) error in <...>/function-invoke-mismatch-error.zeek, line 20 and error: type mismatch (M::e and error) error in <...>/function-invoke-mismatch-error.zeek, line 20: argument type mismatch in function call (M::to_string(M::e)) Record coercion also reports noisy errors when coercing to a type that has errors for individual fields, type clashing with "error": $ zeek language/record-field-error.zeek error in ./language/record-coerce-error.zeek, line 8: identifier not defined: MyEnumTypo error in ./language/record-coerce-error.zeek, line 19 and ./language/record-coerce-error.zeek, line 5: type clash for field "e" ((coerce [$e=MY_ENUM_B, $s=test] to MyRecord) and MyEnum) |
||
---|---|---|
.github/workflows | ||
auxil | ||
ci | ||
cmake@f69e08247e | ||
doc@9c204e8133 | ||
docker | ||
man | ||
scripts | ||
src | ||
testing | ||
.cirrus.yml | ||
.clang-format | ||
.clang-tidy | ||
.dockerignore | ||
.git-blame-ignore-revs | ||
.gitattributes | ||
.gitignore | ||
.gitmodules | ||
.pre-commit-config.yaml | ||
.style.yapf | ||
.update-changes.cfg | ||
CHANGES | ||
CMakeLists.txt | ||
configure | ||
COPYING | ||
COPYING-3rdparty | ||
INSTALL | ||
Makefile | ||
NEWS | ||
README | ||
README.md | ||
VERSION | ||
zeek-config.h.in | ||
zeek-config.in | ||
zeek-path-dev.in | ||
zkg-config.in |
The Zeek Network Security Monitor
A powerful framework for network traffic analysis and security monitoring.
Key Features — Documentation — Getting Started — Development — License
Follow us on Twitter at @zeekurity.
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.