Oil, gas & pipelines | Modelled case study
Produce a pipeline cyber-incident evidence pack during operations
Which operational assets and cryptographic controls were affected, and what containment is safe while product continues to move?
The modelled organisation
A recognisable problem reaches the operating agenda
This composite scenario follows the Incident Commander · Pipeline Operations · Regulatory Affairs 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
Responders must join corporate identity, vendor access, SCADA, field device, and key-management evidence without disrupting safety-critical operations.
Event that forces action
Compromised remote account, ransomware, signing-key exposure, or anomalous controller change.
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.
affected operational assets
key and access evidence
containment chronology
regulator and executive reporting package
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
Responders must join corporate identity, vendor access, SCADA, field device, and key-management evidence without disrupting safety-critical operations.
Frame the decision the owners must make
Which operational assets and cryptographic controls were affected, and what containment is safe while product continues to move?
Apply QNSI to the controlled boundary
Correlate QNSI crypto ownership, key state, service dependencies, and audit references with operational incident milestones.
Leave the team with a concrete result
A regulator-facing appendix separating confirmed impact, containment, unavailable telemetry, safety constraints, and follow-up tests.
Prove the result in the organisation's environment
The operator and counsel decide regulatory reporting, operational actions, privilege, public communication, and recovery acceptance.
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 regulator-facing appendix separating confirmed impact, containment, unavailable telemetry, safety constraints, and follow-up tests.
Independent validation boundary
The operator and counsel decide regulatory reporting, operational actions, privilege, public communication, and recovery acceptance.
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.