The present document contains a study on the security aspects of Uncrewed Aerial Systems (UASs). TS 22.125 contains the service requirements for UAS while TR 23.754 is studying aspects like the UAS connectivity, identification and tracking and TR 23.755 studies UAV services and application layer features. The security study of the present document provides key issue including security threat and potential requirements related to the work in these other specifications and develops and analyses solutions to these key issues. Finally the study provides some conclusions for potential normative work.

The following documents contain provisions which, through reference in this text, constitute provisions of the present document.

• References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.

The main objective of 3GPP systems is to facilitate non-3GPP entities UAS Service Supplier (USS) and/or UAS Traffic Management (UTM), which supply services to Civil Aviation Authority (CAA), and provide UAS Remote Identification (Remote ID) services. UAS Remote ID refers to a UAS in flight provides identification and tracking information that can be received by regulatory agencies. An Uncrewed Aerial System (UAS) is composed of an Uncrewed Aerial Vehicle (UAV) and a UAV controller (UAVC). TPAE is the Third Party Authorized Entity which can monitor UAVs, access and track UAV data, and make controls to UAVs. A UAV can be controlled by either a UAVC, TPAE, or UTM. Clause 4 of TS 23.754 provides some architectural assumptions and requirements and an overall reference architecture for the supporting UAS.