Automation first.
People where it matters.
Keeping Drupal secure is mostly routine: read the advisory, find the sites, apply the update, run the tests, deploy, check. Sentinel’s agents take that routine and your CI runs the tests, so your team spends its time on the decisions only people should make.
- Set policy (a person)Sites, schedules, Copilot or Autopilot
- WatchDrupal.org releases and advisories
- MatchEvery affected site you connect
- PrepareUpdate applied, pull request opened
- TestYour CI and required checks
- Approve (a person)Press Deploy, or set Autopilot consent per site
- DeployBackup where supported, merge, deploy, confirm
- ReportEvery fix timed against your SLA
- Review (a person)The month, with your customer
Patching is urgent, repetitive and easy to put off
- 01
Fixes land at awkward hours
Drupal security releases come out on Wednesdays, between 16:00 and 22:00 UTC. In Sydney that is 3 to 9 am Thursday in daylight saving time (2 to 8 am otherwise). In London it is 5 to 11 pm Wednesday in summer time (4 to 10 pm otherwise).3
With Sentinel: agents prepare the update and your CI runs the tests, whatever the hour. - 02
The same update, site by site
One advisory can mean the same Composer update on every site you run, one by one, by hand.
With Sentinel: one pull request for each affected site. - 03
Exposure measured in sprints
Attackers can study a public fix. A patch that waits for the next sprint leaves every affected site exposed.
With Sentinel: work starts when the advisory lands, and every fix is timed against an SLA you set. - 04
Blind spots across the fleet
Nobody can say, right now, which sites run the affected module and how long each one has waited.
With Sentinel: every module on every site, on one screen. - 05
Maintenance nobody sees
When patching goes well, nothing happens, so the work is invisible to the people who pay for it.
With Sentinel: a monthly report of every recorded fix and your SLA results. - 06
Tired people, risky changes
Rushed updates at the end of a long day are where mistakes slip in.
With Sentinel: required checks are the gate, and people review in working hours.
One security release, two ways
An illustrative day for a team that runs 20 Drupal sites, six of them affected in both workflows.
By hand
Someone watches, someone wakes up, everyone waits.
- ReleaseSecurity update published
- ReadA developer reads the advisory Person
- MatchThe team works out which six sites are affected Team
- PrepareDevelopers update each site by hand Person
- ReviewCI runs the tests; people review each change Team
- DeployThe team deploys and writes down what happened Person
Automation first
Agents do the routine. People make the calls, after breakfast.
- ReleaseSecurity update published
- MatchSix affected sites found Sentinel
- PrepareSix pull requests open, your CI runs the tests Agents
- AutopilotSites whose required checks pass deploy under your consent Autopilot
- CopilotYour team reviews the rest and presses Deploy Your team
- RecordVersions confirmed, fixes in this month’s report Sentinel
Illustrative workflows, not measured results. Autopilot deploys only sites whose required checks pass, under the consent you set for each site.
Agents do the work.
People own the decisions.
Automation is not hands-off. It moves people to the four points where judgement matters.
Set the policy
Decide which sites are enrolled, when updates run and how far automation may go.
- You
- Copilot or Autopilot per site, schedules, your AI key or Included AI
- Agent
- Works only inside those settings
Approve the deploy
Review a finished, tested pull request and press Deploy. Or set Autopilot consent for each site.
- You
- Review the change and the transcript
- Agent
- Backup where supported, merge the reviewed commit, deploy, confirm
Handle exceptions
When a required check fails, the deploy stops and waits for your team. Nothing is forced through.
- You
- Fix, skip or pause the site
- Agent
- Records what failed for your review
Review the month
Read the SLA report with your customer or your manager and agree what comes next.
- You
- Targets, priorities, the service review
- Agent
- Timed every fix and wrote it down
Six rules we build by
Routine work is automated by default
If a step is the same every time, agents and your CI do it. People should not copy version numbers.
Every change is reviewable
Work arrives as a pull request in your own repository, with a full transcript of what the agent did.
Tests are the gate
Patching needs automated tests in your CI. Autopilot deploys only when your required checks pass.
People approve risk
A person presses Deploy, or gives explicit consent for Autopilot, site by site.
Everything is recorded
Every step is logged. Organisation administrators can export the records. Proof is a by-product, not extra work.
You can pause it any time
Pause a site, require approval or cap open pull requests. Control is never one-way.
Why speed matters
Give security fixes a clear path to production.
In 2014, automated attacks compromised unpatched Drupal 7 sites within hours of a security advisory.1 ASD’s Essential Eight asks for fixes to online services within 48 hours of release, when the vendor rates the flaw critical or a working exploit exists.2
Built for the people who keep Drupal running
Sentinel Connector brings monitoring and patching together for Drupal fleets. Monitoring shows what needs attention. Patching prepares the updates as pull requests for your own CI to test.
We build for agencies and in-house teams who look after many Drupal sites, and who want faster security without giving up control of their code or their hosting.
How we protect your sites and data