Start your 14-day free trial today
No Credit Card Required
Try Logit.io FreeAlready have an account? Sign In
Auditbeat
A log shipper designed for audit data.
Auditbeat is an open source shipping agent that lets you ship audit data to one or more destinations, including Logstash.
Step 1 - Install Auditbeat
deb (Debian/Ubuntu/Mint)
curl -L -O https://artifacts.elastic.co/downloads/beats//-oss-7.15.1-amd64.deb
sudo dpkg -i -oss-7.15.1-amd64.deb
rpm (CentOS/RHEL/Fedora)
curl -L -O https://artifacts.elastic.co/downloads/beats//-oss-7.15.1-x86_64.rpm
sudo rpm -vi -oss-7.15.1-x86_64.rpm
macOS
curl -L -O https://artifacts.elastic.co/downloads/beats//-oss-7.15.1-darwin-x86_64.tar.gz
tar xzvf -oss-7.15.1-darwin-x86_64.tar.gz
Windows
- Download and extract the Windows zip file.
- Rename the
-<version>-windows
directory to ``. - Open a PowerShell prompt as an Administrator.
- Run the following to install as a Windows service:
.\install-service-.ps1
PowerShell.exe -ExecutionPolicy UnRestricted -File .\install-service-.ps1
.
Step 2 - Configure Modules
Locate and open the auditbeat configuration file:
- deb/rpm (Debian/Ubuntu/Mint/CentOS/RHEL/Fedora):
/etc/auditbeat/auditbeat.yml
- Windows:
C:\Program Files\auditbeat\auditbeat.yml
- Mac:
<EXTRACTED_ARCHIVE>/auditbeat.yml
By default, the file_integrity
module will be enabled. This module watches for file changes such as when a file is created, updated or deleted.
When a change is detected, auditbeat will send events containing metadata to one or more configured output sources (e.g. Logstash).
The module can be configured in auditbeat.yml
by adding or removing path addresses. Auditbeat will watch for changes in files relative to these paths.
Step 3 - Configure output
We'll be shipping to Logstash so that we have the option to run filters before the data is indexed.
Comment out the elasticsearch output block.
## Comment out elasticsearch output
#output.elasticsearch:
# hosts: ["localhost:9200"]
Step 4 - Validate configuration
Let's check the configuration file is syntactically correct by running directly inside the terminal.
If the file is invalid, will print an error loading config file
error message with details on how to correct the problem.
deb/rpm
sudo -e -c /etc//.yml
macOS
cd <EXTRACTED_ARCHIVE>
./ -e -c .yml
Windows
cd <EXTRACTED_ARCHIVE>
.\.exe -e -c .yml
Step 5 - Start auditbeat
If we now start the Auditbeat service, any audited changes will be shipped to your hosted Logstash instance.
deb/rpm
sudo systemctl enable auditbeat
sudo systemctl start auditbeat
mac
./auditbeat
Windows
Start-Service auditbeat
Try changing a file located in one of the configured directory paths. You should see a change event in Kibana.
Step 6 - how to diagnose no data in Stack
If you don't see data appearing in your Stack after following the steps, visit the Help Centre guide for steps to diagnose no data appearing in your Stack or Chat to support now.
Step 7 - Auditbeat Logging Overview
Auditbeat is one of the most recent additions to Elastic Stack’s Beats. It is primarily used to gather audit data on user activity and processes running on your server’s infrastructure. Additionally, Auditbeat can be used to detect crucial and unexpected changes to configuration files & binaries.
This can be key to helping you to identify compliance issues and security violations in your organisation. Once configured, changes to the file are updated in real-time to your output, allowing for optimised visibility of security-related instances. It can be used directly to undertake these processes & gather data without the need to access Linux’s Auditd.
Centralising your Auditbeat event data using a log management system such as Logit.io provides a way of easily managing your ELK Stack overheads in one single platform.
If you need any further assistance with migrating your Auditbeat data to Logstash we're here to help you get started. Feel free to reach out by contacting our support team by visiting our dedicated Help Centre or via live chat & we'll be happy to assist.