QNSI

Energy & electric grid | Modelled case study

Constrain supplier remote-access trust in electric operations

Which supplier identity can reach which asset, for what task, using which credential and approval?

Accountable ownersOT Access Management · Vendor Risk · Operations
Scenario typeComposite model
Required outputDecision artifact

The modelled organisation

A recognisable problem reaches the operating agenda

This composite scenario follows the OT Access Management · Vendor Risk · Operations 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

Emergency vendor accounts and shared support certificates persist across substations and generation sites after the original work ends.

Event that forces action

Supplier onboarding, access recertification, merger, or remote-access incident.

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.

01

vendor identities

02

jump hosts and remote gateways

03

substation and generation assets

04

work-order approval and session evidence

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.

01

Recognise the operating condition

Emergency vendor accounts and shared support certificates persist across substations and generation sites after the original work ends.

02

Frame the decision the owners must make

Which supplier identity can reach which asset, for what task, using which credential and approval?

03

Apply QNSI to the controlled boundary

Inventory supplier cryptographic identities, endpoints, issuers, validity, owner, and authorized service window in QNSI.

04

Leave the team with a concrete result

A vendor trust ledger exposing shared credentials, expired work orders, overbroad reach, and revocation evidence.

05

Prove the result in the organisation's environment

The operator tests enforcement at jump hosts and endpoints, session monitoring, emergency approval, and contract controls.

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 vendor trust ledger exposing shared credentials, expired work orders, overbroad reach, and revocation evidence.

Independent validation boundary

The operator tests enforcement at jump hosts and endpoints, session monitoring, emergency approval, and contract controls.

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.

QNSI privacy choices

Necessary storage keeps the site secure. With your permission, privacy-bounded analytics help HEOSSI understand pages, journeys, and campaign outcomes. No advertising profiles are created.

Cookie policy