S23k · About
Doctrine
Not Theory.
S23k is the result of 30 years working in environments
where failure is an operational reality — not a planning scenario.
a single carve-out
S23k was not built behind a desk.
It was built in the field.
Jean-Paul Sablerolle began his career in IT operations when systems still failed on hardware — not governance shortfalls. Over three decades he led programmes at KPN, Getronics, Capgemini, Akzo Nobel — in sectors where downtime is not “an incident” but a safety risk.
His track record is concrete: a 76,000-seat global rollout at Akzo Nobel across 220 locations in six months. The real-time COVID testing infrastructure for Eurofins — built while the operational landscape shifted daily. Crisis interventions at Martinair, Essent and ABN AMRO. A carve-out of 600 FTE from KPN IS&P to Spie, including full ERP migration. OT/ICS security programmes for aviation and critical infrastructure across four continents.
and start confessing. The architecture tells the truth."
S23k is the codification of what he saw, recovered, and prevented. Not an academic exercise. An operational system built for those who cannot delegate accountability to a disclaimer.
Private Pilot License. CISSP, CISA, CHFI, CEH. MIT certifications in AI and machine learning. UAS Remote Pilot via Eurocontrol. A background that does not fit a standard consultant profile — because it does not try to.
1989 – 2001
Transition & Programme Foundations
First large-scale programmes at Origin/Atos and Getronics. A structured approach to complex IT transitions — before the industry even had formal vocabulary for it. PRINCE2, ITIL, supply chain management: earned in practice, not on paper.
2002 – 2010
Critical Infrastructure & Global Rollouts
Led the 76,000-seat global rollout at Akzo Nobel. OT/ICS security programmes across four continents. First direct encounter with systems that reveal the truth under pressure about their real dependencies.
2010
S23k.com — Doctrine Begins
S23k founded as a knowledge platform. Not a consultancy label — an attempt to codify what repeatedly went wrong and what repeatedly worked. Doctrine over comfort.
2020 – 2024
Crisis, Cybersecurity & Sovereignty
COVID testing infrastructure for Eurofins built in real time. Director Business Security at Cubics ICT: SIEM/SOC, AI-driven incident response, penetration testing, cybersecurity governance at enterprise scale. Hudson Cybertec (Kiwa): classified OT/ICS assignments.
2025 – Present
Sovereign Ready Program & ZAA
Launch of the full Sovereign Ready Programme — an assessment framework that challenges €40,000+ Big4 engagements by offering the same depth for free, without a registration wall. Zero Assumption Architecture, INCA, CTtN: doctrine that demonstrably holds under stress.
Four Principles.
One System.
S23k doctrine is not a framework imported from outside. It is distilled from what repeatedly worked when assumptions failed, vendors disappeared, and geopolitical shifts made contracts irrelevant.
Architecture designed without relying on assumptions you cannot verify. Every dependency is a risk until proven otherwise.
Control that demonstrably works. Accountability that does not evaporate the moment an incident reaches your boardroom. Built for the moments that count.
Decision-making when time is scarce, stakes are real, and ambiguity becomes an attack vector. Not a slogan — an operational discipline.
Sovereignty is not declared. It is engineered — step by step, verifiable, transferable to those who bear accountability.
S23k is not
S23k is
S23k is for organisations
where failure
is not an option.
Not as a marketing claim. As operational reality. S23k exists for those who know their real chain becomes visible at precisely the moment they can least afford it.
Boards and architects who carry responsibility for continuity — not for comfort. Those who want to replace assumptions with verifiable control.
If this resonates, you are already in the conversation.
- National & critical infrastructure
- Government functions under geopolitical pressure
- Defense & mission-critical systems
- Aviation & ATC environments
- Healthcare & OT/ICS networks
- Energy & utilities
- Boards that need to prove control
Digital sovereignty
is not declared.
It is built.
You cannot govern what you cannot architect.
You cannot claim autonomy over what you cannot control.
Control you cannot prove under stress does not exist.
Start with control
