element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • About Us
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
Internet of Things
  • Technologies
  • More
Internet of Things
Blog The Basics of IoT Embedded Device Security
  • Blog
  • Forum
  • Documents
  • Quiz
  • Events
  • Polls
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join Internet of Things to participate - click to join for free!
  • Share
  • More
  • Cancel
Group Actions
  • Group RSS
  • More
  • Cancel
Engagement
  • Author Author: rscasny
  • Date Created: 29 May 2016 10:11 PM Date Created
  • Views 877 views
  • Likes 3 likes
  • Comments 3 comments
  • iot_security
  • embedded security
Related
Recommended

The Basics of IoT Embedded Device Security

rscasny
rscasny
29 May 2016

At this week's Chicago IoT Meetup, Roman Budek of NXP gave a talk on understanding and implementing embedded system security. What follows are the high points of the talk:

 

1. What makes IoT security unique? The IoT will consists of billions of connected, embedded devices. The more embedded devices connected to a gateway, the greater the security risk..

 

2. Why is it important to secure all end nodes? If a connected thermostat for a commercial freezer in a restaurant was hacked, the result could be food spoiling. If a connected treadmill was hacked, the hacker could cause the treadmill to accelerate unpredictably and possibly causing the user to fall. More than anything else, a hacked embedded device can damage a company’s brand. Hackers know what devices are vulnerable because the vulnerabilities are published on websites such as Shogan.tech.

 

3. Since many IoT embedded devices are in the field, upgrades pose a risk because reflashing the firmware can be done by an unauthorized source.

 

4. You can design the most secure gateway in existence but if your customer connects to a hotspot, for example, that is infected, you are at risk.

 

5. There are many types of embedded device security risks. They include:

  • Remote attacks on a cloud service provider
  • Physical attacks (e.g., using side channel) on peripheral systems (e.g. door lock)
  • Vulnerable or compromised device from unknown origin that compromises home network from the inside
  • Remote attacks on home devices (gateway or IP edge nodes) from cloud
  • Attack from an infected Smart phones/watches (rogue App. Pin code phishing, etc.)
  • Decommissioned devices used as Trojan horse to compromise other networked devices

 

6.While open source dev boards like Arduino make it easy for development, it also means that hackers know their vulnerabilities.

 

7. The 6 tenets of IoT security are:

  • Identity/Authentication
  • Authorization
  • Audit
  • Confidentiality
  • Integrity
  • Availability

 

 

8. The goals of embedded security include:

  • Data Integrity: to prevent data snooping and detect data alterations
  • Code Integrity: prevent code theft; detect code alterations; allowing authorized code changes only
  • Device integrity: protecting cryptographic keys and prevent product counterfeits

 

9. The Basics of Cryptographic Algorithms

  • Objective-- scramble data so that only select entities can decipher it
  • Can be implemented in software or hardware
  • Hardware implementations can save performance & power

 

image

Source: NXP

 

10. There are two basic types of cryptography algorithms:

 

A) Symmetric – same key can encrypt & decrypt

  • DES, 3DES, Blowfish, AES are symmetric cryptographic algorithms
  • AES is the most popular due to its strength – no published reports of successful hack
  • 128-, 192- & 256-bits are frequently-used key lengths for AES algorithm
  • Pros: Faster than asymmetric cryptography
  • Cons: Difficult to distribute & protect the shared secret key securely

 

B) Asymmetric – different key required for reverse operation

  • Public & Private Key pair per system
  • Only the Private key is kept secret
  • Keys operate “one-way”
  • Public key encrypts -> Private key decrypts
  • Private key encrypts -> Public key decrypts
  • Commonly used algorithms: RSA & ECC
  • Keys can be up to 2048-bits or longer
  • Pros- Easy to manage, scalable
  • Cons - Slower than symmetric cryptography

 

11. Why is Data Integrity Important?

 

A) Unencrypted messages

  • Hackers can snoop messages
  • Hackers can substitute, replay or monitor messages & create havoc

 

B) Encrypted messages

  • Message cannot be read without key
  • Cons: Enabling encryption reduces payload size
  • Cons: Takes time to decrypt the message before it can be used

 

12. Data Security- Components and Solutions

image

Source: NXP

 

13. Code Integrity - Components and Solutions

 

image

Source: NXP

 

14. Device Integrity - Components and Solutions

 

image

Source: NXP

 

15. Protection Embedded Systems

 

image

 

16. What Security Problem Does My System Have?:

 

image

Source: NXP

  • Sign in to reply

Top Comments

  • clem57
    clem57 over 9 years ago +1
    Just a point here: usually a string is encoded with a symmetric key which in turn is encrypted with a public-private key asymmetrically which would be a hybrid system. Clem
  • Former Member
    Former Member over 9 years ago +1
    Agree with clem57 that we typically use the public/private key pair for periodic key exchange of a symmetric working key set; the payload data is subsequently protected with the working key. Using a public…
  • DAB
    DAB over 9 years ago

    Nice overview of the issues around IOT security.

     

    I look at it as an issue where you feel that the raw data is important enough to protect and making your analysis software robust enough to identify when a sensor has been compromised.

    You also have the issue of cost to effect.  Hackers will go after the big payoff devices, but will probably ignore the run of the mill implementation.

    It's an issue of what do you get for your effort.  So you can cause a house to over heat, so what, it annoys people, but what did it get YOU?

     

    So I understand the encryption angle for sensitive applications, but there will be a lot of IOT that is just not worth hacking.

     

    DAB

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • Former Member
    Former Member over 9 years ago

    Agree with clem57 that we typically use the public/private key pair for periodic key exchange of a symmetric working key set; the payload data is subsequently protected with the working key.  Using a public/private key for an extensive conversation between two end points is too slow and resource-hungry.

     

    Regarding #11, B) Encrypted messages:

     

    "Cons: Enabling encryption reduces payload size"

    This is not necessarily true.  Assuming that a symmetric key-set was used for encryption, it might cause an increased message size to hold the encrypted payload compared to a clear-text equivalent.  Perhaps this just needs a bit more explanation.

     

    "Cons: Takes time to decrypt the message before it can be used"

    It takes time and resources on both sides (transmitter and receiver) to process data cryptographically.

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • clem57
    clem57 over 9 years ago

    Just a point here: usually a string is encoded with a symmetric key which in turn is encrypted with a public-private key asymmetrically which would be a hybrid system.

    Clem

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • More
    • Cancel
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2025 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube