Home Drupal: Security Audit
Drupal logo

Drupal: Security Audit

About a year ago, I (virtually) attended the DrupalGovCon 2021 conference. The highlight for me was the session on improving security of your Drupal website. I’ve embedded the video below and summarized some of the major points.

DrupalGovCon video: Tips for Securing Your Drupal Application

Security Modules

Review settings of security modules including:

  • jsonapi_extras
  • flood_control
  • login_security
  • username_enumeration_prevention
  • honeypot
  • seckit

Dev Modules

Ensure none of your development modules are on production:

  • field_ui
  • views_ui
  • devel
  • anything migration related
  • stage_file_proxy

I don’t have a perfect solution in place for this yet. I did try the config_split module for a time, allowing me to have separation with some development-related modules on our local development containers but not on production. Unfortunately it was becoming buggy.

Config Cleanup

  • Remove unused views
  • Check that there is correct access control on all views
  • Review permission roles, especially anonymous and authenticated
  • Confirm that user registration is limited to admins
  • Confirm that there are no test user accounts in production
  • Confirm that file size upload limits are reasonable
  • Confirm that private and public file directories are used properly

Custom Modules and Themes

  • Grep for any standard debugging phrases like var_dump which may still be left in your custom code
  • Check code in an editor like VS Code that warns you of unsanitary code
  • Look for any cases where you missed using the t function to make text translatable. Even if your site is entirely in one language, it’s still good practice.
  • Review any TODO / FIXME etc in the code


  • Review users. Anybody, e.g. former staff, still have active accounts that they shouldn’t? Does anybody have more permissions than they need?
  • Confirm that the superuser account is blocked and that nobody else has the superuser role in production.
This post is licensed under CC BY 4.0 by the author.