Keeping Your Edge Computing Gateway Secure Over Time

Keeping Your Edge Computing Gateway Secure Over Time

Three facts carry the whole story

Industrial devices outlive ordinary software support cycles. RobustOS Pro is built for that.

Maintenance does not wipe
The Debian packages you installed are still there after a standard firmware update.
A defined support life
Ten years per generation. For 2.x, Robustel fixes critical and high-severity vulnerabilities and critical bugs through 2031.
Published deadlines
Critical: assessed in 3 days, fixed in 14. High: assessed in 5, fixed in 30. Reports acknowledged within 7 calendar days.

Industrial devices outlive ordinary software support cycles. RobustOS Pro is built for that reality: each major version carries a ten-year maintenance life, well beyond the life of the Debian release beneath it.

Three facts carry the whole story

  • Firmware maintenance does not wipe what you installed. A standard firmware update does not remove the Debian packages you installed — it updates the device without starting it over, so what you put on the device is still there afterwards. It is not a guarantee that every package stays at the version you installed: see What an Update Changes.
  • Releases have a defined support life. Each RobustOS Pro generation is maintained for ten years. For 2.x, Debian's own support for Debian 11 ended on 31 August 2026; since then Robustel fixes critical and high-severity vulnerabilities and critical bugs, through 2031.
  • Vulnerability response has published deadlines. Critical vulnerabilities are assessed within 3 days and fixed within 14; High vulnerabilities are assessed within 5 days and fixed within 30. Reports to the Robustel Security Centre (robustel.com/security-centre) are acknowledged within 7 calendar days.

Patching in practice

Fixes arrive as security update packages. Nothing installs on its own.

Software Robustel ships
Individual security update packages, from the Robustel website or through RCMS.
Robustel fixes
Kernel and system components
Firmware releases and security update packages. The kernel version does not change within 2.x.
Robustel fixes
Packages you added
Debian packages you installed yourself.
Yours to maintain
Nothing installs on its own. Every update is started by you, on the device or through RCMS, inside your maintenance windows.
Back up before patching. Package operations have no automatic rollback. After the first update of a new release, check the versions you depend on.
  • Security fixes for the software Robustel ships arrive as individual security update packages, from the Robustel website or through RCMS — see Maintenance After Debian 11. Since 31 August 2026 the Debian 11 repositories receive no new fixes; apt still works against them, but new security fixes come only from Robustel. Debian packages you added yourself remain yours to maintain. Nothing installs on its own — RobustOS Pro 2.4.x has no scheduled or automatic update mechanism, so every update is started by you, on the device or through RCMS, inside your maintenance windows.
  • Robustel software fixes (the Linux kernel and Robustel's system components) are delivered through firmware releases and security update packages. The kernel version does not change within 2.x — fixes are backported into it. A standard firmware update installs them in place: your apps, containers, settings and data are untouched, and the packages you installed are not removed. Because the update installs its own packages alongside yours, check the versions you depend on after the first update of a new release.
  • Back up before patching. Package operations have no automatic rollback. The same habit that protects updates protects patching.
Web UISystem → Debian Management
Drop a screenshot of the Debian Management page
Debian Management — install and remove packages per device. It has no upgrade action.

Where fixes come from, over the years

Two supply lines: Debian until 31 August 2026, Robustel from 1 September 2026 through 2031.

Until 31 August 2026
Official Debian 11 repositories.
Debian
→
From 1 September 2026
Security update packages for critical and high-severity vulnerabilities and critical bugs, through 2031.
Robustel

Your device's software has two supply lines:

Until 31 August 2026 · Debian

Official Debian 11 repositories — Debian's own support ended on 31 August 2026

From 1 September 2026 · Robustel

Security update packages for critical and high-severity vulnerabilities and critical bugs, through 2031
Two supply lines — Debian's repositories until 31 August 2026, Robustel's security update packages from 1 September 2026 through 2031.

From 1 September 2026, Robustel's Product Security Incident Response Team assesses every published critical and high-severity vulnerability affecting the software in the firmware image — the Debian packages Robustel ships, Robustel's own software and the Linux kernel — and fixes it, publishes a mitigation, or documents it as not affected. Full detail: Maintenance After Debian 11.

The support life of a release

2.x receives critical and high-severity security fixes through 2031. 3.x is expected to 2035.

GenerationSupport life
2.x · Debian 11Debian support 2022 to August 2026, then Robustel maintenance to 2031
3.x · Debian 13Ten years from release: to 2035 (expected)
Where the severity levels come from. CVSS rating bands defined by FIRST: Critical 9.0–10.0, High 7.0–8.9, Medium 4.0–6.9, Low 0.1–3.9. CVE records and their scores are public: cve.org, the US NVD (nvd.nist.gov), ENISA's EU Vulnerability Database (euvd.enisa.europa.eu). Actively exploited vulnerabilities: CISA's Known Exploited Vulnerabilities catalogue.
Reading version numbers. MAJOR.MINOR.PATCH: the major number tracks the Debian generation. Moving from 2.x to 3.x is a migration, not an update.
2.xDebian 11
Debian support 2022–Aug 2026Robustel maintenance to 2031
3.xDebian 13
Ten years from release — to 2035 (expected)
2022  ·  2035
Release support life — the 2.x generation receives critical and high-severity security fixes through 2031. 3.x dates are current expectations.

What the 2.x generation receives from 1 September 2026 to 2031:

1 September 2026 – 2031
Critical vulnerability fixesYes — assessed within 3 days, fixed within 14
High vulnerability fixesYes — assessed within 5 days, fixed within 30
Critical bug fixesYes
Medium & low vulnerability fixesAssessed case by case; no committed fix
New features, general bug fixesNo — these go into 3.x

Severity is classified using CVSS (first.org/cvss). Vulnerabilities that are actively exploited are prioritized regardless of score.

Where severity and vulnerability information come from. The severity levels are the CVSS rating bands defined by FIRST: Critical 9.0–10.0, High 7.0–8.9, Medium 4.0–6.9, Low 0.1–3.9. Publicly known vulnerabilities are published as CVE records, with a CVSS score where one has been assigned, in public databases: the CVE record itself (cve.org), the US National Vulnerability Database (nvd.nist.gov) and the EU Vulnerability Database run by ENISA (euvd.enisa.europa.eu). Vulnerabilities known to be actively exploited are listed in CISA's Known Exploited Vulnerabilities catalogue (cisa.gov/known-exploited-vulnerabilities-catalog).

Reading version numbers. RobustOS Pro uses MAJOR.MINOR.PATCH versioning: the major number tracks the Debian generation (2.x = Debian 11), the minor number adds backward-compatible features, the patch number fixes bugs. Different major versions are not compatible — moving from 2.x to 3.x is a migration, not an update.

How you learn that an update exists

Three places tell you. The Cybersecurity Version on the Dashboard is not one of them.

Robustel knowledge base
Subscribe at Robustel.com for update and security announcements.
RCMS
Managed fleets see available updates in the fleet platform.
Release notes
Each release lists the fixes it contains.
The Cybersecurity Version is a certification baseline, not a patch level. It does not change when fixes are installed: read release notes to know what is fixed.
  • Robustel knowledge base — subscribe at Robustel.com to receive update and security announcements.
  • RCMS — managed fleets see available updates through the fleet platform.
  • Release notes — each release lists the fixes it contains. Note that the Cybersecurity Version shown on the Dashboard (System Information panel) is the security-certification baseline of the installed firmware, not a patch level — it does not change when individual fixes are installed. To know what is fixed, read release notes, not that field.

Reporting and response

Report suspected vulnerabilities through the Robustel Security Centre (robustel.com/security-centre).

7 days
Reports acknowledged
14 days
Critical fixed (assessed in 3)
30 days
High fixed (assessed in 5)

Suspected vulnerabilities are reported through the Robustel Security Centre (robustel.com/security-centre). The published commitments: reports acknowledged within 7 calendar days; Critical vulnerabilities assessed within 3 days and fixed within 14; High vulnerabilities assessed within 5 days and fixed within 30; a defined six-step response workflow from report to advisory.

For fleet operators

RCMS rolls out firmware and security update packages. Your own packages need your own route.

Fleet-wide through RCMS
Firmware updates and security update packages.
Fleet-wide
Your Debian packages
Per device. RCMS does not carry them; a golden image builds a fleet, it does not patch one.
Plan your own route
Plan your route before you deploy: a signed apt repository you control, driven over SSH. Review your fleet periodically.
  • Firmware updates and security update packages can be rolled out fleet-wide through RCMS.
  • Debian package patching is a per-device operation, and RCMS does not carry your packages. A golden image builds a fleet; it does not patch one — restoring a clone is a per-device operation with no fleet push behind it. Plan your own route before you deploy: a signed apt repository you control, driven over SSH. See Updating Your Device → Shipping a new version of your own software.
  • Review your fleet periodically: firmware versions, patch state, and where each device generation stands in its support life.
Updating Your Device
How to install updates and patches.
What an Update Changes
What updates change on the device.
Securing Your Device
Deployment-time hardening.
End of Life
What happens when support ends.

What this guide does not cover

Next · step 12 of 13Maintenance after Debian 11 →What happens to 2.x devices now that Debian 11 has ended.