AIDE File Integrity Monitor

AWS Security

host based file integrity monitoring that reports exactly what was added, changed or removed

Base
Hardened build
minimal ports, security patches applied at build time
Access
Unique credentials
generated on first boot, readable only by root
Verified
Boots working
services pass a health gate before release
Support
24/7, 365 days
by email and live chat, 24 hour response SLA

Overview

AIDE (Advanced Intrusion Detection Environment) is an open source host based file and directory integrity checker. It builds a cryptographic baseline of the attributes of the files it watches, permissions, ownership, size, timestamps and content hashes, and on every run reports exactly what has been added, removed or changed against that baseline. It is a host intrusion detection staple and a direct answer to compliance controls that mandate file integrity monitoring, such as PCI DSS requirement 11.5 and the CIS Benchmarks. There is no daemon, no network port and no credential: it is a purely local command line tool driven over SSH.

Why the cloudimg image

The cloudimg image builds the baseline per instance at first boot, so it fingerprints your own machine rather than the build server and the very first check is meaningful instead of drowning in spurious differences. It ships a focused, hardened monitored scope covering executables, libraries, boot and configuration, a systemd timer that runs a daily check and writes the report to a log ready for your pipeline, and a fail closed design that refuses to run a check without a valid baseline. AIDE installs from the operating system archive so it stays covered by standard security updates, and the image is paired with a step by step deploy guide and 24/7 support.

Common uses

  • Compliance file integrity monitoring for PCI DSS 11.5, CIS and similar controls
  • Host intrusion detection on system binaries, libraries and configuration
  • Reviewable daily change auditing and golden image drift detection

Key features

  • Per-instance baseline built at first boot, never baked into the image. The AIDE baseline database fingerprints your own machine, generated on your instance at first boot rather than shipped from the build server, so the very first integrity check is meaningful instead of drowning in thousands of spurious differences. This is the load-bearing design decision that makes the appliance correct.
  • Scheduled, logged and fail-closed out of the box. A systemd timer runs a daily integrity check and writes the added, changed and removed report to /var/log/aide, ready for your log pipeline. The check refuses to run unless a valid per-instance baseline is present, so a silent no-baseline state can never masquerade as a clean result - integrity monitoring you can trust for PCI-DSS 11.5 and CIS compliance.
  • Unmodified AIDE from the operating system's official package archive with 24/7 support from cloudimg engineers. AIDE installs from the operating system's official package archive so it stays covered by standard unattended security updates, with no unpatchable vendored binary. Get help with baseline updates, tuning the monitored scope, interpreting reports, and moving the baseline off-box for stronger tamper assurance. Critical issues receive a one-hour average response.

See it running

Real screenshots taken while testing this image against its deployment guide.

AIDE File Integrity Monitor screenshot 1 AIDE File Integrity Monitor screenshot 2 AIDE File Integrity Monitor screenshot 3

Description

This is a repackaged open source software product wherein additional charges apply for cloudimg support services.

## Overview

AIDE (Advanced Intrusion Detection Environment) is the open source, GPL-2.0 licensed host-based file and directory integrity checker. It builds a cryptographic baseline database of the attributes of the files it watches - permissions, ownership, inode, size, timestamps and content hashes - and on every subsequent run reports exactly what has been added, removed or changed against that baseline. It is a host intrusion detection staple and a direct answer to compliance controls that mandate file-integrity monitoring, such as PCI-DSS requirement 11.5 and the CIS Benchmarks. This AMI delivers AIDE fully configured as a ready-to-run integrity-monitoring appliance - SSH in and the baseline and scheduled check are already in place.

## Why Choose This AMI Over Self-Installation

Standing AIDE up correctly is more subtle than installing a package: the baseline must be built on the real machine, the monitored scope must be tuned so the daily check is meaningful without drowning in noise, and the schedule and reporting must be wired up. This AMI handles all of it:

  • Per-instance baseline, built at first boot - The baseline database is never baked into the image. It is generated on your own instance at first boot so it fingerprints your real machine, not the build server.
  • Focused, hardened monitored scope - Executables, libraries, boot, kernel modules and /etc are watched out of the box, with volatile paths excluded so the report stays signal, not noise.
  • Scheduled and logged - A systemd timer runs a daily integrity check and writes the diff report to /var/log/aide, ready for your log pipeline.
  • Fail-closed by design - The scheduled check refuses to run unless a valid per-instance baseline is present, so a silent no-baseline state can never masquerade as a clean result.

## How File-Integrity Monitoring Works Here

  • On first boot, AIDE initializes a baseline database describing your instance's monitored files
  • A daily systemd timer runs an integrity check against that baseline
  • The check reports every added, removed or changed file to /var/log/aide
  • After intentional, reviewed changes (a package update, a config edit) you update the baseline with aideinit or aide --update
  • There is no daemon, no network port and no credential - AIDE is a purely local command-line tool

## Getting Started

1. Launch the AMI on your preferred EC2 instance type

2. Connect over SSH using your key pair

3. Confirm the per-instance baseline built at first boot with sudo aide --check --config=/etc/aide/aide.conf

4. Review the daily report at /var/log/aide/aide.log

5. After any intentional change, refresh the baseline with sudo aideinit

## Security Practices

AIDE is installed unmodified from the operating system's official package archive, so it is covered by standard unattended security updates. The baseline database is generated per instance and stored read-restricted; for real tamper assurance, move a copy of the baseline off the instance or to read-only media. SSH access uses key-based authentication. AIDE opens no network socket and runs no daemon.

## Use Cases

  • Compliance file-integrity monitoring - Satisfy PCI-DSS 11.5, CIS and similar controls that mandate FIM
  • Host intrusion detection - Detect tampering of system binaries, libraries and configuration
  • Change auditing - Get a reviewable daily record of what changed on a server
  • Golden-image drift detection - Confirm a fleet instance still matches its intended state

## cloudimg Support

24/7 technical support by email and live chat covers baseline initialization and updates, tuning the monitored scope, interpreting integrity reports, wiring the schedule and reports into a log pipeline, and moving the baseline off-box for stronger assurance. Critical issues receive a one-hour average response.

## Next Steps

Contact support@cloudimg.co.uk to request a sample integrity report, schedule a monitored-scope tuning walkthrough, or ask any pre-purchase questions about the product.

All product and company names are trademarks or registered trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.

Related technologies

file integrity monitoringaidehost intrusion detectionhidsfimpci-dss compliancecis benchmarktamper detectionchange auditingsecurity compliance