Building With Security First on the SmartThings Platform
summary
SmartThings requires device identity (X.509 or signed serials) and splits device trust into level one / level two / level three certification with hardware root of trust mandatory for levels two and three, secure OTA updates required for all, and hardware encryption for PII. The SmartThings Device Kit supplies identity and root trust. Integrations must use fine‑grained OAuth scopes, store refresh tokens on server backends to maintain long‑lived access, validate incoming HTTP signatures, and note subscription tokens expire after five minutes.
AI-written summary · about
chapters (9)
- 0:00Introduction and agenda
- 1:02Device maker security considerations
- 8:15SmartThings Device Kit overview
- 9:01UI security design principles
- 14:21Principle of least privilege
- 21:41App and Lambda security tips
- 31:19Certification and fail-safe design
- 40:08Device identity and authentication
- 41:15Q&A session
related talks
39mUnleash the Power of Cloud Connected Devices with SmartThings
30mSupply Chain Security for IoT Devices
39mApplied IoT security for healthcare and industrial
44mScaling Your Business with SmartThings
18mIoT as a Service: How SmartThings is Embracing Enterprise
43mDevice Security in IoT
18mBeyond the Default Password: Building Trustworthy IoT Products
45mIoT 2.0: The Next Phase of SmartThings Engagement and Growth
