Skip to content

Data sources

51 help pages

Open Data sources from Records in the sidebar (open the group first). The page lists the outside security lists Sentinel compares your sites with, and shows whether Sentinel's copy of each one is up to date. Every signed-in person who has finished setup can open it, whatever their role or plan. You do not need to select an organisation. The lists are public and are the same for every customer, so the page shows nothing about your own sites, and nothing on it can be changed.

When GitHub Dependabot alerts are available to your organisation, one more row can describe your own organisation's GitHub repositories. See Your GitHub Dependabot alerts row. That row is the only part of the page that is about your organisation.

At the top, a line says All 5 sources up to date, or N source needs attention or N sources need attention, followed by Checked and how long ago. A source that is Off counts as needing attention. The page reloads its status every minute while it is open, and again when you return to its tab.

The five sources

Each source is a card, in this order:

  1. drupal.org security advisories: the security updates for Drupal core and modules.
  2. drupal.org releases: release history and Composer advisories, which decide which release is current for each module.
  3. NVD and CISA Known Exploited Vulnerabilities: known vulnerabilities in PHP, web server and database versions. CISA marks the ones attackers are known to use.
  4. Vendor security pages: each project's own list of fixed versions for PHP, Nginx, Apache httpd, MySQL, MariaDB and PostgreSQL.
  5. Ubuntu and Debian security data: whether the operating system vendor has already fixed a vulnerability in the package build a server runs.

Read a card

Each card shows the source name, what it is used for, and a status:

  • Up to date: no extra line.
  • Update overdue: "The last refresh was later than expected. Sentinel is still using the data it has."
  • Not updating: "The last refresh failed. Sentinel is still using the data it has and will try again at the next scheduled run." A source made of several lists says "One or more of its sources failed to refresh." instead. A source that has never run says "No refresh has completed yet."
  • Off: "This source is switched off for now. Sentinel is not refreshing it." An Off card shows no times or counts.

The status is the word on the card; the colour only repeats it. The page never shows the technical cause of a failure. It does not say that anyone has been told about a failure, and it does not tell you what to do: the page is for reading.

Below the status a card can show:

  • Last updated: how long ago, with the date and time in your profile time zone. Hover over it to see the time in UTC.
  • Refreshed: how often Sentinel refreshes the source, for example once a day.
  • Holds: what the copy contains, such as the number of advisories or vulnerabilities. drupal.org releases shows no count: which modules it covers depends on every customer's sites, so the page does not count them.
  • Last sweep (drupal.org releases only): when Sentinel last queued every site for a re-check. It does not prove that the release data was refreshed, so read it with Last updated.
  • Links to the original source. They open in a new tab.

Vendor security pages and Ubuntu and Debian security data have a Sources (N) list. It opens by itself when the card is not up to date. Each Ubuntu or Debian entry shows its own last success; each vendor page shows its number of CVEs.

While Sentinel is not yet using Ubuntu and Debian data to decide whether a vulnerability is fixed, that card says Collected, not yet used to decide whether a vulnerability is fixed.

Your GitHub Dependabot alerts row

This row appears only when GitHub Dependabot alerts are available to your organisation. An organisation without them sees the five cards above and nothing different. The page sends the organisation you have selected, and the row is added last when all of these are true:

  • Patching is available to the organisation.
  • You are a member there with a role that can read Patching: Organisation admin, Site manager or Viewer. A person whose role has expired, or who has no role there, does not see it.
  • The organisation has at least one enrolled Patching site whose Git connection is GitHub.

If any of these is not true, the row is simply not there. No error is shown, and the other five cards are unchanged. If you belong to several organisations, change the selected organisation in the top bar and the row follows it.

The row is called GitHub Dependabot alerts. It reads like the other cards:

  • Up to date: every repository was read successfully on each weekday since its last read. Weekends do not count, so a read on Friday is still current on Monday. A repository is behind when a whole weekday passes without a read, when its last read failed, or when the GitHub App can no longer read its alerts.
  • Partly updated: some repositories are behind. The line reads "Some repositories are not up to date." followed by the names, for example "Not up to date: my-org/site-one.", and "Sentinel is still using the data it has."
  • Not updating: every repository is behind. If none has been read yet, the line says "No refresh has completed yet."; otherwise "The last refresh failed."
  • Last updated shows the newest read. Refreshed reads "Each repository once a weekday; a new one within the hour."
  • Holds shows counts only, for example "5 open alerts across 2 repositories". Counts come only from a finished read: while some repositories have not been read yet it reads, for example, "3 open alerts in 1 of 2 repositories read so far", and before any read "Alert counts appear after the first full read".
  • Sources (N) lists each repository with a link to its GitHub Dependabot page (opens in a new tab), its open alert count and when it was read, for example "3 open alerts · Read 2 hours ago", or "Not read yet" before its first full read. The list opens by itself when the row is not up to date.

The page shows counts only, never the alerts themselves. To see an alert and what Patching does about it, open the site's Patching tab. A repository you add is read within the hour. The row is for reading: it has no controls, and a repository name is shown only to members of your organisation. When the row is shown, the line at the top counts it, for example All 6 sources up to date.

How Sentinel uses these

Select How does Sentinel use these? at the foot of the page for four sentences on how advisories, release history, stack vulnerabilities and vendor data are used. Read the full article opens the knowledge base article "What Sentinel checks your sites against". It shows only while the knowledge base is on for you.

If the page does not load

The page shows Couldn't load the status of Sentinel's data sources. and Try again in a moment. Select Try again. Sentinel does not show a guess in place of the status, and the message does not say anything about how your sites are being checked. If it keeps failing, raise a ticket from Support and say which page you were on.