Securing IoT's Trust Boundaries: Navigating Complexity with NCSC Patterns
summary
Claims a reproducible engineering approach: applies NCSC cross-domain patterns to IoT, implements an import pipeline that terminates LoRaWAN and inspects decrypted payloads, uses data diodes and schema/analytics checks, and pushes configuration via a declarative model over MQTT so endpoints are rebuilt from approved configs rather than session state. Demonstrates a Chariot-backed broker with Chariot memory-safe compartments to run confined parsers that block persistent compromise and prevent malformed updates like the CrowdStrike-style failure.
AI-written summary · about
chapters (12)
- 0:00NCSC patterns for IoT security
- 1:50Cross-domain solutions and NCSC patterns
- 3:59NCSC cross-domain design principles
- 5:25Isolation vs sharing challenges
- 7:53IoT needs dynamic trust boundaries
- 8:34Securing LoRaWAN networks
- 10:40IoT data import/export pipelines
- 12:46Smart meter updates example
- 14:51NCSC patterns for memory-safe hardware
- 17:38Key takeaways
- 18:42Managing trust relationships
- 19:46Q&A: Capability vs language security
related talks
11mSecuring IoT Integrations with Third-Party Services
29mEnabling a secure IoT from design to deployment
31mSecuring the Internet of Things
47mPatterns of Authentication and Self-Announcement in IoT
35mIoT Cornerstones of Security
30mSupply Chain Security for IoT Devices
31mEcosystem, Interoperability and Standards: IoT Security
59mArchitectural Patterns Focus: Security