We fixed several deprecations in the NetEye SIEM module, which allow NetEye installations to be compliant with the directives of Elastic Stack and to be prepared for future upgrade of the Elastic Stack.
Updated packages
For NetEye 4.30 we updated the following packages:
apm-server, apm-server-autosetup, apm-server-neteye-config, elasticsearch, elasticsearch-autosetup, elasticsearch-neteye-config, elasticsearch-xpack-license, filebeat, filebeat-autosetup, filebeat-neteye-config, kibana, kibana-autosetup, kibana-neteye-config, logstash, logstash-autosetup, logstash-neteye-config, logstash-neteye-config-autosetup to version 7.17.9_neteye3.48.2-1
elastic-blockchain-proxy, elastic-blockchain-proxy-autosetup to version 0.29.0-1
icingaweb2-module-kibana, icingaweb2-module-kibana-autosetup to version 1.23.0-1
Fix Tornado filter WHERE condition We fixed an issue in Tornado UI in which the WHERE condition of a filter were not being displayed correctly for some conditions not created through the API. List of updated packages To solve the Read More
Fix Tornado filter WHERE condition We fixed an issue in Tornado UI that did not allow deleting the WHERE condition of a filter in some conditions. List of updated packages To solve the issue, the following packages have been updated Read More
Important: Chromium security update Type/Severity NetEye Product Security has rated this update as having a security impact of Low Security Fix for NetEye 4.41 An update for the following packages is now available for NetEye 4: chromium to version 133.0.6943.141-1 Read More
Fix Tornado Filters names and descriptions editing We fixed an issue in Tornado related to the editing of new Filters names and descriptions, which would have resulted in an error. List of updated packages To solve the issue, the following Read More
Fix Elasticsearch read-only indices check We fixed an issue related to the 01002_elastic_indices_read_only_check.sh light health check, which checks if some indices are present in Elasticsearch in a read-only state. The check may have wrongly recognized as in read-only also some Read More
