No description
Find a file
Jon Siwek a08b1ff56f Add warning message for unknown Broker statuses
There's now a couple placeholder/unimplemented status values in Broker
related to upcoming routing features that we don't want to handle
explicitly for compatibility reasons, but also don't want the compiler
warning about unhandled values in the switch.
2020-04-29 15:28:18 -07:00
.github/workflows Add branch whitelist for CI notifications 2020-03-13 13:41:46 -07:00
aux Add warning message for unknown Broker statuses 2020-04-29 15:28:18 -07:00
ci Remove Travis CI configuration 2020-02-28 21:17:02 -08:00
cmake@d85153d8e0 Update submodule(s) 2020-04-29 14:25:53 -07:00
doc@e862aa7a89 Merge remote-tracking branch 'origin/topic/jsiwek/gh-854-preserve-header-name' 2020-04-27 19:31:49 +00:00
man Rename all BRO-prefixed environment variables 2019-05-22 00:12:31 -05:00
scripts Merge remote-tracking branch 'origin/topic/jsiwek/gh-854-preserve-header-name' 2020-04-27 19:31:49 +00:00
src Add warning message for unknown Broker statuses 2020-04-29 15:28:18 -07:00
testing Merge remote-tracking branch 'origin/topic/vern/any-typetype-when-fix' 2020-04-27 13:33:40 -07:00
.cirrus.yml Add a 32-bit task to Cirrus CI config 2020-02-14 21:40:36 -08:00
.clang-tidy Change over to whitelisting clang-tidy options instead of blacklisting 2019-08-12 13:59:17 -07:00
.gitattributes Make github identify our Flex source correctly. 2019-08-23 14:27:06 -04:00
.gitignore Add CLion directories to gitignore 2019-05-30 16:00:18 -07:00
.gitmodules Move libkqueue submodule to the aux directory 2020-03-05 19:40:03 -08:00
.update-changes.cfg Add script to update external test repo commit pointers 2019-04-05 17:09:01 -07:00
CHANGES Add warning message for unknown Broker statuses 2020-04-29 15:28:18 -07:00
CMakeLists.txt Move rapidjson submodule to aux directory 2020-03-05 19:24:13 -08:00
configure GH-878: Make RocksDB usage opt-in and add --enable-rocksdb configure flag 2020-03-26 12:18:42 -07:00
COPYING Update license year for 2018 2018-11-01 13:54:07 -05:00
COPYING.3rdparty Merge remote-tracking branch 'origin/topic/timw/faster-hashing' 2020-02-25 19:56:17 -08: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/jsiwek/intrusive-ptr-chipping' 2020-04-24 16:20:08 -07:00
README Fix hello world script in the readme. 2019-07-31 14:43:18 -04:00
README.md Update README.md to fix the logo and one of the links 2020-04-15 13:45:25 -07:00
VERSION Add warning message for unknown Broker statuses 2020-04-29 15:28:18 -07:00
zeek-config.h.in GH-808: Add ZEEK_VERSION_NUMBER definition to zeek-config.h 2020-02-23 09:55:20 +00: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 Merge remote-tracking branch 'origin/topic/robin/631-deprecation-v2' 2020-01-30 19:19:56 -08: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.