Oil, gas & pipelines | Modelled case study
Verify firmware before it reaches a pipeline controller
Can field staff prove that a controller image is authentic, approved, and compatible before installation?
The modelled organisation
A recognisable problem reaches the operating agenda
This composite scenario follows the OT Engineering · Product Security · Maintenance functions. It is grounded in the cited problem context but does not identify a real customer.
Operating environment
A pipeline or oilfield operator connects control centres, compressor stations, field controllers, remote sensors, maintenance channels, and regulatory reporting workflows.
What is at stake
A compromised remote identity or software image can affect physical operations, while weak evidence slows containment and mandatory reporting.
Situation
Firmware may travel through vendor portals, laptops, removable media, and staging shares where hashes are copied separately and approval context disappears.
Event that forces action
Safety patch, controller refresh, vulnerability response, or introduction of post-quantum signing.
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.
controller firmware packages
vendor release signer
staging and engineering workstation
field installation and rollback
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
Firmware may travel through vendor portals, laptops, removable media, and staging shares where hashes are copied separately and approval context disappears.
Frame the decision the owners must make
Can field staff prove that a controller image is authentic, approved, and compatible before installation?
Apply QNSI to the controlled boundary
Bind QNSI-supported signature metadata to firmware digest, vendor identity, target model, test record, and maintenance approval.
Leave the team with a concrete result
A field-verifiable firmware manifest with signer, algorithm, device compatibility, evidence, and rollback image.
Prove the result in the organisation's environment
The operator validates vendor keys, controller behavior, safety logic, media handling, offline verification, and rollback.
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 field-verifiable firmware manifest with signer, algorithm, device compatibility, evidence, and rollback image.
Independent validation boundary
The operator validates vendor keys, controller behavior, safety logic, media handling, offline verification, and rollback.
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.