Skip to content
Free public beta until December 4, 2026: every course is open, no card needed. After that, the first chapter of each course stays free and full access is a one-time $39 ($19 for up to 100 founding members chosen for helpful feedback). Your progress is kept. How the beta works

iot

Explaining why IoT security differs -- physical consequences, long lifetimes, fleets -- with real incidents

taught

Taught in

Requires

Local knowledge map

Local knowledge map

Mapping a device against NIST IR 8259A, ETSI EN 303 645 and… Planning a connected capstone with requirements, a… Segmenting networks and scoping credentials and ACLs… Signing and verifying firmware images with manifests and… Storing secrets on a device with NVS encryption, the… Tracing a chain of trust from ROM through bootloader to app wit… Validating a certificate chain to a trusted root with… Building a data-flow diagram with trust boundaries and listin… Choosing hashes, MACs, symmetric encryption, public-key encryption… Recognising when a system is safety-critical and… Explaining why IoT security differs -- physical consequences… Analysing agriculture and water IoT systems Analysing connected robotics and scientific instruments Analysing environmental and infrastructure… Analysing home and building automation systems --… Deciding between a gateway and direct-to-cloud… Drawing a system's architecture and writing down the… Placing C# in an IoT system -- gateways, back ends, tools and… Splitting an IoT back end into ingest, state, API and jobs,… Weighing what a managed IoT service does against its… Comparing local-only, self-hosted, managed-cloud and… Ingesting telemetry from a broker into a store with validation… Naming the roles in a connected system (device, gateway,…

Click to expand

Solid arrows are required prerequisites; dashed are recommended or helpful. Lower rows are more foundational. Click any box to jump to that concept.