Last year, with the security release of SA-CORE-2018-002, the most significant security vulnerability since 2014, we heard the pain of site owners and development teams around the world staying up at all hours waiting for the complex security release process to complete and the patch to drop. We heard the pain of agencies and end-user organizations required to put teams on late shifts and overtime. We heard from some users who simply couldn’t respond to patch their sites on the day of release, because of lack of resources or entrenched change management policies.
We’ve heard calls from the community for rotating the timezones for security advisories from release to release, or for having more on-call support from security team members across the globe, or simply for a longer horizon between the release of PSA and SA.
Yet at the same time, we’re cognizant that these solutions would put increased burden on a security team composed of dedicated volunteers and contributors. There are a number of generous organizations who sponsor many of the members of the security team, but relying on their altruism alone is not a sustainable long-term solution—especially if we consider expanding the role of the security team to address the larger pain points above.
Last week, with the release of SA-CORE-2019-003, we heard these concerns for site owners and the sustainability of the security team echoed again.
The Security Team and the Drupal Association have been developing solutions for this issue for well over a year.
The goals are simple:
- Provide a new service to the Drupal community, from small site owners to enterprise-scale end users, to protect their sites in the gap from security release to the time it takes them to patch.
- Create a new model for sustainability for the Security Team, generating funding that 1) covers the operating costs of the program 2) can support security team operations and 3) can support additional Drupal Association programs.
Although the execution will take care and careful partnership, we are happy to announce that we’ve found a solution.
We’re tentatively calling this: Drupal Steward. It is a service to be provided by the Drupal Association, the Security team, and carefully vetted hosting partners.
Drupal Steward will offer sites a form of mitigation through the implementation of web application firewall rules to prevent mass exploitation of some highly critical vulnerabilities (not all highly critical vulnerabilities can be protected in this fashion, but a good many can be – this method would have worked for SA-CORE-2018-002 for example).
It will come in three versions:
- Community version – for small sites, low-budget organizations, and non-profits, we will offer a community tier, sold directly by the DA. This will be effectively at cost.
- Self hosted version – for sites that are too large for the community tier but not hosted by our vendor partners.
- Partner version – For sites that are hosted on vetted Drupal platform providers, who have demonstrated a commitment of contribution to the project in general and the security team in particular, protection will be available directly through these partners.
The Drupal Association and Security Team are excited to bring this opportunity to the Drupal Community.
We believe that the program outlined above will make this additional peace of mind accessible to the broadest base of our community possible, given the inherent costs, and are hopeful that success will only continue to strengthen Drupal’s reputation both for one of the most robust security teams in open source, and for innovating to find new ways to fund the efforts of open source contributors.
We will announce more details of the program over the coming weeks and months as we get it up and running.
If you are a hosting company and are interested in providing this service to your customers, please reach out to us at email@example.com.
Please also join us at DrupalCon for any questions about this program.
If you are a site owner and have questions you can join us in slack #drupalsteward.
For press inquiries, please contact us at: firstname.lastname@example.org