Securitynik on 2020-06-13 20:32:28
In the SANS SEC503 Intrusion Detection in Depth
class, we teach you quite a lot to get you started with Zeek Network Security Monitoring
. One of the things we cannot do because of time, is walk you through the installation, upgrading, etc., of Zeek. In this post, we help you to install Zeek 3.1.4, the current version as of this writing on Ubuntu 20.04. The hope is with the knowledge we provide to you in the SEC 503
class as well as what you get here, you are in a better position to maximize your Zeek deployment.
First, let us confirm my version of Ubuntu. As seen below, I am running Ubuntu 20.04 LTS.
securitynik@securitynik-zeek:~$ lsb_release --all
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 20.04 LTS
Next, let us install Zeek's dependencies. As we are using Ubuntu, we need the following dependencies:
Let's install them by using:
securitynik@securitynik-zeek:~$sudo apt-get install cmake make gcc g++ flex bison libpcap-dev libssl-dev python-dev swig zlib1g-dev
Let's now install an optional dependency. Specifically, we will install libmaxminddb
(for geolocating IP addresses). To make the most of this, you will need to register with MaxMind
before you can download the GeoIP dataset. Once registered and logged in, download the GeoLite2 City
Once downloaded, you may need to copy the file to the remote machine running Zeek. In my example, I downloaded the file on a Windows system, then used SCP to transfer it to the device running Zeek.
If you don't wish to use geo-data, feel free to skip this step.
securitynik@securitynik-zeek:~$ sudo apt-get install libmaxminddb-dev
Copy the GeoIP data file from Windows 10 system to the system running Zeek, using the native SCP client in Windows 10.
C:\Users\securitynik\Downloads>scp GeoLite2-City_20200609.tar.gz email@example.com:~/
GeoLite2-City_20200609.tar gz 100% 29MB 10.4MB/s 00:02
Once the file is on the system running Zeek, we then extract the files:
securitynik@securitynik-zeek:~$ tar --extract --verbose --gunzip --file GeoLite2-City_20200609.tar.gz
Next copy the GeoLite2-City_20200609/GeoLite2-City.mmdb into the /usr/share/GeoIP folder. In my case I had to create this folder.
securitynik@securitynik-zeek:~$ sudo mkdir --parents /usr/share/GeoIP
securitynik@securitynik-zeek:~$ sudo cp GeoLite2-City_20200609/GeoLite2-City.mmdb /usr/share/GeoIP/
Once the dependencies have been installed successfully, we then transition to the Zeek installation. For our install, we use the latest version at the time of this writing from Zeek's GitHub page.
securitynik@securitynik-zeek:~$ git clone --recursive https://github.com/zeek/zeek
Upon completion of the cloning, we then change directory (cd) into the zeek directory. Once we changed into the zeek directory, we then specify "--with-geoip" argument for the configure script so as to customize our installation. In this example, we are pointing it to the previously created folder which holds or geo-data file.
securitynik@securitynik-zeek:~/zeek$ cd zeek/
securitynik@securitynik-zeek:~/zeek$ ./configure --with-geoip=/usr/share/GeoIP
If everything went ok, you may see something similar to:
====================| Zeek Build Summary |====================
Build type: RelWithDebInfo
Build dir: /home/nik/zeek/build
Install prefix: /usr/local/zeek
Zeek Script Path: /usr/local/zeek/share/zeek
Debug mode: false
CFLAGS: -Wall -Wno-unused -O2 -g -DNDEBUG
CXXFLAGS: -Wall -Wno-unused -Wno-register -Werror=vla -std=c++17 -O2 -g -DNDEBUG
Aux. Tools: true
gperftools found: false
-- Configuring done
-- Generating done
-- Build files have been written to: /home/nik/zeek/build
Next up, make and make install Zeek. Grab a quick coffee, beer or Guinness. Basically whatever you drink as depending on your system resources, this may take a while to complete.
securitynik@securitynik-zeek:~/zeek$ sudo make
securitynik@securitynik-zeek:~/zeek$ sudo make install
Now that the install has completed, test to see if zeek can be executed.
Looks like zeek is not in the path. Let's add a symbolic link and verify Zeek is now in the path
securitynik@securitynik-zeek:~$ sudo ln --symbolic /usr/local/zeek/bin/zeek /usr/bin/zeek
securitynik@securitynik-zeek:~$ which zeek
Looks good! Similarly, let's setup a symbolic link for zeekctl
securitynik@securitynik-zeek:~$ sudo ln --symbolic /usr/local/zeek/bin/zeekctl /usr/bin/zeekctl
securitynik@securitynik-zeek:~$ which zeekctl
While the above is cool, we need to make this a bit more permanent. More importantly, there are other files in the /usr/local/zeek/bin/ directory such as zeek-cut that we more than likely need to use. Thus adding all of these symbolic links may not be the best use of our time. Let's address this by first modifying the path.
securitynik@securitynik-zeek:~$ export PATH=$PATH:/usr/local/zeek/bin
securitynik@securitynik-zeek:~$ echo $PATH
This now allows us to access the other binaries in the /usr/local/zeek/bin/ directory such as zeek-cut
Let's now make it permanent.
securitynik@securitynik-zeek:~$ echo "export PATH=$PATH:/usr/local/zeek/bin" >> .bashrc
securitynik@securitynik-zeek:~$ tail --lines 1 .bashrc
At this point you should be able to execute Zeek with its default configuration in standalone mode. However, for us, let move away from the defaults.
First edit the networks.cfg using your favourite editor (vi, nano, gedit, mousepad, etc.), to ensure it reflects your protected network(s). Here is what mine looks like.
securitynik@securitynik-zeek:/usr/local/zeek/etc$ cat networks.cfg
# List of local networks in CIDR notation, optionally followed by a
# descriptive tag.
# For example, "10.0.0.0/8" or "fe80::/64" are valid prefixes.
#10.0.0.0/8 Private IP space
#172.16.0.0/12 Private IP space
192.168.0.0/24 SecurityNik Protected Network
For demonstration purposes, I commented out 10.0.0.0/8 and 172.16.0.0/12 networks and left the 192.168.0.0/16. I also changed the description to suit my needs. You should also add any other networks you have to this file.
Once that is completed, you should then configure the node.cfg file. Here is what mine looks like. I commented out the standalone section to simulate a distributed deployment. Everything is on one host but the host has two interfaces. One of those is the loopback and the other enp0s25. Note, you don't really need to do it the way I did. I am only doing it this way to demonstrate how you can use different workers on different systems and or interfaces.
## Below is an example clustered configuration. If you use this,
## remove the [zeek] node above.
Once you have modified your node.cfg to reflect your configuration needs, your next step is to make any necessary changes to your zeekctl.cfg. At a minimum in this file you may want to change the recipient email address. Here is a snapshot of my file:
securitynik@securitynik-zeek:/usr/local/zeek/etc$ cat zeekctl.cfg | more
## Global ZeekControl configuration file.
# Mail Options
# Recipient address for all emails sent out by Zeek and ZeekControl.
MailTo = firstname.lastname@example.org
At this point, we should be good to go. Once you modify your files, you should deploy your changes. Let's do that.
securitynik@securitynik-zeek:/usr/local/zeek/etc$ sudo zeekctl deploy
checking configurations ...
removing old policies in /usr/local/zeek/spool/installed-scripts-do-not-touch/site ...
removing old policies in /usr/local/zeek/spool/installed-scripts-do-not-touch/auto ...
creating policy directories ...
installing site policies ...
generating cluster-layout.zeek ...
generating local-networks.zeek ...
generating zeekctl-config.zeek ...
generating zeekctl-config.sh ...
stopping workers ...
stopping proxy ...
stopping manager ...
starting manager ...
starting proxy ...
starting workers ...
Looks like everything started properly. Let's confirm this:
securitynik@securitynik-zeek:/usr/local/zeek/etc$ sudo zeekctl status
Name Type Host Status Pid Started
securitynik-zeek-manager manager 192.168.0.4 running 207505 13 Jun 14:13:33
securitynik-zeek-proxy proxy 192.168.0.4 running 207554 13 Jun 14:13:35
securitynik-zeek-worker-enp0s25 worker 192.168.0.4 running 207624 13 Jun 14:13:37
securitynik-zeek-worker-lo worker localhost running 207621 13 Jun 14:13:37
Looks like we are good to go. To further confirm, let's see if any logs are being created.
securitynik@securitynik-zeek:/usr/local/zeek/etc$ ls ../logs/current
broker.log conn.log files.log loaded_scripts.log reporter.log stats.log stdout.log weird.log
cluster.log dns.log http.log packet_filter.log ssl.log stderr.log syslog.log x509.log
Nice. Looks like we are making progress.
Finally, you may wish to have Zeek start as a service via Systemd. Let's make that happen.
Create a file name zeek.zervice and verify its existence as follow.
securitynik@securitynik-zeek:~$ sudo touch /etc/systemd/system/zeek.service
securitynik@securitynik-zeek:~$ ls /etc/systemd/system/zeek.service*
Next edit the file and add the following contents:
securitynik@securitynik-zeek:~$ sudo vi /etc/systemd/system/zeek.service
securitynik@securitynik-zeek:~$ cat /etc/systemd/system/zeek.service
Description=Zeek Network Security Monitoring
securitynik@securitynik-zeek:~$ sudo systemctl daemon-reload
Enable the zeek service (zeek.zervice)
securitynik@securitynik-zeek:~$ sudo systemctl enable --now zeek.service
Created symlink /etc/systemd/system/multi-user.target.wants/zeek.service → /etc/systemd/system/zeek.service.
securitynik@securitynik-zeek:~$ sudo systemctl start zeek.service
Looks like the Zeek service started without errors. Let's confirm the service is now running.
securitynik@securitynik-zeek:~$ systemctl status zeek.service
Loaded: loaded (/etc/systemd/system/zeek.service; enabled; vendor preset: enabled)
Active: inactive (dead) since Sat 2020-06-13 14:42:21 EDT; 1min 26s ago
Process: 215455 ExecStart=/usr/bin/zeekctl start (code=exited, status=0/SUCCESS)
Main PID: 215455 (code=exited, status=0/SUCCESS)
Tasks: 50 (limit: 2225)
├─215481 /usr/bin/bash /usr/local/zeek/share/zeekctl/scripts/run-zeek -1 -U .status -p zeekctl -p zeekctl->
├─215487 /usr/local/zeek/bin/zeek -U .status -p zeekctl -p zeekctl-live -p local -p securitynik-zeek-manager lo>
├─215533 /usr/bin/bash /usr/local/zeek/share/zeekctl/scripts/run-zeek -1 -U .status -p zeekctl -p zeekctl->
├─215539 /usr/local/zeek/bin/zeek -U .status -p zeekctl -p zeekctl-live -p local -p securitynik-zeek-proxy loca>
├─215592 /usr/bin/bash /usr/local/zeek/share/zeekctl/scripts/run-zeek -1 -i enp0s25 -U .status -p zeekctl >
├─215600 /usr/bin/bash /usr/local/zeek/share/zeekctl/scripts/run-zeek -1 -i lo -U .status -p zeekctl -p ze>
├─215605 /usr/local/zeek/bin/zeek -i enp0s25 -U .status -p zeekctl -p zeekctl-live -p local -p securitynik-zeek>
└─215609 /usr/local/zeek/bin/zeek -i lo -U .status -p zeekctl -p zeekctl-live -p local -p securitynik-zeek-work>
Jun 13 14:42:14 securitynik systemd: Started zeek.service.
Jun 13 14:42:21 securitynik zeekctl: starting manager ...
Jun 13 14:42:21 securitynik zeekctl: starting proxy ...
Jun 13 14:42:21 securitynik zeekctl: starting workers ...
Jun 13 14:42:21 securitynik systemd: zeek.service: Succeeded.
Above we can see zeek.serviceSuceeded. However, if you look at the Active above, we see Inactive dead. However, I was able to confirm Zeek is running as expected even after stopping Zeek with zeekctl stop. I then restarted the system and run sudo zeekctl status along with systemctl status zeek.service and everything is working as expected.
At this point, I will close off this post. Have fun, stay safe and I look forward to seeing you in one of the upcoming SANS SEC503 Intrusion Detection in Depth
class, where we teach you how to maximize your security monitoring with Zeek.