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
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 |
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.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 |
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.
2.x receives critical and high-severity security fixes through 2031. 3.x is expected to 2035.
| Generation | Support life |
|---|---|
| 2.x · Debian 11 | Debian support 2022 to August 2026, then Robustel maintenance to 2031 |
| 3.x · Debian 13 | Ten years from release: to 2035 (expected) |
2.xDebian 11 |
| |||
3.xDebian 13 |
|
2022 · 2035 |
What the 2.x generation receives from 1 September 2026 to 2031:
| 1 September 2026 – 2031 | |
|---|---|
| Critical vulnerability fixes | Yes — assessed within 3 days, fixed within 14 |
| High vulnerability fixes | Yes — assessed within 5 days, fixed within 30 |
| Critical bug fixes | Yes |
| Medium & low vulnerability fixes | Assessed case by case; no committed fix |
| New features, general bug fixes | No — 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.
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. |
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.
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 |
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. |
| Next · step 12 of 13Maintenance after Debian 11 →What happens to 2.x devices now that Debian 11 has ended. |