No description
Find a file
2019-07-31 22:49:01 -04:00
aux Updating submodule(s). 2019-07-29 20:10:58 -07:00
cmake@58e4eebe3a Merge remote-tracking branch 'origin/topic/dnthayer/gh-313' 2019-06-12 15:11:04 -07:00
doc@f3b78d6369 Merge remote-tracking branch 'origin/topic/dev/non-ascii-logging' 2019-07-30 19:42:34 -07:00
man Rename all BRO-prefixed environment variables 2019-05-22 00:12:31 -05:00
scripts Tiny tweaks to try and address ticket #506 2019-07-31 11:17:53 -04:00
src Fixes a tiny Bro->Zeek renaming issue 2019-07-31 14:17:46 -04:00
testing Rename a broxygen unit test to zeekygen 2019-07-31 14:25:22 -07:00
.clang-tidy Add clang-tidy rule to CMake including a base configuration 2019-07-01 12:09:55 -07:00
.gitignore Add CLion directories to gitignore 2019-05-30 16:00:18 -07:00
.gitmodules Initial paraglob integration. 2019-06-04 14:24:51 -07:00
.travis.yml Add release branches to Travis CI whitelist 2019-07-25 23:18:05 -07:00
.update-changes.cfg Add script to update external test repo commit pointers 2019-04-05 17:09:01 -07:00
bro-config.h.in Support old plugins that use files within the source/build tree 2019-07-16 10:10:37 -07:00
bro-path-dev.in Additional Bro to Zeek renaming 2019-05-19 16:51:36 -05:00
CHANGES Rename a broxygen unit test to zeekygen 2019-07-31 14:25:22 -07:00
CMakeLists.txt Abort when --enable-jemalloc is given, but JeMalloc is not found 2019-07-22 10:37:49 -07:00
configure GH-475: Require --enable-perftools to link in tcmalloc 2019-07-19 14:07:19 -07:00
COPYING Update license year for 2018 2018-11-01 13:54:07 -05:00
COPYING.3rdparty Merge remote-tracking branch 'origin/topic/johanna/3rdparty-licenses' 2019-07-30 02:48:10 +00:00
INSTALL Make INSTALL a symlink to doc/install/install.rst 2015-03-13 15:45:20 -05:00
Makefile More bro-to-zeek renaming in scripts and other files 2019-05-16 02:36:41 -05:00
NEWS Merge remote-tracking branch 'origin/topic/dev/non-ascii-logging' 2019-07-30 19:42:34 -07:00
README Fix hello world script in the readme. 2019-07-31 14:43:18 -04:00
README.md Fix the link to "good first issue" tickets. 2019-07-31 22:49:01 -04:00
VERSION Rename a broxygen unit test to zeekygen 2019-07-31 14:25:22 -07:00
zeek-config.h.in Support old plugins that use files within the source/build tree 2019-07-16 10:10:37 -07:00
zeek-config.in Rename directories from bro to zeek 2019-05-24 03:32:14 -05:00
zeek-path-dev.in Rename all BRO-prefixed environment variables 2019-05-22 00:12:31 -05:00
zeek-wrapper.in Fix zeek-wrapper 2019-05-11 19:05:25 -05: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.

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.