300 likes | 363 Views
Join Charles J. Lord for a comprehensive course on IoT network security, covering commissioning, authentication, channel security, and more. Explore various methods of commissioning IoT nodes, from manual configuration to NFC or Bluetooth setups, as well as decommissioning strategies. Discover the importance of device and network authentication in protecting IoT systems and delve into channel security mechanisms such as IPsec, SSL, and SSH. Gain insights into different tunneling and encapsulation techniques to safeguard data packets and ensure secure communication between devices. Learn about the latest advancements in IoT security and how to implement best practices to counter potential threats. Don't miss this opportunity to enhance your knowledge and skills in IoT network security.
E N D
The Principles of IoT Security A Hands-on Course Class 4 : Network Security February 2, 2017 Charles J. Lord, PEPresident, Consultant, TrainerBlue Ridge Advanced Design and Automation
This Week’s Agenda 1/30 Intro to IoT Security1/31 Hardware Security Challenges 2/1 Data Security 2/2 Network Security 2/3Other Security Issues in the IoT
This Week’s Agenda 1/30 Intro to IoT Security1/31 Hardware Security Challenges 2/1 Data Security 2/2 Network Security 2/3Other Security Issues in the IoT
IoT Network Security • Commissioning and decommissioning • Device Authentication • Network Authentication • Channel Security • IPsec • SSL, SSH • WEP / WPA • Others
Commissioning • Depending on the protocol used, commissioning can be one of the ‘big challenges’ of IoT nodes • Many approaches • Manual configuration • Hardwired • NFC or BT commissioning • Wired (typically USB)
Manual configuration • Network ID set by dip switches or pin jumpers • X-10 • Garage Door Openers • Expensive to make • Failure prone • Mechanical failure / contamination • User failure Question 1 - Other devices that used dip switches for configuration?
Hardwired • Cheapest to make – device has a hardwired ID • Typically based on the MAC address • Gateway or local network controller must be programmed to accept this new ID in network • Easy to clone, particularly in 802.11x • WIFI access point example
NFC or BT commissioning • “ease of use” • There’s an app for that • Great way to sell NFC hardware • BT has to be distance sensitive • Can be easy to clone, depending on security of commissioning app
Wired • Plugs into PC (or tablet with correct cable) • Can use sophisticated authentication (or not) • Requires USB port • Drivers can be an issue • A lot of PC / MAC / Linux / iOS / Android to maintain • USB ports are notorious dirt magnets
Decommissioning • Network alarms on device disappearance • In mesh networks – what if device was a router? • How does the absence affect the network? • Alarm sensor • Temp sensor for thermostat • Medical sensor • How to remove network memory from device
Device Authentication • ACL (access control list) – ‘login’ • Network ID • Known to network? • Multi-level authentication • ACL plus a challenge key • Fixed vs dynamic network configuration • Must guard against cloning or spoofing Question 2 – Other ways a device may authenticate?
Network Authentication • “Am I in the right place?” • Anti-spoofing or anti-phishing • PKI certificate authority • RSA • Reverse ACL
Channel Security How do we protect our data packets? • IPsec • SSL • SSH • TLS • DTLS • Tunneling / Encapsulation
IPsec • Internet Protocol Security • Operates at the Network layer (#3) • Authenticates and encrypts each IP packet • Establishes mutual authentication between agents at the beginning of the session • Negotiates cryptographic keys to be used during the session.
More on IPsec • Crypto includes: • Hashing, including SHA-1 and SHA-2 • AES-CBC • AES-GCM • 3DES • Typically works in “Transport Mode” • Payload is encrypted • Routing is not encrypted, but Authentication Header keeps from being mis-routed (e.g. port change)
SSL • Secure Sockets Layer • Works at the Session Layer (#5) • Establishes a secure link between two points in a network • Public Key Certificates • Incorporated in and replaced by TLS
SSH • Secure Shell • Works at the Application Layer • Origin in BSD Unix • Encrypts application – level data throughout all layers from point to point • Often used for login to remote systems • Typically uses TCP port 22
TLS • Replacement of SSL • Covers both transport and session layers • Current version 1.2 (RFC 5246) • Supports many public key standards from basic AES through 3DES and many ellipticals • Supports both block cipher and stream cipher • Works with TCP
DTLS • Datagram Transport Level Security • Can cover from transport to application levels • Derived from TLS streaming mode • Supports UDP packets • Less overhead than TLS while providing protection for the payload (datagram) • Popular in IoT with CoAP Question 3 – CoAP stands for? And does what?
Tunneling / Encapsulation • Can be part of IPsec • Both payload and routing headers are encrypted and are the new payload • Can support one protocol over another (IPv6 over IPv4, IPv6 over PAN, etc) • Basic mechanism for VPNs
What to Use? • Again, the security level will dictate, as well as the topology and exposure to attack or eavesdropping • Does the discovery of who is talking to whom matter? • How secure does the data have to be? • What algorithms are • Available as either software or hardwired • Within the processor’s abilities? • Tomorrow – we sum it all up!
This Week’s Agenda 1/30 Intro to IoT Security1/31 Hardware Security Challenges 2/1 Data Security 2/2 Network Security 2/3Other Security Issues in the IoT
Please stick around as I answer your questions! • Please give me a moment to scroll back through the chat window to find your questions • I will stay on chat as long as it takes to answer! • I am available to answer simple questions or to consult (or offer in-house training for your company)c.j.lord@ieee.orghttp://www.blueridgetechnc.comhttp://www.linkedin.com/in/charleslordTwitter: @charleslordhttps://www.github.com/bradatraining