Editorial theme C / F

Subcontracting chains

Behind the provider the bank chose there is a host, a managed-service firm, a support centre, sometimes a module vendor. Each may touch the data. The bank has signed with only the first.

Thesis — A bank cannot control a risk it has not mapped.

Eight questions that deserve a written answer

For each critical service, an institution should be able to give its counsel or its supervisor a documented answer to each of these questions.

  1. Who actually hosts the data?
  2. Who administers the infrastructure?
  3. Which subcontractors are involved, and at which tier?
  4. From which countries?
  5. Who holds privileged access?
  6. What controls apply to that access?
  7. Can the provider change subcontractors or terms without consent?
  8. Can the bank, in practice, audit beyond the first tier?

In most institutions the first two get a quick answer. From the third onwards, someone has to write to the provider, wait, chase. The last two often go unanswered.

Where the opacity comes from

Rarely from a wish to hide anything. More often from industrialised offerings: standard-form contracts, subcontractor lists published on a web page and changeable on thirty days' notice, certifications covering “all services” without saying which. Facing a global provider, a mid-sized Monaco bank negotiates almost nothing.

That imbalance is one more reason to favour, for sensitive functions, providers whose chain is short and verifiable — ideally, providers operating in Monaco.

What the rules require

Mapping

Analysis in this section

C · Subcontracting chains2 min

Cascading subcontracting: the risk nobody sees.

The direct provider is assessed. Its own subcontractors rarely are. Beyond the first tier visibility disappears, while access rights multiply.