1. De Situatie
Data Owner
EPD Applicatie
Public Cloud
"Will I face challenges with legislation and cyber threats?"
The Short Answer:
You face fundamental challenges in data sovereignty, supply chain risk, and ransomware resilience.
The paradigm shift: From "Trust in Contracts" (Microsoft's promises) → "Trust in Technology" (Mathematical certainty).
2. Wetgevende Storm & Dreigingen
Compliance Gap AnalyseBescherming tegen 'Double Extortion' (datalekken).
Mitigatie tegen toegang vreemde mogendheden (CLOUD Act).
Chain responsibility & Risk distribution.
Technical barriers required, no SCCs.
3. The Urgent Danger: Double Extortion
Modern ransomware does two things: 1. Encrypt systems (business shutdown) and 2. Steal data and threaten publication (data breach/fines). Backups only help against point 1.
Hacker breekt in (Admin Account)
-
π
Toegang tot Data
Hacker ziet leesbare patiΓ«ntdata (plain text) of heeft toegang tot sleutels.
-
π€
Exfiltratie (Diefstal)
Data is copied to hacker servers.
-
π’
CHANTEERBAAR
"Betaal of we publiceren alles."
Resultaat: Enorme reputatieschade & AVG-boetes.
Hacker breekt in (Admin Account)
-
π‘οΈ
Toegang tot... Ruis
Hacker only sees encrypted blobs. Keys are not in Azure.
-
π§±
Exfiltratie is Zinloos
Hacker steelt onleesbare data (waardeloos).
-
β
VEILIG
No data leak. No blackmail opportunity. Hacker leaves empty-handed.
4. De Split-Trust Architectuur
How you remain owner of your data while using the power of Azure.
Hospital
(Lokaal Veilig)
CHUNK WORKS
ZERO TRUST LAAG
- On-the-fly Encryptie
- Anonimisering
- No Latency
Azure Cloud
(Onleesbaar)
5. Strategische Keuze Matrix
A comparison of possible routes for a modern hospital.
| Scenario | Juridische Status | Ransomware Risk | Toekomstbestendigheid |
|---|---|---|---|
|
1. Status Quo (Azure Only) |
β Risk
Not compliant (Schrems II)
|
π₯ HOOG
Gevaar op Datalek & Chantage
|
π LAAG
Vulnerable to CLOUD Act
|
|
2. Private Cloud (On-Premise/Legacy) |
β
Veilig
Volledig NL Beheer
|
π§ MEDIUM
Dependent on own security team
|
β GEMIDDELD
Complex, Duur, Verlies innovatie
|
|
3. Azure + Chunk Works (Split-Trust Cloud) |
β
Compliant
Conform NEN7510 / EHDS
|
π‘οΈ LAAG
Data unreadable if stolen
|
π HOOG
Cloud power + Sovereign control
|
|
4. Klassiek Hybride (Data On-Prem, App Azure) |
β οΈ Grijs Gebied
Data 'in use' onbeschermd
|
π§ MEDIUM
Risk of lateral movement
|
π LAAG
Latency issues (HiX performance)
|
|
5. Secure Hybrid (Azure + On-Prem + Chunk Works) |
β
Maximaal Veilig
Data lokaal + Zero Trust Bridge
|
π‘οΈ ZERO TRUST
Volledige segmentatie
|
π FLEXIBEL
Safe transition from legacy to cloud
|