Digital sovereignty
Why a data centre's address says very little about who actually controls the data.
Six editorial themes
Take a sanctions-screening tool, hosted by a foreign cloud provider and used by several banks in Monaco. It touches all six topics at once.
Why a data centre's address says very little about who actually controls the data.
A task can be handed to a provider. The responsibility cannot. The case of AML, KYC and screening tools.
Hosting firms, managed-service providers, support centres: who is working behind the provider the bank chose?
CLOUD Act, FISA, Patriot Act, GDPR, UK, Swiss and Monegasque law: what each text says, and who it applies to.
What is mandatory, what is recommended, what is good practice — and what ends up on the board's desk.
When an incident at a shared provider, or a leak at an intermediary, hits the whole financial centre.
One tool, six questions
Who controls the infrastructure the tool runs on? (A) Does it really need the entire client base? (B) Who, behind the vendor, administers the platform? (C) Which foreign laws may apply to the vendor and its host? (D) Who in the bank approved this choice, and who reviews it each year? (E) And how many other institutions in Monaco use the same service? (F)
None of these questions is enough on its own, which is why the sections keep pointing to one another.