The proposal looks good. The price fits, the features do too, and the supplier promises that all data will stay in Europe. One question still deserves attention: how much say will you retain over your digital services?

Can you keep working if the supplier fails? Who can access your data? What changes after an acquisition? Can you actually leave, taking your information and business processes with you? Procurement often determines your freedom to choose for years to come.

Control starts before signing

My book Soevereiniteit! Hoe dan? puts control at the centre. Digital sovereignty means retaining authority over data, systems and continuity. You consciously decide which dependencies to accept and what capacity you need to act independently.

Collaboration and outsourcing remain possible. They require visibility into the supply chain, workable agreements, technical safeguards and sufficient expertise of your own. A European address or data centre alone says little about ownership, jurisdiction, administration and access.

Sovereignty affects availability, integrity and confidentiality. Can services continue? Who can change information or systems? Who can read data? Answers require coherence between regulation, organisation and technology.

Buy the ability to leave, too

Suppose a supplier offers a complete data export. A trial reveals that attachments and access permissions are missing. You have files, but cannot continue your work with them. An exit clause becomes useful when leaving is feasible in practice.

Before selecting a supplier, ask for concrete evidence:

  • Authority: who owns the supplier, which jurisdictions matter and who can compel access?
  • Data management: where are data, metadata and backups held; who administers permissions and keys?
  • The supply chain: which subcontractors and technologies are indispensable, and what happens when these change?
  • Continuity and exit: have recovery and migration been tested, are export formats usable, and have assistance, timescales and costs been agreed?

Management identifies critical processes and acceptable dependencies. Procurement translates this into requirements and evidence with the service owner, legal advisers, architects and security specialists. The same considerations belong in contract management and renewal.

You cannot investigate every supplier entirely yourself

Having each customer investigate the same technical, organisational and legal reality takes considerable time. Not every organisation has the expertise or obtains sufficient access. Suppliers also receive piles of similar questions.

A silver ocicat inspects a server while two other ocicats examine a shared evidence file

This is where SAFARI, the Sovereignty Assurance Framework for Autonomy, Resilience & Independence, helps. This open methodology links the eight goals of the European Cloud Sovereignty Framework to controls in ISO 27001:2022. It examines the customer’s actual control over a service.

SAFARI covers strategic authority, jurisdiction, data and AI, operational continuity, the supply chain, technology, security and compliance, and sustainability. Fixed questions, evidence requirements and scoring rules give buyers and assessors a shared language.

The achieved level and the strength of evidence are assessed separately, each from 0 to 4. A supplier statement carries different weight from documentation, technical evidence or independent verification. The lowest level among the designated core goals determines the overall level, keeping material weaknesses visible.

Sharing assessments requires clear boundaries

This common approach provides a basis for organising assessments jointly. A competent, independent party can examine shared components of a service. Multiple customers can then use relevant findings in their own purchasing decisions.

Always check the assessment’s coverage: which service, version, supply chain, period and assertion were examined? Which criteria and limitations apply? Is the assessor competent and independent? What degree of assurance does the report provide, and are you permitted to use it for this purpose?

A report on one environment does not automatically cover your configuration and agreement. The customer’s own implementation still matters. Reuse what demonstrably fits and have the gaps assessed separately.

SAFARI is not a universally valid supplier certification. A formal assurance engagement requires safeguards for acceptance, independence, procedures and reporting. The methodology follows the structure of ISAE 3000 for this purpose. A completed questionnaire alone does not constitute an assurance conclusion.

Start with your next purchase

Choose a critical service. Specify the control you need, the evidence required and who decides. Request existing assessment reports, check their suitability and investigate gaps. Agree safeguards and exit arrangements, then review them throughout the contract, especially after acquisitions or supply chain changes.

Procurement can thus preserve the organisation’s ability to choose later. Management remains responsible for accepted dependencies and residual risks.

Want to discuss this with colleagues? Read the Dutch two-page briefing directly in OciDeck. It is plain Markdown and also opens in other text editors.

Read more about SAFARI or explore the full methodology and assessment questions. SAFARI v0.9 is a voluntary draft methodology by Brenno de Winter and Stichting LibreKAT, available under CC BY-SA 4.0. Joint assessment and reuse of findings are described here as a possible application.

The two images accompanying this article are AI-generated illustrations.