← Back to the chapter · Previous detail

Technical detail · Human-Centred Design for IoT

Data contracts, authority, and recovery

The evidence also has data contracts: agreed message fields and what each field means. A prototype may publish MQTT messages with timestamp, device_id, firmware_version, reading_value, battery_mv, and fault_code. That is enough to test a flow, but a release plan must decide which identifiers are personal data, which values are retained, which dashboard fields support a decision, and which logs support diagnostics. AWS IoT Device Shadow, Azure IoT Hub device twins, LwM2M objects, or a simple fleet table can all represent device state; the design question is what state the user, operator, and support team actually need.

Security and privacy decisions belong inside the design loop because they change user trust and product viability. Provisioning, certificate rotation, role-based access, audit logs, consent copy, data deletion, and incident escalation are not separate from the experience. A design that asks a parent, nurse, tenant, or technician to trust automation must also show how authority, recovery, and accountability work when the device is wrong, offline, or compromised.

NIST SP 800-213 provides IoT cybersecurity guidance for connected-product risk and release gates. NISTIR 8259A supplies an IoT device cybersecurity capability baseline for considering secure behavior early.

← Back to the chapter · Previous detail