Energy & electric grid | Modelled case study
Test cryptographic key recovery during a grid blackstart scenario
Can essential operators and systems recover credentials when normal identity, network, and key services are unavailable?
The modelled organisation
A recognisable problem reaches the operating agenda
This composite scenario follows the Business Continuity · Control Systems · Key Custodians functions. It is grounded in the cited problem context but does not identify a real customer.
Operating environment
An electric utility coordinates control centres, substations, protection systems, field communications, market interfaces, recovery sites, and specialist suppliers.
What is at stake
Security work must fit narrow operating windows and preserve safe control, restoration capability, and accountable remote access to critical assets.
Situation
Recovery plans often assume reachable cloud KMS, synchronized directories, healthy certificate authorities, and staff who may be inaccessible.
Event that forces action
Blackstart exercise, regional disaster planning, or dependency review.
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.
primary and alternate control sites
blackstart communication keys
offline recovery material
restoration authentication workflow
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
Recovery plans often assume reachable cloud KMS, synchronized directories, healthy certificate authorities, and staff who may be inaccessible.
Frame the decision the owners must make
Can essential operators and systems recover credentials when normal identity, network, and key services are unavailable?
Apply QNSI to the controlled boundary
Use QNSI key ownership and dependency records to design offline recovery sets, authorization roles, expiry, and reconciliation.
Leave the team with a concrete result
A blackstart crypto-recovery exercise report with dependency failures, recovered services, elapsed decisions, and remediation.
Prove the result in the organisation's environment
The utility proves secure storage, dual control, facility access, restoration sequencing, revocation, and post-event reconciliation.
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 blackstart crypto-recovery exercise report with dependency failures, recovered services, elapsed decisions, and remediation.
Independent validation boundary
The utility proves secure storage, dual control, facility access, restoration sequencing, revocation, and post-event reconciliation.
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.