Warning signs

The weak signals decision-makers should not ignore.

None of these situations is a breach in itself. All of them are common. And all of them should prompt a review by compliance, risk and, ultimately, the board.

Sign 01 · Foreign jurisdictions

A provider runs on cloud infrastructure whose controlling jurisdiction is poorly understood.

What it means

The contract says “hosted in Switzerland” or “in Ireland”. It does not say who operates the servers, which group that operator belongs to, or which law it answers to. The bank knows an address, not a chain of control.

Why it matters

The US CLOUD Act, for instance, targets the provider that holds or controls the data, not the place where it is stored. Stopping at the hosting country risks underestimating exposure to foreign requests — or overestimating it.

Preventive measures

  • Have the actual infrastructure operator, its parent company and its main subcontractors identified.
  • Ask counsel to analyse which foreign laws may apply to each of them.
  • Get the provider's response to a foreign authority's request in writing.
  • For the most sensitive data, encrypt with keys held by the bank.

Sign 02 · Subcontracting chains

Administrator access is poorly documented.

What it means

Nobody at the bank can produce a list of the people with privileged access to the systems holding its data: the provider's staff, night-time support, the managed-service firm, remote maintenance.

Why it matters

An administrator account can, depending on its rights, read, extract or alter data. It is an attacker's favourite target. And access from a third country can, in itself, raise a data-protection question.

Preventive measures

  • Ask for an inventory of privileged access: who, from where, why, under which procedure.
  • Require these accesses to be logged, with a right to inspect the logs.
  • For certain operations, require prior approval by the bank.
  • Review permissions at least once a year.

Sign 03 · Subcontracting chains

The bank does not know some of its second- or third-tier subcontractors.

What it means

The contracting provider has been assessed. Its hosting firm, the vendor of one of its modules, the support centre it uses — much less so. Beyond the first tier, visibility drops fast.

Why it matters

An outage or intrusion at a distant subcontractor has the same effect as a failure of the main provider — without ever having appeared in a risk assessment.

Preventive measures

  • Obtain, by contract, the list of subcontractors working on critical functions, with their country.
  • Be notified before any change, with a right to object and, if needed, to terminate.
  • Have audit, security and confidentiality requirements flowed down the whole chain.
  • Keep a register that goes down to the lower tiers for critical services.

Sign 04 · Bank outsourcing

Data is sent without enough minimisation.

What it means

The provider receives the whole client file when its service needs only part of it — a few fields, or a few cases. This is common with screening, scoring and analytics tools.

Why it matters

Every piece of data that leaves is a piece of data exposed. Minimisation is a principle of Monaco's Law No. 1.565 as well as the GDPR. Above all, it is the simplest way to limit what a leak can take.

Preventive measures

  • List, service by service, the data actually needed.
  • Consider a set-up where only flagged cases are sent.
  • Pseudonymise where identity is not essential.
  • Document the justification for each outbound data flow.

Sign 05 · Accountability and governance

Audit rights are limited.

What it means

The contract offers only a standard certification report, or surrounds audits with so many conditions — notice, scope, cost — that one will never take place.

Why it matters

DORA, now applicable to Monegasque financial institutions under the Monetary Agreement with the EU, requires effective rights of access, inspection and audit over ICT service providers. A certification report has its uses, provided you know exactly what it covers.

Preventive measures

  • Negotiate real audit and access rights, including for the supervisory authority.
  • Check the exact scope of certifications: systems, sites, period.
  • Consider pooled audits with other institutions.
  • Track the implementation of audit findings.

Sign 06 · Accountability and governance

The exit plan has never really been tested.

What it means

The clause exists. No one has checked that the data can be retrieved in a usable format, within a time frame compatible with business continuity, and taken over by another team.

Why it matters

Without a workable exit, the bank no longer has a real choice: price rises, changed terms or a degraded service will have to be accepted. It is the quietest form of dependency.

Preventive measures

  • Write an exit strategy for each critical service: data, formats, timelines, fallback.
  • Test a full export and re-import of the data.
  • Check what the outgoing provider commits to doing, and for how long.
  • Report test results to the board.

Sign 07 · Systemic and reputational risk

Several institutions depend on the same critical provider.

What it means

In a financial centre this size, banks, asset managers and family offices often end up with the same software vendors, managed-service firms or screening services. Each manages its own risk. No one sees the concentration.

Why it matters

An outage or intrusion at that provider would hit several firms on the same day. The Financial Stability Board and DORA both address this concentration risk explicitly.

Preventive measures

  • Identify, in each institution, the providers whose failure would be critical.
  • Encourage an aggregated, confidential map of dependencies across the financial centre.
  • Do not build the continuity plan on the very provider it is meant to replace.
  • Run exercises simulating the failure of a shared provider.

Sign 08 · Systemic and reputational risk

Data on high-profile clients is concentrated at loosely supervised intermediaries.

What it means

Beneficial owners, wealth structures, KYC files: this information does not live only inside the bank. It passes through law firms, trust companies, screening providers, document platforms and IT contractors — rarely held to the same standard.

Why it matters

The Panama, Paradise and Pandora Papers came from intermediaries, not banks. In a financial centre with so many prominent clients, a leak of that kind would carry a very heavy reputational cost.

Preventive measures

  • List every third party holding KYC or wealth data, not only IT providers.
  • Classify this data at the highest sensitivity level and restrict its circulation.
  • Require intermediaries to secure it accordingly: encryption, logging, export controls.
  • Prepare the response to a mass leak, including communication with clients and authorities.

Each sign is developed in an in-depth article.

Read the analysis