Intrusion detection environment
Go to file
Patrik Koncity 43cdcea6e5 RHEL-9.9 ERRATUM
Support for included files in /etc/aide.d/
Resolves: RHEL-178122
Increase default values for num_workers
Resolves: RHEL-178123
Add pre-configured systemd timer for aide check
Resolves: RHEL-178121
2026-06-05 08:15:04 +02:00
.fmf Add ci plan for gating and adjust gating rules 2025-02-06 13:42:32 +01:00
.gitignore RHEL 9.8.0 ERRATUM 2025-09-16 11:57:09 +02:00
aide-0.15-syslog-format.patch RHEL 9.0.0 Alpha bootstrap 2020-10-14 21:34:29 +02:00
aide-0.19.2-syslog-format.patch aide: re-add syslog_format option for 0.19.2 2026-06-02 09:11:38 +02:00
aide-check.service RHEL-9.9 ERRATUM 2026-06-05 08:15:04 +02:00
aide-check.timer RHEL-9.9 ERRATUM 2026-06-05 08:15:04 +02:00
aide-include-permission-checks.patch RHEL-9.9 ERRATUM 2026-06-05 08:15:04 +02:00
aide-migrate-config aide: add aide-migrate-config to automate config migration from pre-0.19 2026-06-02 09:13:25 +02:00
aide-tmpfiles.conf RHEL 9.8.0 ERRATUM 2025-09-16 11:57:09 +02:00
aide.conf RHEL-9.9 ERRATUM 2026-06-05 08:15:04 +02:00
aide.logrotate RHEL 9.0.0 Alpha bootstrap 2020-10-14 21:34:29 +02:00
aide.spec RHEL-9.9 ERRATUM 2026-06-05 08:15:04 +02:00
ci_tests.fmf Add ci plan for upgrade 2026-06-02 09:07:12 +02:00
gating.yaml Add ci plan for gating and adjust gating rules 2025-02-06 13:42:32 +01:00
gpgkey-aide.gpg RHEL 9.8.0 ERRATUM 2025-09-16 11:57:09 +02:00
README.quickstart RHEL-9.9 ERRATUM 2026-06-05 08:15:04 +02:00
sources RHEL 9.8.0 ERRATUM 2025-09-16 11:57:09 +02:00

1) Customize /etc/aide.conf to your liking. In particular, add
   important directories and files which you would like to be
   covered by integrity checks. Avoid files which are expected
   to change frequently or which don't affect the safety of your
   system.

2) Run "/usr/sbin/aide --init" to build the initial database.
   With the default setup, that creates /var/lib/aide/aide.db.new.gz

3) Store /etc/aide.conf, /usr/sbin/aide and /var/lib/aide/aide.db.new.gz
   in a secure location, e.g. on separate read-only media (such as
   CD-ROM). Alternatively, keep MD5 fingerprints or GPG signatures
   of those files in a secure location, so you have means to verify
   that nobody modified those files.

4) Copy /var/lib/aide/aide.db.new.gz to /var/lib/aide/aide.db.gz
   which is the location of the input database.

5) Run "/usr/sbin/aide --check" to check your system for inconsistencies
   compared with the AIDE database. Prior to running a check manually,
   ensure that the AIDE binary and database have not been modified
   without your knowledge.

6) To schedule daily integrity checks, enable the systemd timer:

   systemctl enable --now aide-check.timer

   View results with: journalctl -u aide-check
   Check timer status with: systemctl status aide-check.timer

   The timer runs daily with low CPU/IO priority to minimize impact
   on production workloads. It is disabled by default — only enable
   it after initializing the database (steps 2-4).

   Caution!

   It cannot be guaranteed that the AIDE binaries, config file and
   database are intact. It is not recommended that you run automated
   AIDE checks without verifying AIDE yourself frequently. In addition
   to that, AIDE does not implement any password or encryption
   protection for its own files.

   It is up to you how to put a file integrity checker to good effect.
   On a compromised system, the intruder could disable the automated
   check. Or he could replace the AIDE binary, config file and database
   easily when they are not located on read-only media.