Manufacturing | Modelled case study
Use machine identity to enforce factory-cell boundaries
Can a machine authenticate only to the controllers, brokers, and services required for its production role?
The modelled organisation
A recognisable problem reaches the operating agenda
This composite scenario follows the OT Architecture · Plant Engineering · Identity functions. It is grounded in the cited problem context but does not identify a real customer.
Operating environment
A manufacturer integrates production cells, robots, engineering systems, digital twins, firmware, machine identities, and a multi-tier supplier network.
What is at stake
An untrusted device, configuration, or supplier certificate can stop a line, corrupt quality decisions, or propagate risk across multiple products and plants.
Situation
Cloned images, shared certificates, and flat broker credentials let one compromised machine impersonate peers or cross production cells.
Event that forces action
Smart-factory rollout, segmentation programme, or line reconfiguration.
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.
production-cell machines
machine identity issuer
industrial network policy
maintenance and orchestration services
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
Cloned images, shared certificates, and flat broker credentials let one compromised machine impersonate peers or cross production cells.
Frame the decision the owners must make
Can a machine authenticate only to the controllers, brokers, and services required for its production role?
Apply QNSI to the controlled boundary
Map machine identities, issuers, algorithms, authorized services, line ownership, and rotation constraints in QNSI.
Leave the team with a concrete result
A cell-level machine trust matrix with shared identities, unauthorized reach, and enrollment remediation.
Prove the result in the organisation's environment
The manufacturer tests enforcement, production timing, fail-safe behavior, maintenance access, and recovery.
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 cell-level machine trust matrix with shared identities, unauthorized reach, and enrollment remediation.
Independent validation boundary
The manufacturer tests enforcement, production timing, fail-safe behavior, maintenance access, and recovery.
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.