This module does not protect your site's file integrity. Only you can do that by configuring the site correctly and by not installing insecure software. It can be used to check a Drupal site for file integrity breeches.

This module lets the site maintainer “fingerprint” an entire site (except the files below the public:// upload directory) when it is in an untainted state. It can then be configured to periodically compare the site to this “fingerprint”, and report the following:

  • modified files and directories;
  • potential back-doors (files added to the site);
  • files removed from the site;
  • files writeable by the web-server.

This module should only be used on a stable production site to alert the site maintainer as a first line of defence against file integrity breeches.


Recommended modules

  • Advanced Help:
    When this module is enabled, the project's may be displayed on the screen.
  • Markdown filter:
    When this module is enabled, display of the project's will be rendered with the markdown filter.


The project is considered complete, and I have been using it for about one month on a production site without any issues. However, before making a full release I want feedback from more users. Please take a look at this issue and respond if you've tested the module.

Similar projects

The following projects may be applied to use cases that are similar to the use case this module is designed to handle:

  • Hacked!:
    This Drupal module differs from the File integrity module by not being designed to do used on a production site to perform automatic and periodic checks. Instead, it will verify integrity of core and modules on demand by downloading a untainted copy from and compare. Note that it will not detect back-doors.
  • MD5 Check:
    This Drupal module differs from the File integrity module by only monitoring the directories of installed modules, and by comparing the current version to the previous, instead of comparing to a saved “fingerprint”. It does not send email, but log potential integrity breeches using watchdog.
  • Git:
    This is not a Drupal module. It is a general source control system that may also be used to monitor changes to a set of files.
  • inotify-tools:
    This is not a Drupal module, but a C library and a set of CLI-tools that can be used to monitor and act upon filesystem events.
Supporting organizations: 
sponsored development of the Drupal 7 version.

Project Information