Drupal keeps install and update pages in the web root, and a few text files that name the Drupal version. A live site does not need them. Drupal setup files open to the web is a Security row in Deep scan that finds the ones your repository would still serve. It is rated Low. Drupal guards its own setup pages, so this is not an open hole. Blocking them is best practice: it hides that the site runs Drupal and which version, takes away a page for attackers to try, and stops the installer appearing if a bad deploy loses the database settings. Before you block update.php, check that your deploys run drush updatedb. The live site then never needs these pages.
What Sentinel reads. Sentinel reads your repository only. It sends nothing to your site and never asks your site for these files. It checks eight files under the Drupal web root (the folder it finds as web, docroot, html, public or www):
- Setup pages:
core/install.php,update.php,core/rebuild.phpandcore/authorize.php. - Version files:
core/CHANGELOG.txt,core/INSTALL.txt,INSTALL.txtandREADME.md. Put the rule above the location that runs PHP, because nginx uses the first regex location that matches, then check each path answers 404.
For each file it looks at the composer scaffold settings, your build scripts and the web server rules in the repository (nginx, Apache and IIS) to see whether something removes or blocks the file. The check runs as part of the security scan. It never emails you and sends no Slack message, alert or webhook.
The row. It shows one of these:
- N open: that many files are open to the web or cannot be judged. The link is See files.
- No open findings: every file is removed, blocked or marked handled elsewhere. This means the check found nothing in your repository. It does not prove nothing in front of your site serves them. The link is See files.
- Not checked yet: no scan has run the check. It runs with the next security scan that includes Custom code and Drupal settings. If you untick that check in Scan selected, this one does not run. There is no link yet.
- Checking: a scan that includes the check is running.
- Out of date: a later scan could not check these files, so the row still shows the check before it. Do not read it as clear.
- Partly checked: the repository had more files than the check reads, or one too large to read. Do not read it as clear.
- Can't tell: Sentinel found no Drupal web root in the repository. The link is See what was read.
- Needs set-up: the site has no repository. The link is Choose the repository.
Findings from a repository or branch the site used before do not count.
The page. Select See files to open the check (address ?tab=patching&view=deep-scan&check=setup-files). Any member who can open the site can read it. It shows the state, Low, Copilot, and when and from which branch and commit it was checked. Under it, Setup pages and Version files list each file with its result and the evidence in your repository:
- Open to the web: nothing in the repository removes or blocks the file. The evidence says whether composer scaffolds it into the web root on every build.
- Can't tell: Sentinel found a rule it cannot judge. For example, the rules are loaded from outside the repository, a rule it cannot read, or another web server file serves the site too. Check which one runs. Then fix it or mark it handled elsewhere. A "Can't tell" file counts as open.
- Removed at build: a composer scaffold setting or a build step removes it. The evidence names the file and line.
- Blocked by web server: a web server rule in the repository returns an error for it.
- Blocked at the edge: a rule in the repository's edge configuration blocks it.
- Handled elsewhere: someone marked it (see below). It shows who, when and why.
A file that was blocked and is open again shows Back since with the date. A file you marked handled elsewhere is not shown as back. The page also has a History of each check, each mark and each withdrawal.
How to fix, in layers. Use at least two layers, so one mistake does not open the files again.
- Stop composer adding
update.phpand the root text files. Underextra.drupal-scaffold.file-mappingincomposer.json, set"[web-root]/update.php": false,"[web-root]/INSTALL.txt": falseand"[web-root]/README.md": false. - Remove the core files at build, with composer
post-install-cmdandpost-update-cmdscripts. The page shows the exactrm -fline for your web root. - Block them in the web server. In nginx, return 404 for
update.php,core/install.php,core/rebuild.php,core/authorize.php,core/*.txt,INSTALL.txtandREADME.md. Put the rule above the location that runs PHP, because nginx uses the first regex location that matches, then check each path answers 404. - Block them at your host, CDN or firewall too. Add a rule that returns 403 or 404 for the same paths. In a web application firewall (WAF), match the exact paths, or a path pattern for the
core/*.txtfiles, and choose Block or a 404 response. Where your host offers redirect or header rules in its own settings, use the same paths there. Check the rule by opening one of the paths in a private browser window. A 403 or 404 page means it works; a Drupal page means it does not. Rules at your host, CDN or firewall are outside your repository, so Sentinel cannot see them. Mark the files handled elsewhere (below). - Keep
drush updatedbin your deploy steps, so updates never run from the browser.
Let Sentinel prepare steps 1 and 2. While files are open, the page has a Fix pull request panel. An organisation administrator can select Prepare fix pull request. A dialog lists what the pull request changes and what it cannot change. Select Prepare pull request to go on.
- What it changes. Sentinel edits
composer.jsonitself. No AI is used, so there is no AI cost. For step 1 it stops the Drupal scaffold addingupdate.php,INSTALL.txtandREADME.md. For step 2 it adds aremove-setup-filesComposer script that removes the other setup pages and version files by name after everycomposer installandcomposer update. Incomposer.lockit changes only the content hash, when Sentinel can work it out. If it cannot, the pull request asks you to runcomposer update --lock. - What it cannot change. It cannot change web server rules (nginx or Apache), or rules at your host, CDN or firewall. The pull request description lists those steps, and reminds you to run
drush updatedbin your deploy. - You stay in charge. Sentinel never merges, deploys or rebases this pull request. You review it, merge it and deploy it. The files stay open in Deep scan until it is merged, deployed and the next scan reads it.
The panel shows one of these:
- Preparing: the job is running. Select Follow it to watch it.
- Waiting for your review: the pull request is open. Select Open pull request #N to review it on your Git host.
- Not prepared: nothing was changed. The panel gives the reason. Select See what happened to read the job, then Try again, or make the changes yourself using the steps above.
Sentinel refuses to start when no files are open, when a fix pull request is already open, when another Patching job is running for the site, when the site has no connected repository, when the site is not enrolled in Patching, or when Patching has been stopped. If the job finds no web root, cannot read composer.json, or finds the repository already has its own remove-setup-files script, the panel says Not prepared with the reason, and nothing is changed. Site managers and viewers see the panel and the pull request state, with a note that an organisation administrator can prepare it.
Handled elsewhere. When something outside your repository blocks a file, mark it so it stops counting as open.
- Organisation administrators and site managers tick the files in the table. Only files that are open or "Can't tell" have a checkbox.
- Select Mark handled elsewhere (N).
- Choose what handles it: Blocked at the edge or firewall, Blocked by the hosting platform, Removed during deployment or Other. Other needs a note. A note is optional for the others and holds up to 1,000 characters.
- Select Mark handled elsewhere.
The files stop counting as open for everyone in your organisation, and the row and count update. The page shows your name, the date, the reason and the note. A mark is not a test: Sentinel does not check that the rule works, so check it yourself. A mark stays until someone withdraws it, including after later scans. A file that is no longer open, or already marked, is skipped, and the message says how many.
Withdraw a mark. Select Withdraw beside the file, or under Handled elsewhere for a mark on a file the latest check does not list (for example after the web root changed). The file counts as open again, and the message says so. Withdrawing is the same role as marking.
Who can do what. Any member who can read Patching for the organisation sees the row and the page, viewers included. Only organisation administrators and site managers can mark or withdraw. Viewers and other readers see no checkboxes or buttons, and the server refuses the request if they try. The row, the page and the marks appear only once Sentinel has turned on Deep scan and the security scan for your organisation. Until then there is no row and the page address opens Deep scan without it. Only organisation administrators can select Prepare fix pull request. Site managers and viewers see the panel and the pull request state, and the server refuses the request if they try.
In the monthly report. The full monthly report lists each site with its open, handled elsewhere and removed or blocked files at the end of the month. See Drupal setup files in reports.
Excluded Composer packages
Use Package exclusions on the site's Patching tab to keep named Composer packages unchanged during security and maintenance work, in Copilot and Autopilot. Organisation administrators and site managers can change the list where editing is enabled. Other members can read it. If editing is switched off, the saved list remains read-only and its restrictions stay in force. Exclusions do not hide security findings or mark a vulnerability as fixed.
Enter names. In Excluded Composer packages, enter one exact vendor/package name per line, for example drupal/civictheme. The example is not prefilled. Blank lines and repeated names are removed, surrounding spaces are trimmed, and ASCII capital letters become lowercase. Normalised preview shows the names to save. Versions, ranges, wildcards, URLs and comments are not accepted. A validation message identifies the line to correct. Each name can have up to 255 characters, each list up to 200 different names, and the pasted text up to 64 KiB.
A name does not have to be in the lock file to be saved. An excluded name that is absent cannot be installed by the update. A name supplied by another package can stop the run because Sentinel cannot isolate it safely. Check the actual package name in the repository before changing the list.
During enrolment. The Exclusions step follows Repository in both setup paths, including when you use a profile. First enrolment starts with an empty list; re-enrolment starts with the site's saved list. Your draft keeps the text. Check the names in Review and use Edit to return to them. Exclusions belong to the site: saving or applying a profile does not replace them. Confirming enrolment saves the site's explicit exclusions with the other enrolment choices.
Save or cancel. Select Save exclusions to save this list independently of the other configuration fields. Unsaved changes marks a draft; Cancel restores the saved list. The controls are locked while Saving… appears. If saving fails, the draft stays in the field. If someone changed the saved list, use Reload saved list and keep draft. The Current saved list panel shows the latest packages and revision beside your unchanged draft. Add any entries you want to keep, then select I reviewed the saved list; keep my draft before saving again. Saving replaces the displayed saved list; reloading alone does not allow an overwrite. During enrolment, use Reload saved policy, review the current saved packages, then Use current revision and keep draft before trying again. Do not retry an old draft without checking the change.
Repository entries. From composer.json — edit in Git is read-only. Effective observed exclusions combines those entries with the dashboard list. Clearing the dashboard field does not remove an entry from the repository. Repository restrictions apply to every site that reads that repository and Composer path; dashboard entries apply only to this site. An administrator can select Refresh repository policy to obtain a new preview. An unknown or unavailable preview is not an empty policy: known entries remain visible, but the preview can be incomplete. Check the observed commits and time. Each run checks the repository again.
When work stops. Exclusions can block an update, including unrelated updates when Composer cannot resolve them while an excluded vulnerable package stays unchanged. Sentinel does not switch off security checks to force that update through. A missing committed lock file or missing preservation evidence can also stop the work. If Sentinel cannot identify the files installed by an excluded package, it stops instead of changing them. Ask your developer to check the package's install location in the repository. A pull request without current preservation evidence is held before a hosting deployment can merge it; refresh the pull request through Sentinel where offered. The next-step guidance for an excluded-only or exclusion-blocked security run says that its findings remain open. Correct the repository or review the restriction, then start a new run where instructed. Existing findings stay visible, and a started job still uses the provider budget. Changes are checked before new work is published or deployed. A deployment already accepted by an external service cannot be stopped by editing this list, and a manual merge outside Sentinel is outside its control.
Schedules
Sentinel can start updates for an enrolled site by itself. There are two schedules, and both apply in Copilot and Autopilot. You set them in the Schedule step of the enrolment wizard, in the profile form (Settings → Patching → Profiles, Schedule) and in the site's Patching tab. Organisation administrators edit them; other members see them but not the controls. Times use the organisation owner's time zone, and a time stays the same on the clock across daylight saving changes.
Security updates. The card has an Enabled switch. It is locked on when security is the only kind of update turned on. Under When to start, choose:
- As soon as an advisory is published: the update starts straight after Sentinel matches an advisory to the site.
- Drupal release window only: the update starts once a week, when the Drupal security release window closes (Wednesday 23:00 UTC), or later if the advisory is matched after that.
Under Don't deploy between, tick Hold deploys during quiet hours and choose Quiet window starts and Quiet window ends. The window can run past midnight, and the two times must differ. There is no quiet window unless you turn one on. The update and its pull request still start at once. In Copilot, the "ready to deploy" message waits until the window ends. In Autopilot, the run is handed on with the merge held until the window ends; the merge and deploy steps themselves are not available yet. Highly critical advisories ignore the quiet window is on by default: an advisory rated Highly critical (Drupal risk score 20 to 25) is not held by the quiet window, and with the release window option it also starts at once.
Maintenance updates. The card has its own Enabled switch. When it is off, no routine updates run on a schedule; Run update still works. When it is on, choose:
- How often: Weekly, Fortnightly, Monthly, Every 2 months or Quarterly.
- Day and Time.
- Starting date: fortnightly runs count from the first matching day on or after it, and monthly runs count months from its month.
- For monthly or longer intervals, Which day of the month: A weekday of the month (for example First Tuesday, up to Last) or A date of the month (Day 1 to Day 28).
- Scope: Patch and minor within the current major (the default), Patch only, or Patch, minor and major for contributed modules, themes and libraries. With the third, a contributed module, theme or library may move to a new major version when it works with your installed Drupal core, and the pull request changes its constraint in
composer.json(for example^1.13to^2.0). Drupal core and distributions such as GovCMS never move to a new major version, whatever the scope. Security updates are not affected: they apply patch releases only.
The form lists Next runs (the next three, in the organisation owner's time zone). On a site's schedule, a warning appears if the runs are further apart than the site's maintenance SLA; you can still save it.
How runs are chosen. Security goes before maintenance, and the two never run at the same time on a site. If maintenance runs were missed, for example while Sentinel was paused, only the latest missed run starts; they do not stack up. A run does not start when its limits are reached: the AI key's spend cap, the plan, the CI tests rule or Autopilot being paused. Sentinel then skips that run, records it in the Patching activity, and sends organisation administrators a message in Messages, with an email, titled "Scheduled (kind) update for (site) did not run". It says why. Run update stays available, unless the plan or the CI tests rule stopped the run. Resume does not run a scheduled run that was skipped during a pause. To catch up a skipped security update, merge or close any open security pull request, then use Run update.
A pull request of the same kind from an earlier run that is still open is not a skip. Nothing is recorded and no email is sent. A security run starts by itself once that pull request is merged or closed, if the update is still needed and the advisory was found in the last 14 days. After that, use Run update. A maintenance run does the same within 24 hours of its slot. After that, it waits for the next slot.
