IoT & smart cities | Modelled case study
Prove secure communications from constrained devices through an IoT gateway
Where does end-to-end protection terminate, and which gateway can see or modify device data?
The modelled organisation
A recognisable problem reaches the operating agenda
This composite scenario follows the IoT Architecture · Network Security · Device Vendor functions. It is grounded in the cited problem context but does not identify a real customer.
Operating environment
A city or IoT operator manages large fleets of constrained sensors, gateways, cloud ingestion, device enrollment, updates, support commitments, and multiple vendors.
What is at stake
A shared credential or abandoned update path can expose an entire fleet whose devices differ in hardware, connectivity, ownership, and remaining support life.
Situation
Marketing describes encrypted devices while protocol translation, broker termination, and cloud ingestion create plaintext or re-signing boundaries.
Event that forces action
IoT platform selection, privacy review, or post-quantum gateway pilot.
Concrete system boundary
Systems this case study puts in scope
The model is specific about the operational surfaces that must be discovered, changed, or independently checked.
constrained end devices
IoT gateway
cloud ingestion endpoint
device-to-gateway and gateway-to-cloud trust
Modelled case study walkthrough
How this organisation would use QNSI
The walkthrough connects the real-world problem to a bounded QNSI contribution and an independently reviewable result.
Recognise the operating condition
Marketing describes encrypted devices while protocol translation, broker termination, and cloud ingestion create plaintext or re-signing boundaries.
Frame the decision the owners must make
Where does end-to-end protection terminate, and which gateway can see or modify device data?
Apply QNSI to the controlled boundary
Map algorithms, keys, session termination, gateway identities, transformations, and evidence status in QNSI.
Leave the team with a concrete result
A device-to-cloud cryptographic boundary diagram with plaintext points, trust changes, and test captures.
Prove the result in the organisation's environment
Architects verify protocol negotiation, gateway hardening, device limits, data authenticity, latency, and key storage.
What useful success looks like
A decision artifact plus proof from the real environment
The model stops at a target result. It becomes an actual case study only when a customer produces and independently validates this evidence in production.
Decision artifact
A device-to-cloud cryptographic boundary diagram with plaintext points, trust changes, and test captures.
Independent validation boundary
Architects verify protocol negotiation, gateway hardening, device limits, data authenticity, latency, and key storage.
Real-world problem grounding
Primary sources behind the model
These sources establish the external requirement, failure mode, or risk context used to model this case. They do not endorse HEOSSI or prove that QNSI completed the scenario.
Customer evidence status
This is modelled, not a customer claim
The organisation is a composite and the result is a target state. This page does not prove a deployment, customer outcome, certification, legal conclusion, regulator endorsement, or completed control.