Ask who holds the signing keys and you open an important security discussion. Stop there and you may miss the operating model around them. A business can retain key material yet still depend on another party for policy changes, access restoration, transaction submission or the records needed to investigate an incident.
Infrastructure selection should make these dependencies explicit. The goal is not to eliminate every external service. It is to understand which decisions remain with the enterprise, which responsibilities are delegated, and what happens when a dependency fails.
Turn “control” into questions that can be tested
Begin with authority. Who may propose a payment, approve it, change the approval policy or suspend activity? Can one person perform several of those roles? What prevents an emergency process from becoming a permanent shortcut?
Then examine evidence. Can a reviewer connect a transaction to the policy and authorization that applied at the time? Are sensitive records available only to the right people? Can the institution export what it needs without depending on screenshots or informal support requests?
Finally, examine continuity. If a service is unavailable, which operations stop, which can continue safely, and who decides? These questions turn an abstract claim into a concrete acceptance plan.
One platform still needs a dependency map
An integrated platform can make coordination easier, but a single commercial relationship should not be mistaken for the absence of dependencies. Networks, hosting providers, communications services and internal administrators may still sit on the critical path.
The Basel Committee’s operational-resilience principles put governance, dependency mapping, continuity testing and incident management alongside technology resilience. This is useful context for bank infrastructure assessments, not a certification checklist that a product can claim to satisfy automatically. 1
Make the recovery exercise part of procurement
A practical evaluation could follow a fictional Friday-evening incident: an approval service is unavailable while a time-sensitive transfer awaits authorization. Ask the supplier and internal team to explain the escalation path, the evidence retained, the permitted actions and the conditions for resuming normal service.
Include an exit exercise too. Identify the records, configuration and responsibilities that would need to move if the institution changed its operating arrangement. Basel Committee commentary also highlights contingency planning and exit strategies in managing third-party dependencies. 2
Ovryde describes an integrated enterprise offering powered by Hybrid Chain, with deployment choices and an emphasis on enterprise control. Those choices should be translated into a documented responsibility model for each engagement. 3
Control becomes credible when the institution can exercise it under pressure, not only describe it during procurement.