The Lumu Virtual Appliance (VA) can work alongside your current security infrastructure to provide an even better Continuous Compromise Assessment. The Lumu VA offers the option to create Collectors, a seamless way to integrate with metadata collected by Security Information and Event Management (SIEM) technologies. One of the capabilities of the VA Collectors is to gather and process network flow data. To get started with Virtual Appliance Collectors, access our documentation.
In addition to collecting Netflow/IPFIX data sent by network hardware, the Lumu VA is able to collect network flows exported by an externally deployed Packetbeat or other solutions. In this guide, we show you how to configure a Lumu VA for network flow collection sent by a network hardware. We also provide guidance for the cases in which you want to have conversation visibility into your network, but your network hardware does not offer network flow synthesis capabilities.
The following two scenarios are an overview of the two scenarios in which Lumu VA can collect network flow information:
Your network devices may be equipped with the capability of generating and exporting network flows information in Netflow or IPFIX format. This is the preferred method, as synthesizing network flows via hardware is more efficient. For this method, you need to create a Virtual Appliance, add a network flow collector in the VA, then configure your device to send the data to the appliance collector.
In case you do not have equipment in your network that offers such capability of network flow information, you still can leverage a third party software and set up a SPAN mirror port at your disposal to collect network flow data using a third party software configured on an additional machine (as illustrated on figure 2) to send it to Lumu to have conversation visibility into your network.
The Lumu VA comes equipped with everything it needs to receive and process flow data captured by externally deployed Netflow/IPFIX solutions. In this scenario, you will create and set up a network flow VA collector and configure third party tools to send the data to the Lumu Virtual Appliance.
Below in this document you are going to find samples of network flow configuration with nProbe, Softflowd and Packetbeat.
Let’s first review the general steps to set up network flow collection using a Lumu Virtual Appliance Collector.
In order to send information to Lumu servers from any of the scenarios previously described, you need first to set up a Virtual Appliance.
The ability to collect network flow data is available from the version 4.0 of the Lumu Virtual Appliance. In case you already have a Lumu VA set up and running, make sure it has the latest appliance version, simply run the command lumu-appliance upgrade , this check if a new version of the appliance is available. If yes, you can download and install it.
In order to receive NetFlow/IPFIX data, the Lumu Virtual Appliance needs Filebeat, a log file shipper from Elastic. For more details about Filebeat, consult the
To install and configure Filebeat, go to the Lumu VA and run the following command:
The Lumu VA will assist you in the download of Filebeat after you accept the Elastic License:
You will be requested to set the port number to listen to network traffic data. This is a positive number below 65536, numbers above 1024 are highly recommended as ports below 1024 are usually used by other applications, and may require different privileges to run. Be sure to select a port that is not used by any other collector. Ports 5044 and 5045 are already in use by the appliance.
To add a VA Collector, go to the Lumu Portal and navigate to the Collectors > Virtual Appliance menu, click on the VA in which you want to add the collector, then click on the “Add Collector” button.
When creating a Virtual Appliance, you are required to provide the following information:
Once you have created the Netflow collector at the Lumu Portal, go to the Virtual Appliance and refresh the VA collectors settings by running the command lumu-appliance collectors refresh. The newly created collector will be presented:
When continuing, you will be prompted to select the device type:
The first option applies to NetFlow/IPFIX. Once selected, the following selection will be presented:
Reverse and post are referred to the fields where the information about the response flow is going to be expected, reverse as in reverse_octet_delta_count or post as in post_octet_delta_count. Usually, Softflowd sends the information in reverse fields and nProbe sends it in post fields. If you don’t know which is your case, contact our support team to help you do a capture and verify.
For the Packetbeat option, you will be requested to set the port number. Keep in mind that this should be a positive number below 65535, numbers above 1024 are highly recommended as ports below 1024 are usually used by other applications, and may require different privileges to run. Be sure to select a port that is not used by any other collector. Port 5044 is already in use by the appliance.
We recommend reloading the appliance after changing the configuration files to make sure the new settings are applied.
In this section, we show how to leverage third party solutions to collect IP traffic data and have IP conversation visibility into your network. While we provide guidance for nProbe and Softflowd, you can configure other third party tools to listen to the SPAN port, synthesize flow information and send it to Lumu, as long as the data generated follows the NetFlow or IPFIX standards.
Once you decide which tool you want to deploy to synthesize network flows, you have to install it in a physical machine where you set up two ports (network interface controller - NIC), one to listen to the SPAN port and another one to export flows to the Lumu Virtual Appliance.
The next step is to configure your network flow generating device or software to send the information to the port you set when configuring the Lumu Virtual Appliance Collector.
Additionally, you should configure the solution to use one of the supported protocols: NetFlow v5, v9 or v10/IPFIX.
If the device/solution uses a protocol v9 or v10/IPFIX, make sure the following fields are configured:
If you use the bidirectional version of the protocol, make sure the corresponding fields are also enabled.
Depending on the device you are using, there may be additional steps required to successfully collect network flow data. Consult your vendor documentation for guidance.
You can find an example of configuring nProbe as a flow synthesizer for the Lumu Virtual Appliance below. The flag -i should be used with the name of the interface where the SPAN port is connected. The flag -n should be used with the IP of the Lumu VA and the port configured to listen for network traffic data.
Note, we use the template option since the default template used by nProbe doesn’t contain the fields expected by the Lumu Virtual Appliance.
To review the appliance logs for any problems, run the following command in the Lumu VA:
Below you can find an example of the use with version 9. The flag -i should be used with the name of the interface where the SPAN port is connected. The flag -n should be used with the IP of the appliance and the port configured to listen for IP traffic data.
Softflowd implements Netflow version 5, 9 and 10/IPFIX, but we recommend not to use the bidirectional mode because the source and destination IP can be switched by the implementation.
To review appliance the logs for any problems, run the following command in the Lumu VA:
Packetbeat is a tool that can be configured to listen for IP traffic on a SPAN port and send the exported flows to the Lumu Virtual Appliance. You can also consult Elastic’s official documentation about configuring flows to monitor network traffic.
In this section, we show the configuration procedure based on docker on a Linux environment, for other operating systems, consult the instructions to install docker and docker-compose.
We suggest the following script to install docker and docker-compose in a Linux based environment (make sure to use the last version of the dock composer available):
After running the script, log out and log back in so that your group membership is re-evaluated.
The next step is to create the following files. Replace the interface, IPs and ports with those configured in the Virtual Appliance.
After configuring both files, use docker compose to start Packetbeat with the following command:
To confirm the Packetbeat configuration is working as expected, run the following command:
If everything is properly configured, the information will start to reach Lumu Virtual Appliance. To review the appliance logs for any problems, run the following command in the Lumu VA: