The Cost of OSCORE and EDHOC for Constrained Devices

We present the design of four firmware libraries for these protocols especially targeted for constrained microcontrollers and their detailed evaluation

Stefan Hristozov; Manuel Huber; Lei Xu; Jaro Fietz; Marco Liess; Georg Sigl


Scholarcy highlights

  • CoAP is a widely used IoT application layer protocol
  • Before we describe the design of μEDHOC-TEE in detail, we provide an analysis of the sensitive assets that need to be protected, and describe the consequences of potential attacks on them
  • In this paper we presented the design of μOSCORE and μEDHOC firmware libraries for constrained regular microcontrollers, which are based on the newest state of the OSCORE and EDHOC specifications and consider all modes of operation
  • We presented the design of μOSCORE-TEE and μEDHOC-TEE firmware libraries for microcontrollers featuring a TEE, which provide protection against attackers exploiting software vulnerabilities
  • This is achieved by separating the cryptographic keys and routines from the rest of the firmware, which may be vulnerable
  • In total μOSCORE-TEE requires 9,921 byte on a Cortex M33 CPU which is 3.13% more than μOSCORE which requires 9,611 byte
  • Our evaluation shows that when μOSCORE and μEDHOC are used together they require a total of ≈25 KB FLASH and between ≈1.8 KB and ≈4.2 KB RAM depending on the EDHOC mode
  • We show that a typical CoAP packet can be protected with OSCORE within a few milliseconds

Need more features? Save interactive summary cards to your Scholarcy Library.