veyepar: The Internet of Scary Things - tips to deploy and manage IoT safely

Author(s):	Christopher Biggs
Location	Plenary Hall
Date	jan Mon 16	Days Raw Files
Start	22:40	First Raw Start	22:17
Duration	0:30:0	Offset	0:22:47
End	23:10	Last Raw End	23:17
Chapters	00:00 0:06:08
Total cuts_time	29 min.

http://linux.conf.au/schedule/presentation/150/
raw-playlist raw-mp4-playlist encoded-files-playlist host archive tweet mp4 svg png

assets release.pdf The_Internet_of_Scary_Things_tips_to_deploy_and_manage_IoT_safely.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:

Locked:

clear this to unlock

Locked by:

user/process that locked.

Start:

initially scheduled time from master, adjusted to match reality

Duration:

length in hh:mm:ss

Name:

Video Title (shows in video search results)

Emails:

email(s) of the presenter(s)

Released:

has someone authorised pubication

Normalise:

Channelcopy:

m=mono, 01=copy left to right, 10=right to left, 00=ignore.

Thumbnail:

filename.png

Description:

markdown

IoT has been in the news for the wrong reasons, with poorly designed
and managed IoT devices being blamed for contribiting to denial of service
attacks.

This presentation covers

* risks to your own business from IoT takeup and how to avoid them
  * how to be a good citizen by ensuring your devices are not a risk to others
  * how to run your own IoT control and monitoring hub in the cloud, and 
    to coerce incompatible devices into working together.
  * points to consider when selecting IoT products

IoT is immature - many devices are not as secure as they could be.  
I cover how to structure your network in order to reduce the attack 
surface presented by your devices.

IoT is faceless, many devices are unobtrusive and you may not notice
if they "go rogue".   I offer advice on how to establish a management regime
to limit the damage a misbehaving device can do.

IoT is fragmented, everyone is scrabbling to be the market leader, so
many products do not work well together.  This means each device may want 
to talk to its own cloud service.  I cover how to bridge uncooperative 
products to narrow or eliminate need for direct internet access, and offer
advice on strategies to build a cooperating whole.

Comment:

production notes