This document discusses creating a secure Internet of Things (IoT) architecture. It recommends three rules for IoT security: don't be stupid, be smart, and think about what's different for IoT devices. It also notes unique challenges for IoT security like long device lifecycles and limited capabilities. The document advocates for using federated identity and access control to securely manage devices and data. It presents a reference architecture for IoT that incorporates real-time stream processing, analytics, identity management, and open source components.

1. A reference architecture for IoT:
How to create a resilient, secure IoT cloud
Paul Fremantle
CTO, WSO2 (paul@wso2.com)
PhD researcher, Portsmouth
University
(paul.fremantle@port.ac.uk)
@pzfreo #wso2

2. Firstly, does security even matter?

5. My three rules for IoT security
• 1. Don’t be stupid
• 2. Be smart
• 3. Think about what’s different

6. My three rules for IoT security
• 1. Don’t be stupid
– The basics of Internet security haven’t gone away
• 2. Be smart
– Use the best practice from the Internet
• 3. Think about what’s different
– What are the unique challenges of your device?

7. http://www.forbes.com/sites/kashmirhill/2013/07/26/smart-homes-hack/

8. So what is different about IoT?
• The longevity of the device
– Updates are harder (or impossible)
• The size of the device
– Capabilities are limited – especially around crypto
• The fact there is a device
– Usually no UI for entering userids and passwords
• The data
– Often highly personal
• The mindset
– Appliance manufacturers don’t think like security experts
– Embedded systems are often developed by grabbing existing
chips, designs, etc

9. Physical Hacks
A Practical Attack on the MIFARE Classic:
http://www.cs.ru.nl/~flaviog/publications/Attack.MIFARE.pdf
Karsten Nohl and Henryk Plotz. MIFARE, Little Security, Despite Obscurity

11. Or try this at home?
http://freo.me/1g15BiG

12. Hardware recommendations
• Don’t rely on obscurity

13. Hardware recommendations
• Don’t rely on obscurity
• Don’t rely on obscurity
• Don’t rely on obscurity
• Don’t rely on obscurity
• Don’t rely on obscurity
• Don’t rely on obscurity
• Don’t rely on obscurity

14. Hardware Recommendation #2
• Unlocking a single device should risk only that
device’s data

15. The Network

16. Direct network vs Gateway model

17. Crypto on small devices
• Practical Considerations and Implementation Experiences in Securing
Smart Object Networks
– http://tools.ietf.org/html/draft-aks-crypto-sensors-02

18. Key distribution

19. Ubertooth
http://ubertooth.sourceforge.net/
https://www.usenix.org/conference/woot13/
workshop-program/presentation/ryan

21. IDENTITY IS THE NEW PERIMETER

22. Passwords
• Passwords suck for humans
• They suck even more for devices

24. Why Federated Identity for IoT?
• Can enable a meaningful consent mechanism
for sharing of device data
• Giving a device a token to use on API calls
better than giving it a password
– Revokable
– Granular
• May be relevant for both
– Device to cloud
– Cloud to app

25. More information
http://pzf.fremantle.org/2013/11/using-oauth-
20-with-mqtt.html
http://siot-workshop.org/

27. Reference Architecture for the Internet of Things
http://freo.me/iotra

28. Re-active vs Realtime Pro-Active
Web Architecture
• Re-active
• 10k-100k connections
• Pull-based
• Human interactions
• Some APIs
• Creating Big Data
IoT Architecture
• Push-based
• 100k-1m connections
• No human interaction
• Autonomic
• API driven
• Creating even bigger
datasets

29. Real time stream processing
1 million events/s on 4 servers in Amazon EC2

30. 30
Analytics

31. Identity Management

32. Device Management
(Generally available Q1/2015)

33. APIs and API Management
eBay handles 6 billion messages a day through WSO2
That is 4 million a minute

34. *
Develop Once – Deploy Everywhere
Public WSO2
Cloud
Hybrid/Private
PaaS
Managed
Cloud
On AWS
On-Premise

35. DOESN’T EVERYONE SAY “JUST USE
MY OPEN PLATFORM”?

36. Really Actually Open
• 100% Open Source (no bait and switch!)
• Heterogenous
• Polyglot
• Interoperable
• Modular and based on OSGi
• Extensible
• API-driven
https://www.flickr.com/photos/jmarty/

37. Summary
• Think about security from the start
• Build a federated and secure model of Identity
for Things
• Create Autonomic models that deliver value
that surprises and delights customers
• Use Big Data Analytics and the Lambda
Architecture to understand your customers
• Be Open!