Drupal support services
Drupal security maintenance - what's included and how it works
A practical explanation of how I assess, test and apply Drupal security updates, and what you can expect from the service.
Keeping your Drupal website updated is an important part of maintaining its security. But installing updates is only part of the job. Changes need to be checked, tested and applied carefully to avoid causing problems with your website.
I monitor relevant security advisories, assess the updates your website needs, test them before deployment and keep you informed of the work carried out. You'll deal directly with me throughout.
What does Drupal security maintenance cover?
Drupal websites depend on Drupal core, contributed modules and other software dependencies. Vulnerabilities can affect any of these components, even when the website appears to be working normally. I assess relevant security advisories and apply suitable security fixes to reduce known risks.
The service is focused on security-related maintenance, not general website improvements or new functionality.
Before maintenance begins
I start with a paid technical audit to understand the website's condition. I review its Drupal version, installed modules, dependencies, custom functionality and update arrangements. I also check that suitable backups, staging facilities and access are available.
If something makes safe maintenance difficult, I'll explain the problem. The audit does not automatically mean a website will be accepted for ongoing maintenance.
How I manage security updates
- Review advisories. Check relevant Drupal security information and identify which vulnerabilities may affect the website.
- Assess the fixes. Review available updates, dependencies and possible compatibility issues.
- Prepare and test. Take a suitable pre-update backup, apply changes in staging and check agreed important functions.
- Deploy. Apply tested updates to the live website and check the result.
- Record the work. Document changes, test outcomes and any issues still requiring attention.
How often are updates carried out?
I normally plan security maintenance around a monthly cycle. Significant vulnerabilities may need attention sooner. When an important advisory appears, I'll assess whether it affects your site and prioritise it according to risk and my agreed availability.
Some vulnerabilities have no immediately available or compatible patch. If an update cannot safely proceed, I'll explain the risk and any reasonable temporary precautions.
This is a personally managed service, not a staffed 24-hour support operation. Guaranteed out-of-hours response or emergency deployment is not included. Working arrangements are agreed before maintenance starts.
Backups, testing and failed updates
Before deploying changes, I'll take a suitable backup using the agreed facilities and test the update on staging. After deployment, I'll check the live site against the agreed tests.
If an update I apply causes a problem, I'll investigate it and, where technically possible, restore the previous working version safely. Database changes or activity on a live website can make an immediate rollback impractical.
Some problems require changes to existing custom code or work outside security maintenance. I will explain those findings rather than making unrelated changes under the subscription.
Drupal 7 and Drupal 10 legacy maintenance
Drupal 7 reached the end of ordinary community security support in January 2025, and Drupal 10 support ends on 9 December 2026. This does not necessarily mean a website must stop operating, but maintenance brings additional risk.
Suitable security patches may need to come from specialist third-party providers. Their availability, coverage and compatibility cannot be assumed. Before accepting a legacy site, I'll assess its condition and verify whether appropriate patches can be obtained and maintained.
Where suitable patches exist, I can assess, test and apply them under an agreed legacy package. Security maintenance cannot remove every risk associated with unsupported software.
What is not included?
The service does not include general bug fixes, content changes, new features, custom development, major Drupal upgrades, server administration or unrelated technical problems. It also excludes penetration testing, recovery from a security breach and 24/7 emergency support.
Security updates reduce known vulnerabilities but cannot guarantee that a website will never experience a security incident.
What I need to maintain your website safely
The website must have suitable access, a working staging environment and usable backup facilities. I'll check these arrangements during the initial audit. Hosting and routine backup services remain separate; responsibility for those facilities and for restoration will be agreed before maintenance begins.
Keeping you informed
You'll work directly with me. I keep a record of updates and provide a monthly report covering work completed, relevant checks and outstanding risks. If an update cannot be applied safely, I'll explain why.
Over time, I become more familiar with the website's configuration and update history, helping me understand the effect of future changes.
Getting started
Tell me about your Drupal website and its current maintenance arrangements. If it looks suitable, the next step is the paid technical audit. I can then confirm whether ongoing security maintenance is appropriate.