Skip to main content

Scripts to display contents of Suricata eve.json log

Project description

SuricataLog

Downloads

When I started learning how to use Suricata quickly found that I needed a tool to inspect the eve.json file; Most of the tutorials and documentation out there suggested installing a stack to do the following tasks:

  1. Store the logs in a central location
  2. Normalize and enrich the events, specially alerts
  3. Use a frontend to dive into the data

Which is very useful, but what if I just needed to do a quick inspection of the events?

Sooner or later you will get bored to death doing this:

cat eve.json | jq -r -c 'select(.event_type=="alert")|.payload'| base64 --decode

SuricataLog is a set of tools/ scripts to parse and display Suricata log files (like /var/log/suricata/eve.json)

The Eve JSON format is not very complex, so I wrote few scripts with the features I tough would be more useful for my home network analysis.

As a bonus, I wrote my learning experience as a tutorial that you can use to learn about Suricata and also how to test it.

Installing from PIP

Before you do anything else, make sure your environment is good to go:

python3 -m venv ~/virtualenv/suricatalog
. ~/virtualenv/suricatalog/bin/activate
python3 -m pip install --upgrade pip setuptools wheel

Installing from Pypi.org

pip3 install --upgrade SuricataLog

Installing from source

git clone git@github.com:josevnz/SuricataLog.git
cd SuricataLog
python3 -m venv ~/virtualenv/suricatalog
. ~/virtualenv/suricatalog/bin/activate
python3 -m pip install --upgrade build
python3 -m build
pip3 install dist/SuricataLog-X.Y.Z-py3-none-any.whl

Developer installation

So you want to contribute? Or found a bug and think you can submit a patch? Nice! Here is what you can dd to run on development mode:

git clone git@github.com:josevnz/SuricataLog.git
cd SuricataLog
python3 -m venv ~/virtualenv/suricatalog
. ~/virtualenv/suricatalog/bin/activate
pip install --upgrade pip
python -m pip install --upgrade build
pip install textual-dev
pip install --editable .

Running unit tests is very easy after that:

(SuricataLog) [josevnz@dmaf5 SuricataLog]$ python -m unittest test/*.py
.........
----------------------------------------------------------------------
Ran 9 tests in 0.334s

OK

If the unit tests fails, then this is most likely the first place to fix a problem.

I do recommend also running the textualize console and watch for the console messages:

# textual console
textual console --exclude SYSTEM --exclude EVENT

Then on another terminal:

textual run --dev --command eve_log --timestamp '2015-01-01 10:41:21.642899' test/eve.json

That will print even debug messages on the console (you can exclude these if you restart the console with '--exclude DEBUG')

Creating a Docker image

Please check DOCKER.md for more details.

Running the scripts

Once everything is installed in your virtual environment you should be able to call the scripts

You can find out what applications got installed by using auto complete, after activating your virtual environment:

eve_[tab][tab]

And if you install the Bash auto complete extension you will also get some suggestions for the flags.

Simple EVE log parser

Better see it by yourself (remember, use --help to learn what options are supported)

Table format:

suricatalog-eve_log-table.png

eve_log --timestamp '2015-01-01 10:41:21.642899' --formats TABLE test/eve.json

Canned reports with eve_json.py

(suricatalog) [josevnz@dmaf5 SuricataLog]$ eve_json --help
usage: eve_json [-h] [--nxdomain | --payload | --flow | --netflow NETFLOW | --useragent] eve [eve ...]

This script is inspired by the examples provided on [15.1.3. Eve JSON ‘jq’ Examples](https://suricata.readthedocs.io/en/suricata-6.0.0/output/eve/eve-json-
examplesjq.html) A few things: * The output uses colorized JSON

positional arguments:
  eve                Path to one or more /var/log/suricata/eve.json file to parse.

optional arguments:
  -h, --help         show this help message and exit
  --nxdomain         Show DNS records with NXDOMAIN
  --payload          Show alerts with a printable payload
  --flow             Aggregated flow report per protocol and destination port
  --netflow NETFLOW  Get the netflow for a given IP address
  --useragent        Top user agent in HTTP traffic

Take a look at some examples below:

NXDOMAIN

suricatalog-eve_json-nxdomain.png

eve_json --nxdomain test/eve.json

PAYLOAD

suricatalog-eve_json-payload.png

eve_json --payload ~/Downloads/eve.json

FLOW

suricatalog_eve_json-flow.png

eve_json --flow test/eve_udp_flow.json

NETFLOW

suricatalog_eve_json-netflow.png

eve_json --netflow 224.0.0.251 test/eve_udp_flow.json

USERAGENT

suricatalog-eve_json-useragent.png

eve_json --useragent test/eve.json

Running eve_* applications on a browser

Suricata eve server, running eve* applications on a browser!

You can run Suricata Log applications on a browser by using the eve_server wrapper:

# Show the flow report on a eve.json file
eve_server --application eve_json -- --flow ~/eve.json

# Show NX domain report
eve_server --application eve_json -- --nxdomain ~/eve.json

# Inspect the eve.json records
eve_server --applications eve_log -- ~/eve.json

You need to pass the '--' to tell the server than this options belong to the underlying eve_* you want to call.

Running from Docker

It is also possible to run SuricataLog from a Docker container. Please see the DOCKER.md for more details

Running with uv

If you have uv, you can just do this:

uvx --from SuricataLog eve_log /var/log/suricata/eve.json
uvx --from SuricataLog eve_json --useragent /var/log/suricata/eve.json
uvx --from SuricataLog eve_server --application eve_json -- --flow /var/log/suricata/eve.json

You get the idea.

Bash Auto complete

I tried my best to follow 8.6 Programmable Completion

I provided auto complete for the most common flags. You can figure out all the flags by passing '--help' to any of the scripts.

Installation of auto complete commands

You can install Bash autocomplete for all the SuricataLog scripts. Just run the 'eve_autocomplete' and follow directions:

eve_autocomplete --help

Supported versions

I work on this project on my spare time and I cannot support every version of Linux/ Python combination out there. This is my current test bed, and it may change without further notice

SuricataLog Supported OS Python Suricata
<= 0.8 NO NA < 3.8 6.04
0.9+ NO fedora 37 => 3.11.4 6.04
0.9+ NO Armbian 23.02.2 Jammy => 3.10.6 6.04
0.9+ NO Ubuntu 20.04.4 LTS (Focal Fossa) => 3.8.10 6.04
1.0.3+ YES fedora 40 => 3.11.4 7.0.6

You are more than welcome to:

  • Submit patches with new features and bug-fixes.
  • Open bug reports. Be as detailed as possible, otherwise I will have no choice but to close it.

Tutorials

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

suricatalog-1.1.4.tar.gz (32.4 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

suricatalog-1.1.4-py3-none-any.whl (37.2 kB view details)

Uploaded Python 3

File details

Details for the file suricatalog-1.1.4.tar.gz.

File metadata

  • Download URL: suricatalog-1.1.4.tar.gz
  • Upload date:
  • Size: 32.4 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.1.0 CPython/3.11.6

File hashes

Hashes for suricatalog-1.1.4.tar.gz
Algorithm Hash digest
SHA256 1f51e51741dfac418fbc032d607a9f004b1a88e3cb8d581164f947dd49a1cfa8
MD5 52766f42c23c8da14ab0db22ad36c24a
BLAKE2b-256 3f68c7c5fb13aaa4256cabcbacc87d4da98695f9609d4026f7208b649c7061d1

See more details on using hashes here.

File details

Details for the file suricatalog-1.1.4-py3-none-any.whl.

File metadata

  • Download URL: suricatalog-1.1.4-py3-none-any.whl
  • Upload date:
  • Size: 37.2 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.1.0 CPython/3.11.6

File hashes

Hashes for suricatalog-1.1.4-py3-none-any.whl
Algorithm Hash digest
SHA256 314d86ad052692aded64794b76930979d994141a7586c10192230f6cbf0a0841
MD5 f1326855763323536cbaa6f6b6fe818f
BLAKE2b-256 8793ce7799b40cf3895afb968e250f9a1a0e282264d90685c8a2da57b12989a6

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page