IoT & smart cities · Smart City Platform · Device Operations · Procurement
Enroll unique identities for a citywide sensor fleet
Can each camera, meter, light, and environmental sensor be traced to an authorized manufacturing and enrollment event?
Operational pain
Mass procurement encourages shared bootstrap credentials and opaque vendor roots that undermine revocation and device attribution.
Trigger
New city platform, multi-vendor tender, or discovery of cloned device credentials.
QNSI contribution
Connect the decision to a controlled security path
Track device identity, manufacturing source, issuer, algorithm, owner, location, and enrollment evidence in QNSI.
Decision artifact
A municipal device identity ledger with duplicate credentials, unapproved issuers, and enrollment confidence.
What still requires validation
The city tests factory provisioning, anti-cloning, privacy, physical replacement, revocation, and supplier evidence.
External problem context
Primary sources
These sources establish the external requirement or risk context. They do not endorse HEOSSI or prove that QNSI completed this scenario.
Evidence boundary
What this page does—and does not—prove
This is a product evaluation pattern, not a customer case study, certification, legal opinion, regulator endorsement, or claim that a production deployment completed the described work.