IoT & smart cities | Modelled case study
Align IoT cryptographic support with the promised support period
Can the manufacturer maintain keys, certificates, libraries, and update trust for the whole declared support period?
The modelled organisation
A recognisable problem reaches the operating agenda
This composite scenario follows the Product Management · Product Security · EU Compliance 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
A support promise can exceed certificate validity, cloud dependencies, component maintenance, and the device's ability to adopt safer algorithms.
Event that forces action
CRA technical-file preparation, product launch, or support-period revision.
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.
device models and firmware
support-period commitments
algorithm and key inventory
update and end-of-support evidence
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
A support promise can exceed certificate validity, cloud dependencies, component maintenance, and the device's ability to adopt safer algorithms.
Frame the decision the owners must make
Can the manufacturer maintain keys, certificates, libraries, and update trust for the whole declared support period?
Apply QNSI to the controlled boundary
Join QNSI crypto inventory and lifecycle metadata to component support, key plans, update mechanisms, and product variants.
Leave the team with a concrete result
A support-period crypto schedule exposing expiry cliffs, unsupported dependencies, and funded transition work.
Prove the result in the organisation's environment
The manufacturer and counsel approve support commitments, vulnerability handling, update feasibility, and market obligations.
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 support-period crypto schedule exposing expiry cliffs, unsupported dependencies, and funded transition work.
Independent validation boundary
The manufacturer and counsel approve support commitments, vulnerability handling, update feasibility, and market obligations.
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.