RotorLabThe question is already on procurement questionnaires, insurance renewals and agency contracts — and until recently there was no way to answer it that anyone could check. There is now a published, open standard for drone security configuration. RotorLab measures the flight logs you are already storing against it, and hands you the evidence.
The UAS Security Verification Standard is open, vendor-neutral and free to read. Every requirement carries a permanent identifier, an assurance level and a published rule. Which means the result you hand to a client is not a vendor’s say-so: anyone holding the same flight log and the same version of the standard can run it themselves and get the same answer.
1 red and 7 amber failures are open. 24 requirements could not be decided from a log, and none of those count as passes.
It reads the logs already in your account. Nothing to install, nothing to upload twice.
A disabled failsafe, a geofence switched off, pre-arm checks weakened from default, firmware carrying a published vulnerability with a named fixed release. Each one names the parameter it was decided on and the setting to change.
Two aircraft that left the shop identical, answering the same requirement differently. The fleet view gathers open failures by requirement — one requirement failing on four airframes is one job, not four findings buried in a grid.
A dated document naming every aircraft, what was checked, what was accepted with a reason, and how much of the standard was never assessed. The thing a procurement officer asks for.
Plenty of requirements cannot be decided from a flight log at all — some need a person, some need live state from your ground infrastructure. A tool that quietly counted those as passing would produce a much better-looking result and a worthless one. Every screen and every report states both figures: what was decided, and what was not.
| The verdict | What it means |
|---|---|
| Pass | Decided from the log, against a published rule. |
| Fail | Decided, and it cites the value it was decided on. |
| Accepted | Failing, carried deliberately, with a person and a reason. |
| Not applicable | You attested the condition it depends on does not apply. |
| Not assessed | Needs a person, or live ground-station state. Never a pass. |
| Not assessable | The log did not carry what the rule needed. |
The Security Analyzer is an add-on on any plan, and included on Studio and above. Assess a log on its own, or every stored log in the account.
Conformance under UASVS is self-attested. RotorLab reports the evidence behind what you claim — it does not certify your operation, and no result here is an approval from any authority.