This project is not covered by Drupal’s security advisory policy.
Security Advisory Monitor helps Drupal administrators identify published security advisories that may affect Drupal core, modules, and themes installed on their sites. It brings the findings together in one place and maintains a history of changes over time.
Drupal already provides security update information, but determining which advisories are relevant to a particular installation can require additional research. Security Advisory Monitor simplifies that process by comparing installed project versions against published affected-version ranges and presenting the results in an administrative dashboard.
The module is a read-only security monitoring tool. It does not test for vulnerabilities, run exploits, or automatically install updates. A matching version range does not necessarily mean a site is exploitable, and the absence of a match does not guarantee that a site is secure.
Features
- Advisory monitoring: Checks installed Drupal core and contributed projects against official Drupal security advisories and their published affected-version ranges.
- Applicability assessments: Organizes findings into Needs Attention, Needs Review, Installed but Inactive, and All Advisories. Where sufficient information is available, the module also considers site-specific prerequisites.
- Actionable reporting: Displays installed versions, available security updates, advisory severity, supporting evidence, and links to original advisories.
- Automated checks: Uses Drupal cron to monitor advisory sources and installed projects for changes. Administrators can also refresh advisories and reassess installed projects manually.
- Assessment history: Records changes in advisory applicability, including when an affected project is updated to a version outside the published affected range.
- Notifications: Records new affected-version findings in a Notifications dashboard. Optional email notifications can be configured for selected recipients.
- Additional advisory research: Includes tools for inspecting advisory evidence and discovering historical advisories. Unverified information is kept separate from verified affected-version ranges.
- Environment identification: Supports identifying individual Drupal installations, with protected storage options for environment identity data.
The goal is to make it easier to identify relevant security updates, understand why an advisory may apply, and keep a record of what changed without manually comparing installed versions against individual advisory pages.
Post-Installation
After installing and enabling Security Advisory Monitor:
- Navigate to Reports > Security Advisory Monitor and review the Getting Started information.
- Configure an environment identity. Protected storage outside the public webroot is recommended.
- Review the module's permissions and grant reporting or administrative access to the appropriate users.
- Open Settings to configure notification preferences, recipients, and advisory display options.
- Run an initial advisory check and reassess installed projects to establish the site's starting status.
- Ensure Drupal cron is configured and running regularly so monitoring continues automatically.
Notifications use dashboard-only mode by default. Email delivery is optional and requires a properly configured mail transport and valid recipients.
The administration interface provides Overview, Advisories, History, Notifications, Environment, Settings, and Getting Started pages.
Security Advisory Monitor complements Drupal's existing update-management tools rather than replacing them. Administrators should continue using Available updates, Composer audit, and their normal security maintenance procedures.
Additional Requirements
- Drupal's core Update module is a required dependency.
- The server must be able to retrieve information from official Drupal security advisory sources over HTTPS.
- Drupal cron should be configured for ongoing automated monitoring.
- PHP must meet the requirements of the installed Drupal core version. The module declares a minimum PHP version of 8.1.
No additional contributed Drupal modules or third-party Composer packages are required.
Historical advisory coverage is not exhaustive, and some older advisories lack verified affected-version information. Such records are not used to establish affected-version matches without adequate evidence.
Recommended modules/libraries
No additional modules or libraries are necessary.
Security Advisory Monitor works alongside Drupal's core Available updates functionality and Composer's built-in security auditing. Both should remain part of your regular maintenance process.
If email notifications are enabled, verify that the site's existing email transport is configured and working correctly before relying on delivery.
Project information
- Project categories: Administration tools, Artificial Intelligence (AI), Security
- Created by webdrips on , updated
This project is not covered by the security advisory policy.
Use at your own risk! It may have publicly disclosed vulnerabilities.
Releases
Initial stable release of Security Advisory Monitor

