How to design security into your connected product

0 Comments

We often talk about designing security into a product from the get go, but we don’t often discuss what that means. In today’s podcast John Kestner, a principle with Supermechanical, the company behind the Twine sensor and the Range thermometer, shares his thoughts on how he designed Twine and range to be more secure but also how we might design our devices to indicate that what was once a humble lock is now a connected computer with all the pros and cons that entails.

Before Kestner and I dig into security, Kevin Tofel and I talk about my experience playing with the Logitech Harmony Ultimate Remote and home hub and then we dig into CSRMesh and the Bluetooth SIG’s creation of a working group to add mesh networking to the Bluetooth Smart standard. That could put Bluetooth in closer competition with thread, Zigbee and Z-wave. So kick back and listen up.

Hosts: Stacey Higginbotham and Kevin Tofel
Guests: John Kestner, principal with Supermechanical

  • Thoughts on the Logitech Harmony Hub and remote (it’s pretty nifty, guys)
  • The Bluetooth SIG is forming a working group on mesh technologies. Why this is cool!
  • Should you rely on security by obscurity or hope your device doesn’t do much that’s scary as a way to be secure?
  • Thinking about how to convey connectedness in design

 

Internet of Things Show RSS Feed

Subscribe to this show in iTunes

Download This Episode

PREVIOUS IoT PODCASTS:

Insurers may subsidize your smart home, but which device?

Let’s learn about blockname, a decentralized version of DNS

Connected apartments may be smarter than connected homes

This week’s podcast unravels the secrets of Thread and HomeKit

The internet of mi. Discussing Xiaomi, Yonomi and smart homes

Wall Street’s perspective on IoT and the plague of CES

Smart coffee makers, cheap light bulbs and better voice control

Hanging with my husband: His thoughts on our smart home

Exploring Amazon’s Echo and the retailer’s home automation channel plans

Looking for an architecture for the internet of things? Try DNS.

Building networks that can expand and survive the internet of things, plus some tips on crowdfunding

Why the internet of things should be designed with efficiency in mind

Comments are closed.