First of all, I’d like to explain in simple terms what Elastiflow is all about. ElastiFlow is a NetFlow analyzer that works with the Elastic Stack.
The Elastiflow Analyzer can collect various network flows, such as netflow or sflow, and write them to Elastic, taking into account the ECS format. In addition, the Elastiflow Analyzer provides a number of ready-made dashboards that make analysis of the flow data much easier.
Of course, it’s also possible to create your own dashboards, or to change the dashboards that are already included.
One of our customers purchased Elastiflow some time ago, and it was now time to install the latest version 5 in their NetEye SIEM environment. Since I was already familiar with the previous version, I was able to make a good comparison between the two.
The prerequisite for the installation is a NetEye SIEM environment, which is already based on Elastic. The new Elastiflow analyzer can easily be installed on the NetEye server via an rpm package. You should then create an additional user in Elastic to give it access to the Elastiflow analyzer.
Since Elastiflow is started as a systemd service, it has a configuration file, located at:
In it you can configure the Elastiflow user you just created with an associated password and the UDP port over which the flow can be received. To enable visualization of geolocation on the Elastiflow dashboards, the geolite databases must be linked to the /etc/elastiflow/maxmind directory. The Elasticsearch settings must also be activated and configured.
In addition, the ElastiFlow user must be added to the logstash group, and finally, the dashboards have to be downloaded as ndjson files from the Elastiflow site and imported into the Elastic system.
If all configuration parameters have been set successfully, the Elastiflow Analyzer can be started as a systemd service:
If flows are already being sent to the defined port, they will be displayed in the dashboards.
In my opinion, the installation of the new Elastiflow version 5 is now much easier than before.
Incidentally, I’d like to inform you that the customer for whom I installed the Elastiflow Analyzer operates a NetEye SIEM cluster. So I had to configure the Elastiflow Analyzer to work in a cluster environment. This, too, was easy to do.
Finally, I must mention that Würth Phoenix is an Elastiflow partner and thus supports and offers integration of the Elastiflow module via the NetEye SIEM.
I started my professional career as a system administrator.
Over the years, my area of responsibility changed from administrative work to the architectural planning of systems.
During my activities at Würth IT Italy, the focus of my area of responsibility changed to the installation and consulting of the IT system management solution WÜRTHPHOENIX NetEye.
In the meantime, I take care of the implementation and planning of customer projects in the area of our unified monitoring solution.
Author
Tobias Goller
I started my professional career as a system administrator.
Over the years, my area of responsibility changed from administrative work to the architectural planning of systems.
During my activities at Würth IT Italy, the focus of my area of responsibility changed to the installation and consulting of the IT system management solution WÜRTHPHOENIX NetEye.
In the meantime, I take care of the implementation and planning of customer projects in the area of our unified monitoring solution.
Introduction For on-premise Elasticsearch installations, performing a rolling restart across a cluster can be a time-consuming task, especially when dealing with large clusters. Rolling restarts are typically required when changing node configurations or upgrading the cluster to a new version. Read More
When performance degradation occurs within a complex system, understanding the root cause can be extremely challenging. If the issue happens sporadically, this difficulty increases even more. This is because modern systems involve numerous components that interact in complex ways. For Read More
If you've worked with Elastic APM, you're probably familiar with the APM Server: a component that collects telemetry data from APM Agents deployed across your infrastructure. But what happens when you need to segregate that data by tenant, especially in Read More
This article gives an overview and offers a practical tips to detecting some suspicious activities in Microsoft SQL Server, from configuring audit policies to leveraging Elastic for effective monitoring and threat detection. Introduction Microsoft SQL Server is one of the Read More
If you're monitoring an OpenShift or a Kubernetes cluster with Elastic Stack, you might've noticed that the Kubernetes integration uses the default Index Lifecycle Policy. It means that those logs and metrics have an unlimited retention. If the volume of Read More