A small drone fleet is a set of computers with propellers. The software checklist covers link authentication, failsafe settings, Remote ID health, configuration control, access to ground stations and an inventory of the dependencies in your tools. None of it needs a large team, but it does need an owner.
Authenticate the link
If you use MAVLink, turn on message signing and test it. The MAVLink guide describes a 32 byte shared secret that should be loaded over a secure link such as USB or wired Ethernet and kept out of parameters and logs. Remember it authenticates, and does not encrypt. Also check which unsigned messages your setup still accepts, because the guide allows conditional acceptance.
Set and record failsafes
PX4 documents failsafes for data link loss, manual control loss, GPS loss, geofence breach and battery levels, with actions from Warning up to Termination. Choose actions by site type. Save the full parameter set in version control and compare it after every firmware update, because defaults can change between releases.
Treat Remote ID as an arming condition
Part 89 requires a Remote ID broadcast from takeoff to shutdown and a self test before takeoff. Where your autopilot supports it, block arming when the module is unhealthy. PX4 added such a check in version 1.18, with an arming error option. Do not rely on a pilot noticing a warning light.
Control who can change what
Flight plans, parameters and firmware are the three things an attacker or a careless colleague can change that matter most. For each, answer these questions:
- Who may change it?
- Where is the approved version stored?
- How do you find out it changed?
- How do you roll it back?
Use named accounts on ground station software and cloud dashboards. Remove accounts when people leave. Keep a record of which pilot flew which aircraft, which also supports Part 107 supervision rules.
Keep an inventory of the software
Ground stations, companion computers and mobile apps all bring in open source libraries. Ask for a list of components for each tool you run, and check it against known vulnerabilities on a schedule. The interactive example below shows what a dependency inventory looks like.
Click through it at your own pace, or open it full screen.
Where Safeguard fits
Safeguard provides SBOM and dependency scanning, and you can try a free scan of a repository at gold.safeguard.sh/scan. For a fleet, that is most useful on the code you control: ground station tools, companion software and any scripts that touch flight data. It does not replace flight testing or a review of your autopilot configuration.
A monthly routine
- Check for firmware and app updates, and read the release notes.
- Re-run the dependency scan on tools you build.
- Review the list of accounts.
- Test one failsafe on the bench or in a field.
- Review the incident log, and confirm logs are being kept.
Quick check
Does MAVLink signing hide telemetry from eavesdroppers?
No. It adds a signature for authentication. The guide does not describe encryption.
Why save the parameter set in version control?
So you can see exactly what changed after a firmware update or a field edit, and roll back to an approved configuration.
Sources
- MAVLink guide, Message Signing: key handling and unsigned packet rules.
- PX4 User Guide, Safety configuration: failsafes, Remote ID arming check.
- 14 CFR Part 89, eCFR: Remote ID operating requirements.
Last reviewed: 19 October 2026.
