Falco
Ship your Falco logs using Filebeat to your Logit.io Stack
Configure Falco to ship logs via Filebeat to your Logit.io stacks via Logstash.
Install Integration
Install Filebeat
To get started you will need to install filebeat. To do this you have two main options:
- Choose the filebeat (opens in a new tab) ZIP file (Windows ZIP x86_64) or
- Choose the Microsoft Software Installer MSI (opens in a new tab) file (Windows MSI x86_64 (beta))
To successfully install filebeat and set up the required Windows service you will need to have administrator access.
If you have chosen to download the zip file:
- Extract the contents of the zip file into C:\Program Files.
- Rename the extracted folder to filebeat
- Open a PowerShell prompt as an Administrator (right-click the PowerShell icon and select Run As Administrator).
- From the PowerShell prompt, run the following commands to install filebeat as a Windows service:
cd 'C:\Program Files\filebeat'
.\install-service-filebeat.ps1
If script execution is disabled on your system, you need to set the execution policy for the current session to allow the script to run. For example:
PowerShell.exe -ExecutionPolicy UnRestricted -File .\install-service-filebeat.ps1
For more information about Powershell execution policies see here (opens in a new tab).
If you have chosen to download the filebeat.msi file:
- double-click on it and the relevant files will be downloaded.
At the end of the installation process you'll be given the option to open the folder where filebeat has been installed.
- Open a PowerShell prompt as an Administrator (right-click the PowerShell icon and select Run As Administrator).
- From the PowerShell prompt, change directory to the location where filebeat was installed and run the following command to install filebeat as a Windows service:
.\install-service-filebeat.ps1
If script execution is disabled on your system, you need to set the execution policy for the current session to allow the script to run. For example:
PowerShell.exe -ExecutionPolicy UnRestricted -File .\install-service-filebeat.ps1
For more information about Powershell execution policies see here (opens in a new tab).
Configure Falco Logging
Falco serves as a container security and threat detection engine for Kubernetes at runtime, that detects unauthorized container activity and logs it. Falco has been approved by the CNCF (opens in a new tab) for this purpose.
Set the output format to JSON
- Locate the configuration file, which is typically named
/etc/falco/falco.yaml
. - Open the configuration file with a text editor of your choice.
- Ensure
json_output: true
andjson_include_output_property: true
- Save the changes to the configuration file.
- Restart the Falco service to apply the updated configuration.
Look up the filepath to Falco's logs
- In the same configuration file
/etc/falco/falco.yaml
- Under
file_output:
make a note of thefilename:
value, this will be used in step 3 to configure Filebeat.
It's important to review the Falco documentation (opens in a new tab) for any specific guidance or instructions if you need to customise how logging is configured.
In the pre-configuted Filebeat configuration file below be sure to update the path to your Falco events log file. This path can vary depending on your installation.
Configure Filebeat.yml
The configuration file below is pre-configured to send data to your Logit.io Stack.
Copy the configuration file below and overwrite the contents of the Filebeat
configuration file typically located at /etc/filebeat/filebeat.yml
# ============================== Filebeat inputs ===============================
filebeat.inputs:
- type: filestream
enabled: true
paths:
- "@path:strip_quotes"
fields:
type: "@type:strip_quotes"
fields_under_root: true
encoding: utf-8
ignore_older: 12h
# ================================== Outputs ===================================
output.logstash:
hosts: ["@logstash.host:@logstash.sslPort"]
loadbalance: true
ssl.enabled: true
If you're running Filebeat 7.10 or older, change the type as shown below.
- type: log
It's a good idea to run the configuration file through a YAML validator to rule out indentation errors, clean up extra characters, and check if your YAML file is valid. Yamllint.com (opens in a new tab) is a great choice.
Validate Configuration
.\@beatname.exe test config -c @beatname.yml
If the yml file is invalid, @beatname will print a description of the error. For example, if the
output.logstash
section was missing, @beatname would print no outputs are defined, please define one under the output section
Start Filebeat
To start Filebeat, run in Powershell:
Start-Service filebeat
Launch Logit.io to view your logs
Data should now have been sent to your Stack.
View My DataIf you don't see take a look at How to diagnose no data in Stack below for how to diagnose common issues.
How to diagnose no data in Stack
If you don't see data appearing in your stack after following this integration, take a look at the troubleshooting guide for steps to diagnose and resolve the problem or contact our support team and we'll be happy to assist.
Falco Overview
Falco is a free, open-source container security monitoring solution that provides real-time threat detection and response capabilities. It is designed to help organizations identify and respond to security incidents in containerized environments.
To effectively monitor and analyze security events in containerized environments, it is essential to have a reliable and efficient log management solution. Falco provides a centralized platform for collecting, processing, and visualizing security-related data in real-time. It can be used to monitor various activities in container environments, such as network connections, file system access, and process execution.
To send data from Falco to other systems or services, organizations can use various output options, including JSON logs, Syslog, and gRPC. For instance, to output JSON logs to a file, users can modify the Falco configuration file and add the necessary output configuration.
In summary, using Falco as a container security monitoring solution provides organizations with a reliable and efficient way to detect and respond to security incidents in real-time. By leveraging the output options and various agents and modules, organizations can collect and analyze data from container environments and gain valuable insights into their security posture.
If you need any further assistance with migrating your log data to ELK we're here to help you get started. Feel free to get in contact with our support team by sending us a message via live chat and we'll be happy to assist.