C-UAS is a system-of-systems problem
Detection, identification, classification, tracking and mitigation are different functions with different failure modes. A valid track does not establish hostile intent or authority to act.
BIT examines the sensor–decision–authority–action chain and the interfaces where latency, conflict or incorrect assumptions can propagate.
Legal authority is an operational dependency
Detection and mitigation may engage aviation, communications, privacy, security and criminal-law constraints. Authority varies by country, site, operator, technology and threat condition.
An assurance layer cannot create authority. It can be designed to verify whether required authority and policy conditions are present before a controlled action proceeds.
Test realistic uncertainty and failure
Relevant scenarios include clutter, false alarms, multiple objects, sensor disagreement, track handover, RF congestion, communications loss, unavailable effectors, localization conflict and authority revocation.
Pass criteria should cover timing, human interaction, unintended effects and behaviour when confidence falls below defined thresholds.
Control the response, not only the alert
Where action depends on verified location or airspace state, the separate Localization Trust States TRUSTED, DEGRADED, CONFLICTED and UNTRUSTED can inform the authority decision.
Reconstruct the complete event
Evidence should show which sensors contributed, how tracks changed, which policy and authority applied, what the operator or system decided and what action followed.
BIT is developing evidence intended for TEVV, incident review, procurement evaluation and accountable oversight.
Frequently asked questions
Does BIT provide a stand-alone jammer or effector?
No claim is made here to provide a stand-alone detector, jammer or effector. BIT focuses on the assurance and TEVV layer around the selected system.
Can C-UAS assurance be used at airports or events?
Potentially, but only within applicable law, aviation-safety requirements, authorized operator roles, threat model and site conditions.
Can detection be tested separately?
Yes. A complete operational assessment must also examine how detection information influences decisions and authorized responses.
Can TEVV guarantee every drone is detected?
No. TEVV can establish evidence for defined scenarios and limits, not universal performance.
Sources and technical basis
- FAA — UAS Detection, Mitigation and Response at Airports — Reference inclusion establishes technical context only; it does not claim conformity, approval or certification.
- U.S. DHS Counter-UAS Technology Guide
- DoD Strategy for Countering Unmanned Systems
- DoD Directive 3000.09 — Autonomy in Weapon Systems
Test the entire C-UAS decision chain.
Define a lawful, mission-based TEVV plan covering sensors, decisions, authority, degraded conditions, response controls and evidence.
Request C-UAS test briefUnclassified · scoped workshops and pilot design