Yves Goeleven
#IoT: Privacy and security considerations
Thanks to
Yves Goeleven
• Founder of MessageHandler.net
– Shipping software since 2001
– Windows Azure MVP
– Developer on NServiceBus
2
Exhibition theater @ kinepolis
Agenda
• Why this talk?
• What are the dangers?
• Security options
• Privacy options
4
Agenda
Why this talk?
5
6
7
You might just leave this session
with more questions than answers
Talk!
Let’s start a conversation!
11
Challenge!
I challenge anyone to do a follow up session
with your own questions and ideas.
12
Agenda
What are the dangers?
13
14
Internet of Things
15
What are the dangers?
Personal
17
& invisible
White lies are the
common decency
holding us together
20
Agenda
What can we do?
22
Security options
• Prevent physical access
– Behind locked doors
– Secure casing
– Do not expose physical ports (usb, ethernet, ...)
24
Security options
• Prevent virtual access
– Do not open inbound ports
– Design without ’listeners’ or ‘servers’ on the devices
– Instead use ‘workers’ or ‘agents’ and remote queues
with outbound connections only
25
26
Security options
• Prevent physical tampering
– Seals, markers
– Alarms
– Camera’s
27
Security options
• Prevent virtual tampering
– Bootloader in chip or ROM, checks firmware origin
before loading into RAM
– Note: Updating (incl. security fixes) now just got a lot
harder though
28
Security options
• Keep track of device identity
– Let devices register themselves/call home
– Do this on boot & periodically
30
Security options
• Analyze device behavior
– Include device specific & variable information
– Analyze it server side to detect hacked or spoofed
devices
31
Security options
• Block compromised devices
– Access control lists
– Protocol/package filtering
– Signal Jamming
– Unplug the power
– On the device, or a specialized device
32
Security options
• Many low-power devices cannot encrypt data
using standard encryption techniques
– Not enough memory
– Drains battery too fast
34
Security options
• Do not store unencrypted data
– On publicly accessible devices
– Better send it elsewhere, unencrypted if needed, to
store it safely
35
Security options
• Do not send unencrypted data over long
distances
– Use a local ‘gateway’, a powerfull local device to
encrypt it on behalf of dumb devices
36
Security options
• Use alternative encryption & data mangling
strategies
– Signed at the foundry, if you can live with lock-in
– Ciphers, hashes & arithmetic algorithms
37
Security options
• Audit your physical environment
– Know which devices are ‘smart’
– And how they communicate
– Include all technologies (IR, RF, Bluetooth)
39
Security options
• Spy on your things
– Intercept communication between your ‘things’
– Analyze the communication & detect anomalies
40
Security options
• Physical canary
– Apply ‘social control’ amongst devices
– Let devices report that other devices are talking to
them inappropriately
41
Internet of things, reference architecture
42
Privacy options
• There are privacy laws
– Make sure not to break these!
– Do not store, send or process information that you’re
not allowed to
– http://en.wikipedia.org/wiki/Data_Protection_Directiv
e
44
Privacy options
• Is it clear what laws apply when?
– Multinationals spread across different countries
– Difference in laws where data is collected vs data is
processed or stored
– US vs EU: direct conflict
45
Privacy options
• Trust is paramount for adoption of IoT
– Make it your policy not to break it
– People may choose not to buy products from
violators
48
Privacy options
• Question is: is this really true?
– Facebook is huge, yet no one trusts them (I hope)
– Will convenience win over privacy concerns for
majority of people?
49
Privacy options
• Build trust by asking for user consent
– On data collection devices
– Oauth great for this!?
– But how about devices without a screen?
50
Privacy options
• And how about exchanging and correlating
information with 3rd parties in backend?
– Need for federated authorization?
– With context?
– F.e. I allow you to analyse my energy consumption,
send the results to government, but not to utility?
52
55
Loyalty plan
Give me your address and
you'll get 10% off on your
next pair of jeans…
Other things we can do?
There’s a lot we can do
56
Other things we can do?
Also a lot of open questions
57
Other things we can do?
But maybe consumers just don’t care
(aren’t prepared to pay for it?)
58
Other things we can do?
What do you think?
59
60
A big thank you to our sponsors
Gold Partners
Silver & Track Partners
Platinum Partners

Io t privacy and security considerations

  • 1.
    Yves Goeleven #IoT: Privacyand security considerations Thanks to
  • 2.
    Yves Goeleven • Founderof MessageHandler.net – Shipping software since 2001 – Windows Azure MVP – Developer on NServiceBus 2
  • 3.
  • 4.
    Agenda • Why thistalk? • What are the dangers? • Security options • Privacy options 4
  • 5.
  • 6.
  • 7.
  • 10.
    You might justleave this session with more questions than answers
  • 11.
    Talk! Let’s start aconversation! 11
  • 12.
    Challenge! I challenge anyoneto do a follow up session with your own questions and ideas. 12
  • 13.
  • 14.
  • 15.
  • 17.
    What are thedangers? Personal 17
  • 18.
  • 20.
    White lies arethe common decency holding us together 20
  • 22.
  • 24.
    Security options • Preventphysical access – Behind locked doors – Secure casing – Do not expose physical ports (usb, ethernet, ...) 24
  • 25.
    Security options • Preventvirtual access – Do not open inbound ports – Design without ’listeners’ or ‘servers’ on the devices – Instead use ‘workers’ or ‘agents’ and remote queues with outbound connections only 25
  • 26.
  • 27.
    Security options • Preventphysical tampering – Seals, markers – Alarms – Camera’s 27
  • 28.
    Security options • Preventvirtual tampering – Bootloader in chip or ROM, checks firmware origin before loading into RAM – Note: Updating (incl. security fixes) now just got a lot harder though 28
  • 30.
    Security options • Keeptrack of device identity – Let devices register themselves/call home – Do this on boot & periodically 30
  • 31.
    Security options • Analyzedevice behavior – Include device specific & variable information – Analyze it server side to detect hacked or spoofed devices 31
  • 32.
    Security options • Blockcompromised devices – Access control lists – Protocol/package filtering – Signal Jamming – Unplug the power – On the device, or a specialized device 32
  • 34.
    Security options • Manylow-power devices cannot encrypt data using standard encryption techniques – Not enough memory – Drains battery too fast 34
  • 35.
    Security options • Donot store unencrypted data – On publicly accessible devices – Better send it elsewhere, unencrypted if needed, to store it safely 35
  • 36.
    Security options • Donot send unencrypted data over long distances – Use a local ‘gateway’, a powerfull local device to encrypt it on behalf of dumb devices 36
  • 37.
    Security options • Usealternative encryption & data mangling strategies – Signed at the foundry, if you can live with lock-in – Ciphers, hashes & arithmetic algorithms 37
  • 39.
    Security options • Audityour physical environment – Know which devices are ‘smart’ – And how they communicate – Include all technologies (IR, RF, Bluetooth) 39
  • 40.
    Security options • Spyon your things – Intercept communication between your ‘things’ – Analyze the communication & detect anomalies 40
  • 41.
    Security options • Physicalcanary – Apply ‘social control’ amongst devices – Let devices report that other devices are talking to them inappropriately 41
  • 42.
    Internet of things,reference architecture 42
  • 44.
    Privacy options • Thereare privacy laws – Make sure not to break these! – Do not store, send or process information that you’re not allowed to – http://en.wikipedia.org/wiki/Data_Protection_Directiv e 44
  • 45.
    Privacy options • Isit clear what laws apply when? – Multinationals spread across different countries – Difference in laws where data is collected vs data is processed or stored – US vs EU: direct conflict 45
  • 48.
    Privacy options • Trustis paramount for adoption of IoT – Make it your policy not to break it – People may choose not to buy products from violators 48
  • 49.
    Privacy options • Questionis: is this really true? – Facebook is huge, yet no one trusts them (I hope) – Will convenience win over privacy concerns for majority of people? 49
  • 50.
    Privacy options • Buildtrust by asking for user consent – On data collection devices – Oauth great for this!? – But how about devices without a screen? 50
  • 52.
    Privacy options • Andhow about exchanging and correlating information with 3rd parties in backend? – Need for federated authorization? – With context? – F.e. I allow you to analyse my energy consumption, send the results to government, but not to utility? 52
  • 55.
    55 Loyalty plan Give meyour address and you'll get 10% off on your next pair of jeans…
  • 56.
    Other things wecan do? There’s a lot we can do 56
  • 57.
    Other things wecan do? Also a lot of open questions 57
  • 58.
    Other things wecan do? But maybe consumers just don’t care (aren’t prepared to pay for it?) 58
  • 59.
    Other things wecan do? What do you think? 59
  • 60.
    60 A big thankyou to our sponsors Gold Partners Silver & Track Partners Platinum Partners

Editor's Notes

  • #8 Real time message processing as a service Think of it as IFTTT for internet of things Solves today’s integration issues Scalability, data volume, multitude protocols & platforms, multitude of integration points, saas & social integration, mobile platforms, business ecosystems, ownership & centralized management, …
  • #9 Real and present dangers Are a threat to IOT Are caused by IOT
  • #10 Investigation and understanding is required
  • #20 Can third parties (ab)use this information? ‘Personally wellbeing’: Doctors, physicians, … ‘Social purposes’: Government, police, judges, … ‘Commercial purposes’: Insurance, lawyers, markting… ‘Pure evil’: Identity theft, extortion, …
  • #21 What about the small things in life? Occasional white lie <> activity/location tracking Socially unacceptable (yet totally normal) behaviour <> Sensors
  • #27 Prevent physical tampering Seals, marks Alarms, camera’s Prevent virtual tampering Bootloader in chip or ROM Checks firmware origin before loading into RAM Updating (incl. security fixes) now just got a lot harder though
  • #55 All this comes at a cost, both in time and money. And not just on the producer side Is it worth it, do people care enough? Or will convenience be more important than privacy?