The project runs under Linux, kernel 5.13+. It has been tested on x86_64(amd64), arm64(aarch64), and armv7a architectures. Currently, available deployment methods include:
Docker containers are available for the x86_64, arm64, and armv7a architectures and can be found on DockerHub: https://hub.docker.com/repository/docker/ziosec/bitblazr
As with most security sensors "privileged" mode is required, as is host networking.
docker run -it --privileged --network host -v /custom/config/dir:/app/config -e sensor_name=SENSOR_NAME -e log_level=LOG_LEVEL --name CONTAINER_NAME ziosec/bitblazr
Here is the description of the rest of the switches:
/app/config volume - use this to mount in a custom configuration directory. Otherwise BitBlazr will use the defaults found in the container.
sensor_name - this is where you assign a custom name to the sensor so it's easier to track, it will show up in logs, MQTT client_id, and cloudevents "source" field.
log_level - set desired log level here, standard log levels apply here, such as "trace", "debug", "info", "warn", "error". But default "info" level will be used.
name - docker container name for local management tasks
To build and run the sensor first make sure you have prerequisites installed. Those include:
Then follow these steps:
And finally, run it:
RUST_LOG=info cargo xtask run
The form has been successfully submitted.
Our excellent customer support team is ready to help.