flowfence iot security
play

FlowFence: IoT security Mikal Fourrier Internet of Things - PowerPoint PPT Presentation

FlowFence: IoT security Mikal Fourrier Internet of Things Interconnection of numerous devices which interacts and exchange data Examples: smart home, smart grid Vague term, like the Cloud 2 Study: Samsung SmartThings


  1. FlowFence: IoT security Mikaël Fourrier

  2. Internet of Things ● Interconnection of numerous devices which interacts and exchange data ● Examples: smart home, smart grid ● Vague term, like the Cloud 2

  3. Study: Samsung SmartThings ● Subscribe: abstraction of the hardware ● Polling ● Access control with a device-level granularity 3

  4. Study: Google Fit ● Wearables-oriented ● Only callbacks ● Access control with scopes – Ex: FITNESS_BODY_READ 4

  5. Study: Android Sensor API ● Events: Motion, Environment, Position ● Callback-based except for Position ● No access control except for Position and heart rate 5

  6. Study: IoT architecture ● Hub ● Cloud 6

  7. Problems with IoT ● Lots of devices → hard to secure ● Very sensitive data: health, home locking, cameras ● Third-party applications have few restrictions: a face-recognition door unlocker can send images to the network 7

  8. FlowFence: basic ideas ● Normal execution environment vs sandbox (Quarantined Modules) ● Use of opaque handles ● Enforce declared data use patterns ● Sandbox treated as a black box 8

  9. API example 9

  10. Publisher examples 10

  11. Taint arithmetic 11

  12. Architecture 12

  13. Sandboxes ● Android process with the “isolatedProcess” flag – Disable all rights except IPC for FlowFence ● Cleaned after QM execution 13

  14. Key-value store ● key → (sensible value, taint) ● Polling easy to implement ● Event channels for callbacks ● Device agnostic 14

  15. Overhead ● 3M/sandbox – reasonable ● 100ms if spare sandboxes – same as network call ● 30M/s bandwidth – the Nest camera uses 1M/s, so should be sufficient 15

  16. Ported applications 16

  17. Weaknesses ● QM could forge keys to leak data – Keys must already exist in the QM ● QM can control it's execution time – Asynchronous execution in future version ● Can't prevent user to approve all ● Over-tainting – Taint bound 17

Download Presentation
Download Policy: The content available on the website is offered to you 'AS IS' for your personal information and use only. It cannot be commercialized, licensed, or distributed on other websites without prior consent from the author. To download a presentation, simply click this link. If you encounter any difficulties during the download process, it's possible that the publisher has removed the file from their server.

Recommend


More recommend