Digital assets & fintech | Modelled case study
Design a recoverable wallet-key lifecycle without creating a master-key shortcut
How can the service recover from device loss or operator unavailability without introducing an ungoverned universal recovery secret?
The modelled organisation
A recognisable problem reaches the operating agenda
This composite scenario follows the Wallet Platform Lead · Business Continuity Manager functions. It is grounded in the cited problem context but does not identify a real customer.
Operating environment
A regulated fintech or digital-asset operator coordinates wallets, ledgers, approval services, partner APIs, reporting systems, and multiple custody boundaries.
What is at stake
A weak identity or signing boundary can turn one compromised operator, integration, or recovery path into unauthorized movement or unreliable financial evidence.
Situation
Recovery designs can silently defeat tenant isolation when shards, wrapping keys, break-glass accounts, or backup media share the same uncontrolled root.
Event that forces action
A custody product adds recovery, inheritance, or enterprise administrator functions.
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.
device and account keys
recovery shards and wrapping keys
break-glass identities
backup and reconstruction 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 designs can silently defeat tenant isolation when shards, wrapping keys, break-glass accounts, or backup media share the same uncontrolled root.
Frame the decision the owners must make
How can the service recover from device loss or operator unavailability without introducing an ungoverned universal recovery secret?
Apply QNSI to the controlled boundary
Use QNSI key metadata and policy boundaries to document recovery roles, wrapped-material locations, rotation conditions, and tenant-specific separation.
Leave the team with a concrete result
A recovery trust map with separation-of-duty checks, rehearsal results, and residual single points of compromise.
Prove the result in the organisation's environment
Independent reviewers must test reconstruction thresholds, deletion, regional failure, insider resistance, and customer agreements.
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 recovery trust map with separation-of-duty checks, rehearsal results, and residual single points of compromise.
Independent validation boundary
Independent reviewers must test reconstruction thresholds, deletion, regional failure, insider resistance, and customer agreements.
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.