Skip to content

The five site tabs

51 help pages

The site page has these tabs: Overview, Updates, History and Setup.

While Patching is available to your organisation, a Patching tab sits between History and Setup. See Patching.

The address keeps the tab, so you can bookmark it. Old addresses such as ?tab=summary, ?tab=modules, ?tab=stack, ?tab=releases, ?tab=drupal-configuration and ?tab=connection still work: they open the matching new tab, so old emails and bookmarks keep working.

The header shows the site name with its status, then one line with the address, Drupal version, PHP version and last sync. Open site opens the site in a new browser tab. Get help with this site shows while the support portal is available and starts a support request for the site. Above the header, a path reads Sites / [site name]. Select the site name to open Switch site, a list of your organisation's sites; picking one opens that site on the same tab. Edit, delete and back actions are not in the header: use the Setup tab, or Sites in the path.

TabWhat to do
OverviewSee the site's verdict at a glance, then its security and maintenance counts, platform versions, health checks (TLS certificate, last data received and last Drupal.org check times, Connector, patching SLA, enabled modules) and a Connector activity block with the site's latest log rows and Drupal.org coverage. See The Overview tab.
UpdatesWork through what needs doing, using the Update lists chips: Needs action (the default), All modules and Platform. A red number on the tab counts security updates when there are any. See Updates tab: status, tiles and panels.
HistoryReview releases (observed version changes, component details, linked fixes and rollbacks), then update history, then resolved advisory evidence. While configuration drift reporting is on, it ends with the Drupal configuration section (see Configuration drift).
SetupOne page for each setting, chosen from a menu: Connection (install and connect the Drupal Connector with this site's Site UUID, and test the connection), How the site reports (cron, Sync now and deployments), What this site reports, Upgrade readiness (while it is on for your organisation), Certificate, Response targets, Slack alerts and Site details. While support status is on and the site has a sync issue, a red Sync issue box on Connection says when the last sync failed and why, with its code (for example processing_failed), and how old the last accepted data is, or that none has been accepted yet. See Add or edit a site for the pages.

All modules. On the Updates tab, the All modules chip (address ?tab=updates&list=modules) searches the reported inventory and filters it by status, type, and enabled state. The list opens on Contributed modules; select All types in the Type filter to also see Drupal Core, custom, and untyped modules. Review installed and recommended versions. Installed marks an alpha, beta or release candidate with Pre-release and a development snapshot with Dev; Not reported means the site sent no version. Recommended shows Up to date in green when nothing newer is published, or the newer release: red for a security update, amber for a maintenance update. A recommended release can be one Drupal.org's security team does not cover; it then says Not covered by Drupal security team. A site on a stable release is only offered stable releases. A site on a pre-release is offered the newest stable release if one is out (Stable release now out), otherwise a newer pre-release (Newer pre-release). Development snapshots are never recommended. For a module that is not supported, Recommended shows the upgrade path with Major upgrade to a supported release. For a revoked release (one withdrawn from Drupal.org), it shows the release to move to with Installed release was withdrawn. Status follows Drupal's order: Security update first, then Revoked, then Not supported, then Maintenance update, so a module that is both revoked and has a newer release reads Revoked. Under Not supported a short line says why: Release line no longer supported, Project no longer supported or, for Drupal Core, Drupal core version past end of life. The Status filter has Revoked and Not supported. These two show only while support status is on. Status reads Security update, Known vulnerability, Revoked, Not supported, Maintenance update, Current, Dev build, Custom or Can't check; Can't check gives its reason, such as Site did not send a version or Not checked yet. Security reads Known vulnerability, No known advisory, Not covered (no Drupal.org security team cover, so no advisories are issued for it) or Can't check. Current and Up to date need a current assessment; an older one shows Can't check with Assessment out of date. Drupal Core is grouped in one row. Sub-modules are not listed: a module is shown as enabled when it or one of its sub-modules is enabled.

The Overview tab

The Overview tab answers "is this site safe, and what should I do next?" from the top down.

  • Verdict: a dark card with one line such as "No vulnerable Drupal.org components. 2 components to update." It counts affected Drupal.org components, not advisories, and leaves out PHP, web server and database matches, which show on Platform and in the Platform list on the Updates tab. The ring shows the share of reported extensions that Drupal.org could check. When some were not checked, the line below says the counts are a minimum. With no usable counts it says "Security status cannot be confirmed yet." The Security, Coverage and Freshness pills match the strip shown on the other tabs. Review updates opens the Updates tab when there is something to apply, and See what is unchecked jumps to Drupal.org coverage.
  • Not supported: while support status is on, a fourth count beside the others shows how many of Drupal core, PHP and enabled contributed modules are no longer supported, and names them, for example "Drupal core, 2 modules". See what to upgrade opens the No longer supported panel on the Updates tab. With nothing unsupported it shows 0 and reads "No unsupported releases detected in the data Sentinel holds".
  • Counts: Known vulnerabilities, Outdated components and Extensions checked (checked out of all reported, then Assessed, Partial assessment or Unknown). The green shield appears only when a complete, current check found no vulnerable component; an unknown or minimum count shows a grey shield.
  • Drupal upgrade readiness: shown when readiness is turned on for your organisation and the site's display switch is on. It reads Pending until Sentinel has checked the site. See Drupal upgrade readiness.
  • Drupal status report: the errors and warnings from the site's own Drupal status report, shown only where the report is turned on for your organisation. See Drupal status report.
  • Platform: the Drupal core, PHP, web server and database versions. While support status is on, Drupal core and PHP carry a badge: Supported, Support ending soon (within 90 days), Security fixes only (PHP), Not supported (a Drupal core minor release without security fixes) or End of life. A line below gives the date, such as "Security support ends 31 Dec 2027", or says "Security support has ended". Select See platform details to open the Platform list on the Updates tab.
  • Health checks: each row shows its label on the left and its value on the right. The TLS certificate comes first; select it to see its details. Then Last data received (the newest report Sentinel accepted from the site), Last Drupal.org check (when Sentinel last checked it against Drupal.org), Connector, Drupal status report (where the report is turned on for your organisation: the counts, such as "2 errors, 3 warnings", or "Clear", "Not reported", "Off" or "Unavailable"; select it to jump to the panel), Patching SLA and Modules enabled. When no patching SLA is set, organisation administrators can select Set SLA to open the Response targets page (on the Setup tab). The row is left out when your plan has no patching SLA.
  • Connector activity: under the health check rows, up to three of the latest Connector log rows for this site over the last 7 days: syncs, connection checks and Drupal.org checks (urgent phone alerts are left out). Each row shows the operation, the time, whether it came from the site, by Sentinel or by a person, and its outcome badge. Open this site's log opens the Communication Logs page for this site. With nothing in 7 days it reads "Nothing recorded in the last 7 days. The site sends only when something changed, so a quiet week can be normal. Otherwise the site sent nothing, or Sentinel refused its key, which is not logged against a site." It checks again every minute while the page is open" If the rows cannot be loaded it reads "Activity could not be loaded. The log may still have it." A note says it lists only requests Sentinel received: a report the site skipped is not there. Every member who can see the site sees this block, viewers included. It is not shown in the platform administration console, or while another organisation is active.
  • Drupal.org coverage: the extensions Sentinel cannot fully vouch for, grouped by reason with a count beside each. Select See these extensions to open the All modules list on the Updates tab.

While Patching is enabled for your organisation, a fourth tab, Patching, sits between History and Setup. It shows a ! mark when Autopilot is paused or the site needs attention. See Patching.

Connector update icon. On Overview, a red information icon next to the Connector version means a newer Connector is available. Hover over it or move keyboard focus to it, or click or tap it, to read "An updated connector version with new capabilities is available." The icon also shows when a site that has synced reports no Connector version. Nothing shows when the version is current or the site has never synced. To clear it, update the Connector with Composer (composer update drupal/sentinel_connector --with-dependencies), deploy, run the database updates (drush updb -y), then run drush sentinel_connector:sync. The icon disappears once the site reports the new version.

Inventory is loaded in pages; use Next inventory page and Previous inventory page when offered. A filter on loaded inventory does not prove that unloaded pages have no matching modules.

The Platform list

Open a site, select Updates, then the Platform chip in Update lists (the address ends ?tab=updates&list=platform). It shows the versions of the site's PHP, web server and database and the known vulnerabilities (CVEs) those versions match. The wording is always "matches known vulnerabilities", never "is vulnerable": Sentinel checks the version number, and hosting providers often fix a problem without changing it. Matches that are probably vendor fixes (low confidence) are never shown.

  • Metric cards: four cards sit above the Stack card: Open matches, Known exploited, Marked not affected and Components checked (for example "2 of 3"). Open matches, Known exploited and Marked not affected read, for example, "0 minimum" while any component has no version check or may have matches held back. Matches can be held back when your vendor may have fixed the problem without changing the version number, even with Sentinel's Ubuntu and Debian checks on, because a vulnerability the vendor has not ruled on stays hidden. Components the site owner stopped sharing count as not checked. The cards show counts, not an all-clear, because a version check cannot prove a component is safe.
  • Stack card: one row for each component with the columns Component, Version, Source (Reported by the Connector, Declared in Stack versions, or Unknown), Last seen and Open matches by severity. There is no separate Fixed in column: when a fix version exists, "Fixed in [version]" shows under the open matches, and the number marked not affected sits there too. Products Sentinel does not match, such as LiteSpeed, Microsoft IIS, Caddy or SQLite, show Not checked yet. A managed or forked database build whose version cannot be matched, such as Amazon Aurora MySQL or Percona Server, reads like a version that was not reported (see No version below); declaring a version does not help while the Connector reports one.
  • No platform data reported: when the site owner turns off Report platform versions in the Connector, the web server and database rows are replaced by a grey panel: web server, database and operating system versions are not checked and no stack alerts are sent; PHP is still reported by Drupal and checked. Versions reported before then are kept for the reports that cover those dates and are no longer shown here. Open matches leave the counts without being called resolved, and show again if the same version is reported again. On Overview, Platform shows Not reported for those components.
  • No version: the row reads "[Component] version not reported. Add it in site settings to check it." Organisation admins and site managers get a link that opens What this site reports on the Setup tab, where Stack versions is (see Stack versions). Viewers read "An organisation administrator can add it in site settings to check it."
  • What this means: a link to the knowledge base article "What 'matches known vulnerabilities' means", shown only while the knowledge base is available. The article also explains how to confirm a match with your host, using its security notices or the package changelog.
  • Known vulnerabilities table: for each match, the CVE and title, the component with the matched version stacked beneath it, the severity with its CVSS score, a red Known exploited badge (CISA Known Exploited list) under the severity, shown only when it applies, the published date, the version it is fixed in, the status (Open, Not affected or Resolved), and Vendor and NVD links. Filter by component, severity (including Not scored) and status. The table shows 25 rows a page; use Previous and Next. The number of matches sits beside the title. A site with no matches at all shows "No known vulnerabilities match the checked versions." and "This is a version check. It does not prove the whole site is secure.", and the filters and table are hidden. Filters that match nothing show "No known vulnerabilities match these filters." with a Clear filters button.
  • Ubuntu and Debian checks: these appear only when Sentinel turns on its Ubuntu and Debian checks. Ubuntu and Debian often fix a problem in a new package build without changing the version number. For a component installed from Ubuntu or Debian packages, Sentinel then reads that vendor's own security data for the exact package build. On the Stack card, under the source, one line says how the component was checked:
    • "Checked against Ubuntu 24.04 security data, package [build]": the vendor's data was used for that build.
    • "Checked against Debian 12 security data by version number": the server named only its operating system, not the package build (Debian's Apache does this). The vendor's data can confirm a problem but cannot confirm a fix.
    • "Ubuntu 24.04 security data is out of date: earlier results kept": Sentinel could not refresh the vendor's data. Earlier answers stay, and nothing new is decided until it refreshes.
    • "No Ubuntu 24.04 security data yet: version check only": Sentinel has no data for that release, so the usual version check applies.
    • "Runs on Ubuntu 24.04, but the package build was not reported: version check only": the site runs on that system but did not say which package build it has. A newer Sentinel Connector can send the build.
  • Ubuntu and Debian answers in the table: under Fixed in, a line gives the vendor's answer: Fixed by Ubuntu (your build has the fix), Ubuntu fix available (a newer build fixes it), Fix needs Ubuntu Pro (the fix is only in Ubuntu Pro, for older releases such as Ubuntu 20.04), No Ubuntu fix yet, or Debian: not affected. Debian reads the same way. Fixed in then shows the vendor's fixed package build when there is one. A link named Ubuntu or Debian opens the vendor's page for that CVE. A match the vendor says is fixed in your build becomes Resolved by Ubuntu (or Resolved by Debian), and one it says is not affected becomes Resolved: Ubuntu not affected (or Resolved: Debian not affected); the Status filter still lists both as Resolved. One already fixed when first checked is never listed. A match the vendor says is not fixed in your build shows even when Installed from operating system vendor packages is ticked or the version carries a package build. A Not affected mark stays on a match the vendor resolves, and applies again if the match comes back at the same version, unless the severity rose or it was added to the Known Exploited list.
  • Download the list: Download CSV and Download PDF, at the top right of the Known vulnerabilities section, save every match that fits the current Component, Severity and Status filters, not only the 25 rows on screen. With all filters on All, the file holds everything. The buttons appear only when at least one match fits, and every member who can open the site can use them, viewers included. The CSV (times in UTC) suits spreadsheets; the PDF is a landscape A4 report that shows the site, the filters used, the count and when it was made, in your time zone. Low-confidence matches are never included. Files are named like example-site-known-vulnerabilities-2026-10-26.csv. While the Ubuntu and Debian checks are on, the CSV also ends with two columns, Distribution verdict and Distribution page, and the PDF shows the vendor's answer under Fixed in with a link to the vendor's page. Platform administrators see the same buttons on the admin console's site page.
  • Mark a match as not affecting the site: organisation administrators and site managers see a checkbox and Not affected on each open row. Choose a reason: patched by the hosting provider or operating system vendor, the affected feature or module is not used, mitigated another way, or other (a note is then required). A note is optional for the other reasons and can be up to 1,000 characters. To do several at once, tick rows and select Mark selected not affected; the select-all box covers the open rows on the page. If a row changed since the list was loaded, it is skipped and the message says so.
  • Marked matches: the row shows who marked it, when, the reason and the note. Withdraw makes it open again. A new vulnerability, or a new version of the component, shows again: marking a match never covers a different CVE. A match marked not affected also reopens when the vulnerability's severity rises to a higher band or it is added to the CISA Known Exploited list. If the component changes to a version that no longer matches, the match becomes Resolved instead.
  • Read-only members: viewers see the table, including who marked a match and why, but no checkboxes, Not affected or Withdraw.
  • Ticket column: when ticket links are on for your organisation, the table has a Ticket column and Link ticket (N). See Ticket links.

Matches come from the NVD, the CISA Known Exploited list and vendor security pages, which Sentinel updates daily. Marked and low-confidence matches do not raise alerts (see Known vulnerability alerts). The tab is available on all plans. No match does not prove the site has no known vulnerabilities.