Secure Drone Identification with  - PowerPoint Presentation

1. Secure Drone Identification with Hyperledger IrohaAndrei GurtovYousef HashemElmedin Zildzic

2. Introduction2

3. Drone Remote Identification Protocol (DRIP)Newly proposed protocol to incorporate authentication and trust mechanisms into drone communicationsDRIP Requirements submitted to IESG for publicationDRIP RID & authentication standards proposed (IETF WG)3

4. Yet to be determined DRIP solutions4

5. DRIP Registry Requirements5

6. Main contributionsNovel drone ID architecture based on Hyperledger Iroha and DRIPInformal security analysis of the proposed architecturePerformance evaluation6

7. Architecture7

8. DRIP Registry interactionObservers receive Direct RID messages, and performs lookups on registryUAs and GCSs send location updates to registryAdmin registers new accounts (drone/operators)UAs do not participate in the blockchain8

9. DRIP Registry ImplementationOpenHIP hipv2_new_crypto branchModified (by us) to support DRIP HIT Suite (EDDSA/cSHAKE) Include Hierarcial ID (HID) in HIT = HHITGenerate HHITsOur own scripts to generate DRIP public keys and certificatesdraft-ietf-drip-reqs-17draft-ietf-drip-rid-089

10. DRIP Registry ImplementationDRIP Bluetooth Advertisements ASTM F3411-19 and DRIP formatWorks with OpenDroneIDWeb app to track drones via blockchain registry (Network RID)Android app to track and verify HHITs and auth messages (Registry lookup)10

11. Hyperledger Iroha11

12. Hyperledger Iroha AccountsAccounts can be created on multiple domains to separate PII from public data One private domain One public domainAny data set on the accounts is non-repudiable, however, values can still be modifiedOne account cannot overwrite data set by another accountAny account that has set some data will be visible12

13. Security analysis13

14. Hyperledger Iroha14

15. Hyperledger IrohaSupports multisignature transactionsSupports smart contracts w/ Hyperledger Burrow15

16. Multisignature transactionsRequiring multiple signatures for a single transaction can prevent single point-of-failures, such as when admin accounts are compromised.Make false data dissemination attacks harder – e.g. need to compromise both GCS and drone.16

17. Smart contractsMake queries behave like transactionsQueries are stored on the blockchainAuditability – Who has requested what information (REG-4)Traceability17

18. Performance evaluation18

19. Methodology16 and 30 Amazon EC2 instances used as Iroha nodes Launched with Docker SwarmPer instance (free): 2 vCPU Intel Scalable Processor @ 2.5 GHz with 6 CPU credits/hour 1 GB RAM  8GB EBS Storage Up to 5 Gbps network speed Region: eu-north-119

20. Methodology100 and 200 simulated drones launched, sending a location update transaction each secondSimulated drones launched as workers with LocustWorkers randomly selected a node to send transactions to (load balancing)Workers launched on home networks, sending transactions to Iroha nodes through Internet10-15 ms RTT (ping) 20

21. MethodologyLocation updates used non-standard formatLatitudeLongitudeAltitudeDirectionSpeedTimestampStatus123 bytes payloadCan be shortened by using standardized format (e.g. ASTM F3411-19, ~24 bytes)Minimize blockchain storage requirements21

22. MethodologyIroha performance parameters configurableLower delays can yield better performance, but also introduce higher network loads (more vote messages exchanged between peers)22

23. Transaction response times(=one-way trip time + block consensus delay)23

24. Average block sizes24

25. Conclusion25

26. ConclusionHyperledger Iroha can fulfill all DRIP registry requirements and has decent performanceFrequent location updates places big requirement on storageMight still be worthwhile to store on blockchain for "black box" purposes.Less frequent location updates to lessen storage requirements26