I have installed Auditbeat and configured it on a RHEL machine. Auditbeat status shows that it is running. However, index for Auditbeat shows zero docs count. Auditd service is disabled. I have deleted and recreated the index several times (using auditbeat setup -c). The index is created with pattern but no docs.
Any help please?
Config as below:
###################### Auditbeat Configuration Example #########################
This is an example configuration file highlighting only the most common
options. The auditbeat.reference.yml file from the same directory contains all
the supported options with more comments. You can use it as a reference.
You can find the full configuration reference here:
Auditbeat Reference | Elastic
=========================== Modules configuration ============================
auditbeat.modules:
-
module: auditd
enabled: falseLoad audit rules from separate files. Same format as audit.rules(7).
#audit_rule_files: [ '${path.config}/audit.rules.d/*.conf' ]
audit_rules: |
-w /etc/group -p wa -k identity
-w /etc/passwd -p wra -k identity
-w /etc/gshadow -p wa -k identity
-w /etc/shadow -p wa -k identity
-w /etc/security/opasswd -p wa -k identity
-w /apps/auditbeat/auditbeat.yml war -k access
-a always,exit -F arch=b64 -S open,creat,truncate,ftruncate,openat,open_by_handle_at -F exit=-EACCES -k access
-a always,exit -F arch=b64 -S open,creat,truncate,ftruncate,openat,open_by_handle_at -F exit=-EPERM -k access -
module: file_integrity
paths:- /bin
- /usr/bin
- /sbin
- /usr/sbin
- /etc
-
module: system
datasets:- package # Installed, updated, and removed packages
period: 1m # The frequency at which the datasets check for changes
-
module: system
datasets:- host # General host information, e.g. uptime, IPs
- login # User logins, logouts, and system boots.
- process # Started and stopped processes
- socket # Opened and closed sockets
- user # User information
How often datasets send state updates with the
current state of the system (e.g. all currently
running processes, all open sockets).
state.period: 1m
Enabled by default. Auditbeat will read password fields in
/etc/passwd and /etc/shadow and store a hash locally to
detect any changes.
user.detect_password_changes: true
File patterns of the login record files.
login.wtmp_file_pattern: /var/log/wtmp*
login.btmp_file_pattern: /var/log/btmp*
======================= Elasticsearch template setting =======================
setup.template.settings:
index.number_of_shards: 3
#index.codec: best_compression
#_source.enabled: false
================================== General ===================================
The name of the shipper that publishes the network data. It can be used to group
all the transactions sent by a single shipper in the web interface.
#name:
The tags of the shipper are included in their own field with each
transaction published.
#tags: ["service-X", "web-tier"]
Optional fields that you can specify to add additional information to the
output.
#fields:
env: staging
================================= Dashboards =================================
These settings control loading the sample dashboards to the Kibana index. Loading
the dashboards is disabled by default and can be enabled either by setting the
options here or by using the setup command.
setup.dashboards.enabled: true
The URL from where to download the dashboards archive. By default this URL
has a value which is computed based on the Beat name and version. For released
versions, this URL points to the dashboard archive on the artifacts.elastic.co
website.
#setup.dashboards.url:
=================================== Kibana ===================================
Starting with Beats version 6.0.0, the dashboards are loaded via the Kibana API.
This requires a Kibana endpoint configuration.
setup.kibana:
host: "https://xyz:5601"
=============================== Elastic Cloud ================================
These settings simplify using Auditbeat with the Elastic Cloud (https://cloud.elastic.co/).
The cloud.id setting overwrites the output.elasticsearch.hosts and
setup.kibana.host options.
You can find the cloud.id in the Elastic Cloud web UI.
#cloud.id:
The cloud.auth setting overwrites the output.elasticsearch.username and
output.elasticsearch.password settings. The format is <user>:<pass>.
#cloud.auth:
================================== Outputs ===================================
Configure what output to use when sending the data collected by the beat.
---------------------------- Elasticsearch Output ----------------------------
output.elasticsearch:
hosts: ["xyz:9200"]
protocol: "https"
username: "elastic"
password: "password"
server.ssl.enabled: true
server.ssl.certificate: /xyz/xyz.cer
server.ssl.key: /xyz/xyz.key
------------------------------ Logstash Output -------------------------------
#output.logstash:
The Logstash hosts
#hosts: ["localhost:5044"]
Optional SSL. By default is off.
List of root certificates for HTTPS server verifications
#ssl.certificate_authorities: ["/etc/pki/root/ca.pem"]
Certificate for SSL client authentication
#ssl.certificate: "/etc/pki/client/cert.pem"
Client Certificate Key
#ssl.key: "/etc/pki/client/cert.key"
================================= Processors =================================
Configure processors to enhance or manipulate events generated by the beat.
processors:
- add_host_metadata: ~
- add_cloud_metadata: ~
- add_docker_metadata: ~
================================== Logging ===================================
logging.level: debug
logging.to_files: true
logging.files:
path: /var/log/auditbeat
name: auditbeat
keepfiles: 7
============================= X-Pack Monitoring ==============================
Auditbeat can export internal metrics to a central Elasticsearch monitoring
cluster. This requires xpack monitoring to be enabled in Elasticsearch. The
reporting is disabled by default.
Set to true to enable the monitoring reporter.
#monitoring.enabled: false
Sets the UUID of the Elasticsearch cluster under which monitoring data for this
Auditbeat instance will appear in the Stack Monitoring UI. If output.elasticsearch
is enabled, the UUID is derived from the Elasticsearch cluster referenced by output.elasticsearch.
#monitoring.cluster_uuid:
Uncomment to send the metrics to Elasticsearch. Most settings from the
Elasticsearch output are accepted here as well.
Note that the settings should point to your Elasticsearch monitoring cluster.
Any setting that is not set is automatically inherited from the Elasticsearch
output configuration, so if you have the Elasticsearch output configured such
that it is pointing to your Elasticsearch monitoring cluster, you can simply
uncomment the following line.
#monitoring.elasticsearch:
============================== Instrumentation ===============================
Instrumentation support for the auditbeat.
#instrumentation:
# Set to true to enable instrumentation of auditbeat.
#enabled: false
# Environment in which auditbeat is running on (eg: staging, production, etc.)
#environment: ""
# APM Server hosts to report instrumentation results to.
#hosts:
# - http://localhost:8200
# API Key for the APM Server(s).
# If api_key is set then secret_token will be ignored.
#api_key:
# Secret token for the APM Server(s).
#secret_token:
================================= Migration ==================================
This allows to enable 6.7 migration aliases
#migration.6_to_7.enabled: true