저사양 IoT 디바이스에 보안 기술 적용의 어려움을 해결하기 위해 oneM2M에서는 하드웨어 보안 모듈의 필요성을 제시하였다. 그러나 하드웨어 보안 모듈이 단독 동작하며, IoT 디바이스의 마이크로프로세서와 구분된 시스템은 또다른 보안 취약점이 될 수 있다. 본 논문에서는 통합 보안 SoC 기반의 IoT 디바이스 보안 플랫폼을 설계하여 oneM2M의 보안 요구 사항을 만족하는 요소 기술을 제안한다. 그리고 이를 통해 IoT 디바이스에 대한 보안 위협 대응을 검증한다.
Snow Chain-Integrated Tire for a Safe Drive on Winter Roads
[KCC oral] 정준영
1. - 1 -
Mobile & Embedded System Lab.
Dept. of Computer Engineering
Kyung Hee Univ.
Design of a IoT Device Security Platform
based on Integrated Security SoC
Presented by Junyoung Jung
2. - 2 - Kyung Hee University
Mobile Embedded System Lab.
Motivation (1/2)
Recent Trends
Accelerated the launch of a variety of IoT products & services
Developed the COTS IoT device platform
▶ Raspberry Pi, Arduino, ESP8266, etc
Problems
COTS IoT device platform
▶ Low CPU, Small memory, Low cost chip/sensor
▶ Absence of Security functions
Existing Security technology (for Server/PC)
▶ Demand Large Memory and Fast computing power
Difficult to apply Security functions
to IoT device platform
4. - 4 - Kyung Hee University
Mobile Embedded System Lab.
Related works (1/2)
Integrated Security SoC (eWBM MS500)
Security features
▶ Secure Key Management
Non Volatile Memory (eFuse)
▶ Secure Storage
Flash Memory
▶ Root of Trust
1st Bootloader
▶ Crypto Blocks
Symmetric Crypto Accelerator (AES, ARIA)
Asymmetric Crypto Accelerator (RSA, ECC)
True Random Number Generator
5. - 5 - Kyung Hee University
Mobile Embedded System Lab.
Related works (2/2)
oneM2M Security Requirements (TS-0003. Security Solutions)
Access Management
▶ Using the encryption functions of the SE for data integrity
▶ Using the encryption functions of the SE for authentication
Security Administration
▶ Pre-provisioning of sensitive data to SE
▶ Management of sensitive data via secure channel
Sensitive Data Handling
▶ Secure storage of sensitive data using SE
▶ Secure management of sensitive data using SE
6. - 6 - Kyung Hee University
Mobile Embedded System Lab.
Proposed System (1/6)
Security functions
① Secure Key Storage & Management
▶ Ensure availability of sensitive data(e.g., Encryption key)
▶ Correspondence) Sensitive Data Handling
② Secure Boot
▶ Verify firmware integrity
▶ Correspondence) Access Management
③ Secure Firmware Update
▶ Ensure safety of firmware update
▶ Correspondence) Access Management, Sensitive Data Handling
④ Secure Communication
▶ Ensure secure channel of device-to-device communication
▶ Correspondence) Security Administration
⑤ Remote Attestation
▶ Verify device trust
▶ Correspondence) Access Management, Security Administration
7. - 7 - Kyung Hee University
Mobile Embedded System Lab.
Proposed System (2/6)
Secure Key Storage & Management
MS500-iSE
BootROM
1 𝑠𝑡 𝐵𝐿
eFuse
𝑆ℎ𝑑𝐾 𝑃𝑙𝑎𝑡𝑓𝑜𝑟𝑚
𝑆ℎ𝑑𝐾 𝐷𝑒𝑣𝑖𝑐𝑒
TRNG
(True Random
Number
Generator)
ACA
(Asymmetric
Crypto
Accelerator)
SCA
(Symmetric
Crypto
Accelerator)
Flash Memory
Public Section
2 𝑛𝑑 𝐵𝐿
𝐹𝑊𝐶𝑢𝑟
Private Section
𝐼𝐷 𝐷𝑒𝑣𝑖𝑐𝑒 𝑃𝑢𝑏𝐾𝐴𝑢𝑡ℎ𝑜𝑟
𝑆𝑖𝑔𝑛(𝑃𝑟𝑖𝐾𝐴𝑢𝑡ℎ𝑜𝑟 , 𝐹𝑊𝐶𝑢𝑟) 𝐸(𝑆ℎ𝑑𝐾 𝐷𝑒𝑣𝑖𝑐𝑒 , 𝐹𝑊𝑉𝐶𝑢𝑟)
𝐸(𝑆ℎ𝑑𝐾 𝐷𝑒𝑣𝑖𝑐𝑒 , 𝑃𝑟𝑖𝐾𝐴𝑡𝑡𝑒𝑠𝑡) 𝐶𝑒𝑟𝑡𝑖𝑆𝐸
< Data Encrypt method >
8. - 8 - Kyung Hee University
Mobile Embedded System Lab.
Proposed System (3/6)
Secure Boot
< System Architecture >
< Sequence Diagram >
MS500-iSE
1 𝑠𝑡 𝐵𝐿 2 𝑛𝑑 𝐵𝐿 𝐹𝑊
Verify 2 𝑛𝑑
𝐵𝐿
( In: 2 𝑛𝑑
𝐵𝐿 𝑀𝐴𝐶, 𝑆ℎ𝑑𝐾 𝑃𝑙𝑎𝑡𝑓𝑜𝑟𝑚 )
Transfer control to 2 𝑛𝑑 𝐵𝐿
MS500-iSE
BootROM
eFuse
1 𝑠𝑡 𝐵𝐿 (includes 2 𝑛𝑑
𝐵𝐿 𝑀𝐴𝐶)
𝑆ℎ𝑑𝐾 𝐷𝑒𝑣𝑖𝑐𝑒
𝑆ℎ𝑑𝐾 𝑃𝑙𝑎𝑡𝑓𝑜𝑟𝑚
Flash
Private Section
𝐶𝑒𝑟𝑡𝑖𝑆𝐸
𝐸(𝑆ℎ𝑑𝐾 𝐷𝑒𝑣𝑖𝑐𝑒, 𝑃𝑟𝑖𝐾𝐴𝑡𝑡𝑒𝑠𝑡)
𝑆𝑖𝑔𝑛(𝑃𝑟𝑖𝐾𝐴𝑢𝑡ℎ𝑜𝑟 , 𝐻(𝐹𝑊𝐶𝑢𝑟))
𝐸(𝑆ℎ𝑑𝐾 𝐷𝑒𝑣𝑖𝑐𝑒, 𝐹𝑊𝑉𝐶𝑢𝑟)
𝑃𝑢𝑏𝐾𝐴𝑢𝑡ℎ𝑜𝑟
𝐼𝐷 𝐷𝑒𝑣𝑖𝑐𝑒
Public Section
𝐹𝑊
2 𝑛𝑑 𝐵𝐿
𝑃𝑢𝑏𝐾𝐴𝑡𝑡𝑒𝑠𝑡
𝑆𝑖𝑔𝑛 𝐶𝐴
Verify 𝐹𝑊
( Compare 𝐻(𝐹𝑊) and 𝐻(𝐹𝑊𝐶𝑢𝑟) )
Extract 𝑆𝑖𝑔𝑛(𝑃𝑟𝑖𝐾𝐴𝑢𝑡ℎ𝑜𝑟 , 𝐻(𝐹𝑊𝐶𝑢𝑟))
( referring to 𝑃𝑢𝑏𝐾𝐴𝑢𝑡ℎ𝑜𝑟 )
Transfer control to 𝐹𝑊𝐶𝑢𝑟
Compute 𝐻(𝐹𝑊)