Zeek

Zeek (formerly Bro)[2] is a free and open-source software network analysis framework; it was first developed in 1994 by Vern Paxson and was originally named in reference to George Orwell's Big Brother from his novel Nineteen Eighty-Four. It can be used as a network intrusion detection system (NIDS) but with additional live analysis of network events.[3] It is released under the BSD license.

Zeek
Original author(s)Vern Paxson
Stable release
3.1.5 / July 27, 2020 (2020-07-27)[1]
Repository
Written inC++
Operating systemLinux, FreeBSD, macOS
TypeNetwork intrusion detection system
LicenseBSD license
Websitezeek.org

Zeek's application architecture

IP packets captured with pcap are transferred to an event engine which accepts or rejects them. The accepted packets are forwarded to the policy script interpreter.

The event engine analyzes live or recorded network traffic or trace files to generate neutral events. It generates events when "something" happens. This can be triggered by the Zeek process, such as just after initialization or just before termination of the Zeek process, as well as by something taking place on the network (or trace file) being analyzed, such as Zeek witnessing an HTTP request or a new TCP connection. Zeek uses common ports and dynamic protocol detection (involving signatures as well as behavioral analysis) to make a best guess at interpreting network protocols. Events are policy neutral in that they are not good or bad but simply signals to script land that something happened.

Events are handled by policy scripts, which analyze events to create action policies. The scripts are written in the Turing complete Zeek scripting language. By default Zeek simply logs information about events to files (Zeek also supports logging events in binary output); however, it can be configured to take other actions such as sending an email, raising an alert, executing a system command, updating an internal metric and even calling another Zeek script. The default behavior produces NetFlow-like output (conn log) as well as application event information. Zeek scripts are able to read in data from external files, such as blacklists, for use within Zeek policy scripts.

Zeek analyzers

Most Zeek analyzers are located in Zeek's event engine with an accompanying policy script. The policy script can be customized by the user. The analyzers perform application layer decoding, anomaly detection, signature matching and connection analysis.[4] Zeek has been designed to easily incorporate additional analyzers. Some application layer analyzers included with Zeek are HTTP, FTP, SMTP and DNS amongst others. Other non-application layer analyzers include analyzers that detect host or port scans, intermediary hosts and syn-floods. Zeek also includes signature detection and allows the import of Snort signatures.

gollark: That would be <#471334670483849216>, yes.
gollark: I decided to avoid going to the US a while ago because apparently border control is frequently quite awful, among other things.
gollark: Quite often.
gollark: I'm pretty sure there's *tons* of other random surveillance laws, and the NSA seems to just blatantly ignore the law.
gollark: Yes.

References
  1. "Releases - zeek/zeek". Retrieved 27 July 2020 – via GitHub.
  2. Paxson, Vern (11 October 2018). "Renaming the Bro Project".
  3. McCarty, Ronald. "Bro IDS » ADMIN Magazine". ADMIN Magazine. Retrieved 2018-07-11.
  4. Sommer, Robin (2003). "Bro: An Open Source Network Intrusion Detection System". Munich, Germany: Computer Science Department TU München. CiteSeerX 10.1.1.60.5410. Cite journal requires |journal= (help)
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.