This changelog documents all notable user-facing changes of
suricata-threatbus
.
Every entry has a category for which we use the following visual abbreviations:
- π Features
- 𧬠Experimental Features
β οΈ Changes- β‘οΈ Breaking Changes
- π Bug Fixes
No user-facing changes.
No user-facing changes.
No user-facing changes.
No user-facing changes.
No user-facing changes.
No user-facing changes.
β οΈ suricata-threatbus
now depends on version 3.0 ofstix2
package. #162
-
β οΈ The Dockerfile ofsuricata-threatbus
has moved to the repository toplevel and now installs Threat Bus from source. This way, the Docker build always uses thelatest
Threat Bus sources, instead of the latest version from PyPI. #141 -
π
suricata-threatbus
now implements the new zmq management protocol of thethreatbus-zmq-app
plugin. The app now simply re-uses the Threat Bus hostname as it is configured in the usersconfig.yaml
and appends the port specifications forpub
andsub
communication that it receives as part of the subscription success response. #140 -
π We now release a pre-built Docker image for
suricata-threatbus
together with our future Threat Bus releases. #137 -
β οΈ suricata-threatbus
now uses Dynaconf for configuration management. Configuration via a config file works exactly as it has worked before. Users can provide a path to the config file using the-c
option.suricata-threatbus
now considers files namedconfig.yaml
andconfig.yml
as default configs if located in the same directory. Additionally,suricata-threatbus
now supports configration via environment variables and.dotenv
. Env vars need to be prefixed withSURICATA_THREATBUS_
to be respected and always take precedence over values in config files. #133
- π
suricata-threatbus
has come to life. This stand-alone application connects to Threat Bus via ZeroMQ and bridges the gap between Threat Bus and Suricata.suricata-threatbus
maintains a custom rule file for Suricata to read from. That allows users users to sync their Suricata rules from other Threat Bus-connected tools, such as OpenCTI, with their Suricata IDS installations. #131