Drone Threat Intel Report: DroneSec Notify #4

This summary has been extracted from our weekly public threat intelligence report. For more information on the platform or weekly email PDFs, please visit: or email us at [email protected] or join the slack group at

See how the DroneSec Notify Threat Intelligence Platform can benefit your organisation.

Welcome to a new decade! It really amuses me that we’ve reached the year 2020 – it’s the year many reports from 2017 onwards referenced as markers for the drone security market reaching X amount in estimated value or worth. We’re now finally here and while some expectations have stayed true, we’re dealing with a very interesting environment in the context of Cyber Physical Systems.

Through the holiday period our team focused on aligning our core Threat Intelligence (TI) model to current Information Security and Open-Source Intelligence standards. This was a combination of our roadmap on what we want to achieve, aligning ourselves with our defence and law enforcement customers ingesting this information, and of course, readers’ feedback.

Our traditional consulting services model links back to the NIST, OWASP and MITRE ATT&CK  frameworks – structuring these around drone security has been a core mission of DroneSec. This is something that we will publish when we feel is ready and truly tested enough on real-world scenarios. With Threat Intelligence however, we wanted to ensure we were sourcing data that would help model scenarios and countermeasures for Red and Blue teams in their respective organisations.

For this reason, our research has focused on two well-recognised and respected; CBEST Threat Intelligence Framework produced by the Bank of England Sector Cyber Team and TIBER-EU produced by the European Central Bank. Of course, it’s a challenge interpreting any traditional framework into a new area such as drone security which merges aviation with electronics and computer systems, but one we hope will help shape both defensive and offensive drone operations for organisations. In the coming weeks, we’ll continue to tweak our TI process and detail these changes in the Methodology section in the Appendix of this document.

Over the Christmas holidays, I came across two documents I hadn’t found in our knowledge base before. One was the FAA’s May 2019 guidance to airports on the deployment and use of UAS detection systems. The other was on the American Association of Airport Executives’ recommendations to the FAA on mitigating safety and security risks posed by UAS in airport environments. While they were released some time ago, they both had a number of considerations and statements I found really interesting that haven’t been apparent in many pre-CUAS discussions. Both documents can be found in one of the links below**.

Amusingly, we kick this year off with a number of GoPro drones grounded due to software updates failing to be pushed through for GPS-based internal clocks. Let’s hope UTM systems keep this all ticking automatically in the future so that we don’t face a Y2K-style mid-air shock next decade! To all our DroneSec Notify subscribers, thanks for being a part of the journey and all the best for your safe and secure drone operations in 2020.


Leave a reply