Skip to content
This repository has been archived by the owner on May 29, 2024. It is now read-only.

Latest commit

Β 

History

History
89 lines (64 loc) Β· 3.28 KB

CHANGELOG.md

File metadata and controls

89 lines (64 loc) Β· 3.28 KB

Changelog

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

[2022.05.16]

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 of stix2 package. #162
  • ⚠️ The Dockerfile of suricata-threatbus has moved to the repository toplevel and now installs Threat Bus from source. This way, the Docker build always uses the latest Threat Bus sources, instead of the latest version from PyPI. #141

  • 🐞 suricata-threatbus now implements the new zmq management protocol of the threatbus-zmq-app plugin. The app now simply re-uses the Threat Bus hostname as it is configured in the users config.yaml and appends the port specifications for pub and sub 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 named config.yaml and config.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 with SURICATA_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