Element 13.10
Fleet management, updates and device security
- Sheet
- 13.10
- Chapter
- 13 Digital infrastructure
- State
- Drafted
- Release
- 16 November 2026
- Editor
- Contributed by Praecise as open research
- Reviewers
- To be named at review
- Safety
- S1, as the chapter
- Licence
- CC BY-SA 4.0
- Resources
- 10
The element
- Requirement
Every small computer the community runs is known, updated and reachable by its keepers, and an update that fails, or a power cut in the middle of one, leaves the device working on its previous version.
- How to tell
There is a list of every device with its system, version and last update. Updates are applied on a schedule. The update method recovers from failure: Mender states that an update system must recover from loss of power or network during an update (Mender introduction). Remote access is encrypted and sign-in to it is phishing-resistant (13.3). Each device is measured against a recognised baseline: ETSI EN 303 645 sets 13 security provisions and 5 data protection provisions for connected consumer devices (ETSI EN 303 645: Cyber Security for Consumer Internet of Things: Baseline Requirements); NIST IR 8259A sets a core baseline of security features a device should provide (NIST IR 8259A: IoT Device Cybersecurity Capability Core Baseline).
- Options
Systems.
- A general distribution updated in place. Raspberry Pi OS is based on Debian and is updated with apt full-upgrade; pre-release firmware is for testers only (Raspberry Pi OS (documentation)). Fits a few devices kept by hand.
- An immutable, transactional system. Ubuntu Core applies updates as transactions with automatic rollback (Ubuntu Core documentation). Fits devices left unattended.
- A custom built system. The Yocto Project builds a system with only the packages needed, for Arm, RISC-V, x86 and others; it states a steep learning curve and long first builds (Yocto Project overview). Fits a community building its own device in numbers.
Updating a fleet.
- A/B updates. The new system is written to the inactive partition and committed only after a good first boot, otherwise the device rolls back (Mender introduction). The Raspberry Pi bootloader supports A/B updates and a boot watchdog (Raspberry Pi hardware documentation); Raspberry Pi Connect offers remote A/B updates on Raspberry Pi 4 and later (Raspberry Pi Connect (documentation)).
- Container releases. balenaOS is a minimal Yocto-based host that runs containers; devices download only the binary differences, offline devices update when they reconnect, and a host update that fails to boot returns to the previous version (Core concepts: a balena primer).
- Remote access. Raspberry Pi Connect gives a browser shell and screen sharing, encrypted between device and browser, linked directly or through a relay; organisation accounts add tagging, an audit log and an API (Raspberry Pi Connect (documentation)). Any such service is a dependence to be judged by the four checks (13.8).
Law. In the European Union the Cyber Resilience Act sets security duties for connectable products, with main duties from 11 December 2027 (Cyber Resilience Act, Regulation (EU) 2024/2847); it matters most to a community that makes and supplies devices.
- Settled, open, contested
Settled. A/B updates with rollback are how the sources make updates survive failure (Mender introduction, Core concepts: a balena primer, Ubuntu Core documentation). Open. Self-hosted fleet tools at community scale are not compared in any source found. Contested. A hosted fleet service against a self-hosted one: hosted is less work; self-hosted passes the four checks (13.8).
The four stages
Learn: A/B updates and rollback (Mender introduction, Core concepts: a balena primer). Design: choose the system and update method; write the device list and the baseline (ETSI EN 303 645: Cyber Security for Consumer Internet of Things: Baseline Requirements, NIST IR 8259A: IoT Device Cybersecurity Capability Core Baseline). Build: install the system and the update agent (Ubuntu Core documentation, Yocto Project overview, Raspberry Pi OS (documentation)). Deploy: update on a schedule, cut power during a test update, and review remote access yearly (Raspberry Pi Connect (documentation)).
Resources at each stage
2 Design
Size and choose
3 Build
Build or obtain
- Raspberry Pi OS (documentation) Guide, S1
- Ubuntu Core documentation Guide, S1
- Yocto Project overview Guide, S0
4 Deploy
Install, run and measure
- Core concepts: a balena primer Guide, S1
- Cyber Resilience Act, Regulation (EU) 2024/2847 Standard, S1
- Mender introduction Guide, S1
- Raspberry Pi hardware documentation Datasheet, S1
- Raspberry Pi Connect (documentation) Tool, S1
- Raspberry Pi OS (documentation) Guide, S1
- Ubuntu Core documentation Guide, S1
What changes between 30 adults and 300 people
At 30 adults a handful of devices updated by hand from a written list. At 300 people dozens of devices need a fleet tool with A/B updates, device identities and an audit log, and remote access rights follow the roles register (15.3).
Reference designs
Open for contributions Designs with drawings, specifications and a bill of materials. Add to it
Parts list
Every resource that supports this element. Those marked External carry the label “External resource. Not made or verified by Public Protocol”.
| Resource | Type | Origin | Maturity | Safety | Licence, as stated at its source |
|---|---|---|---|---|---|
| Core concepts: a balena primer | Guide | External | Established | S1 | Not stated on the page opened |
| ETSI EN 303 645: Cyber Security for Consumer Internet of Things: Baseline Requirements | Standard | External | Established | S1 | Not stated on the page opened |
| Cyber Resilience Act, Regulation (EU) 2024/2847 | Standard | External | Established | S1 | Not stated on the page opened |
| Mender introduction | Guide | External | Established | S1 | Not stated on the page opened |
| NIST IR 8259A: IoT Device Cybersecurity Capability Core Baseline | Standard | External | Established | S1 | Not stated on the page opened |
| Raspberry Pi hardware documentation | Datasheet | External | Established | S1 | Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0); some content from the eLinux wiki under CC BY-SA 3.0 Unported |
| Raspberry Pi Connect (documentation) | Tool | External | Working | S1 | Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0); some content from the eLinux wiki under CC BY-SA 3.0 Unported |
| Raspberry Pi OS (documentation) | Guide | External | Established | S1 | Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0); some content from the eLinux wiki under CC BY-SA 3.0 Unported |
| Ubuntu Core documentation | Guide | External | Established | S1 | Not stated on the page opened |
| Yocto Project overview | Guide | External | Established | S0 | CC-BY-SA-2.0-UK |
Depends on, and completes
It is one of 25 elements that complete Digital infrastructure.
The standing questions
Who can afford this: the systems listed are free to use; some fleet services charge (Raspberry Pi Connect (documentation)). Who does the work: keepers on a rota. Who decides: who may reach devices remotely is a community decision (15.2).
Environments
Remote sites gain most from rollback and offline-tolerant updates: balena states offline devices update on reconnection (Core concepts: a balena primer). No source found on fleet management by climate.
Safety
State and evidence
Drafted
An editor has written the element's text from the resources listed under it, citing them. It is checked when it is reviewed.
Evidence from a real place or system is recorded here, with what did not work. What the states mean
History
- Drafted in the release of 16 November 2026.