The Sovereign Cloud Question Inside a Bank

Tue, 14 Jul 2026 00:00:00 -0400

The commitment was made in public, and with confidence. A European bank announced it would run on sovereign cloud, procurement selected a provider, and the contract was signed. Some months later an architecture team ran a data-flow mapping exercise, as a formality, and found that roughly thirty percent of the bank’s data flows sat outside the boundary the sovereign cloud programme had drawn. Fraud screening called a scoring service hosted in the United States on every card transaction. Identity verification handed passport images and selfies to a specialist vendor. Payment routing crossed borders because payments cross borders. Every one of those services had been procured, reviewed, and contracted properly. The commitment had simply been scoped to hosting, and the data was not where the hosting was.

Eu-Banking on Sakura Sky: Cloud, Data, Security

The Sovereign Cloud Question Inside a Bank