aide

packaged by Chainguard

Chainguard Container for aide

AIDE (Advanced Intrusion Detection Environment) is a file integrity checker that detects tampering by comparing files against a hash baseline.

Chainguard Containers are regularly-updated, secure-by-default container images.

Download this Container Image

For those with access, this container image is available on cgr.dev:

docker pull cgr.dev/ORGANIZATION/aide:latest

Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.

Compatibility Notes

The AIDE project does not publish an official container image, so this image is built from source. AIDE (Advanced Intrusion Detection Environment) is a file integrity checker written in C and licensed under the GNU General Public License v2.0. It builds a database of file attributes and cryptographic hashes from the rules in its configuration file, then compares the filesystem against that baseline to detect added, removed, or changed files.

This image tracks upstream AIDE v0.19.5 and is built against libgcrypt for hashing, with zlib, curl, POSIX ACL, SELinux, xattr, capabilities, and e2fs attribute support. The entrypoint is /usr/bin/aide and the default command is --help, run from the / working directory.

The image runs as root (UID 0) by default because AIDE needs to read every file on the filesystem it monitors. The image contains no shell or default configuration file, so supply your own aide.conf.

Getting Started

Print the AIDE version and compiled-in options:

docker run --rm cgr.dev/ORGANIZATION/aide:latest --version

Create a configuration file and a directory for the database:

mkdir -p db
cat > aide.conf <<'EOF'
database_in=file:/db/aide.db
database_out=file:/db/aide.db.new
gzip_dbout=no
report_url=stdout
NORMAL = p+i+n+u+g+s+m+c+sha256
/target NORMAL
EOF

Initialize a baseline database for a directory mounted read-only at /target:

docker run --rm \
  -v "$PWD/target:/target:ro" \
  -v "$PWD/db:/db" \
  -v "$PWD/aide.conf:/etc/aide.conf:ro" \
  cgr.dev/ORGANIZATION/aide:latest --config=/etc/aide.conf --init
mv db/aide.db.new db/aide.db

Check the directory against the baseline. AIDE exits with a non-zero code (1 to 7) when it detects added, removed, or changed entries:

docker run --rm \
  -v "$PWD/target:/target:ro" \
  -v "$PWD/db:/db" \
  -v "$PWD/aide.conf:/etc/aide.conf:ro" \
  cgr.dev/ORGANIZATION/aide:latest --config=/etc/aide.conf --check

Validate a configuration file without scanning:

docker run --rm \
  -v "$PWD/aide.conf:/etc/aide.conf:ro" \
  cgr.dev/ORGANIZATION/aide:latest --config=/etc/aide.conf --config-check

Configuration

• AIDE reads /etc/aide.conf by default. Mount your configuration there or pass --config=<path>.
• Mount the database directory read-write so --init and --update can write aide.db.new.
• Mount the filesystems to be scanned read-only.
• When libgcrypt runs in FIPS mode, AIDE disables MD5 and keeps SHA-256, SHA-512, and SHA-3 available.

Documentation and Resources

• AIDE GitHub
• AIDE manual

What are Chainguard Containers?

Chainguard's free tier of Starter container images are built with Wolfi, our minimal Linux undistro.

All other Chainguard Containers are built with Chainguard OS, Chainguard's minimal Linux operating system designed to produce container images that meet the requirements of a more secure software supply chain.

The main features of Chainguard Containers include:

• Minimal design, without unnecessary software bloat
• Daily builds to ensure container images are up-to-date with available security patches
• High quality build-time SBOMs attesting to the provenance of all artifacts within the image
• Verifiable signatures provided by Sigstore
• Reproducible builds with Cosign and apko (read more about reproducibility)

For cases where you need container images with shells and package managers to build or debug, most Chainguard Containers come paired with a development, or -dev, variant.

In all other cases, including Chainguard Containers tagged as :latest or with a specific version number, the container images include only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager.

Although the -dev container image variants have similar security features as their more minimal versions, they include additional software that is typically not necessary in production environments. We recommend using multi-stage builds to copy artifacts from the -dev variant into a more minimal production image.

Need additional packages?

To improve security, Chainguard Containers include only essential dependencies. Need more packages? Chainguard customers can use Custom Assembly to add packages, either through the Console, chainctl, or API.

To use Custom Assembly in the Chainguard Console: navigate to the image you'd like to customize in your Organization's list of images, and click on the Customize image button at the top of the page.

Learn More

Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Libraries — contact us for access.

Trademarks

This software listing is packaged by Chainguard. The trademarks set forth in this offering are owned by their respective companies, and use of them does not imply any affiliation, sponsorship, or endorsement by such companies.