Auditbeat

To get started first follow the steps below:

• Install auditbeat
• Root access
• Verify the required port is open

Older versions can be found here auditbeat 7, auditbeat 6, auditbeat 5

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.

There is also a full example configuration file called auditbeat.reference.yml that shows all the possible options.

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"]

No input available! Your stack is missing the required input for this data source Talk to support to add the input

DEB/RPM

sudo auditbeat -e -c /etc/auditbeat/auditbeat.yml

macOS

sudo ./auditbeat -e -c auditbeat.yml --strict.perms=false

You’ll be running auditbeat as root, so you need to change ownership of the configuration file and any configurations enabled in the modules.d directory, or run auditbeat with --strict.perms=false as shown above. Read more about how to change ownership.

Windows

cd <EXTRACTED_ARCHIVE>
.\auditbeat.exe -e -c auditbeat.yml

Linux

sudo ./auditbeat -e -c auditbeat.yml --strict.perms=false

You’ll be running auditbeat as root, so you need to change ownership of the configuration file and any configurations enabled in the modules.d directory, or run auditbeat with --strict.perms=false as shown above. Read more about how to change ownership.

If the yml file is invalid, auditbeat will print an `error loading config file` error message with details on how to correct the problem. If you have issues starting auditbeat see "How To Diagnose No Data In Stack" below to troubleshoot.

Start or restart auditbeat to apply the configuration changes.

Data should now have been sent to your Stack.

View my data

If you don't see logs take a look at How to diagnose no data in Stack below for how to diagnose common issues.

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.

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.