Counter-drone is not a security programme.

Buying a detection system does not secure the aircraft you build. An argument, briefly.

Counter-UAS answers a real question: what do we do about someone else’s drone over our facility. It is not an answer to the question a manufacturer faces, which is whether their own aircraft can be taken from them.

These get conflated in procurement constantly, and the conflation is expensive. A detection system on the perimeter does nothing about a debug header on the flight controller or an unsigned firmware path.

If you build drones, your security programme starts at the board and ends at the fleet portal. Counter-drone is somebody else’s programme, and it is fine to say so.