Malaysia Raised the Sovereignty Bar. Your Architecture Was Signed Years Ago.
- By Winston Thomas
- September 14, 2026

Ask a Malaysian data leader whether digital sovereignty matters and you get a yes in two seconds. Ask which contract in the estate actually decides it, and the room goes quiet.
That silence is what the IBM Executive Roundtable at the CDDO Summit Malaysia on Sept. 23, 2026, is built around. Dickson Woo, country general manager for IBM Malaysia, has spent much of this year inside those conversations. He keeps arriving at the same scene: A client asks for digital sovereignty; the architecture team goes looking; what comes back is a bill for decisions nobody remembers making.
“They realize that sovereignty cannot be bolted on later,” Woo says. “Over time, they have created dependencies on external control planes, fragmented technology estates, proprietary architectures, and governance models that were optimized for speed but not control.”
Speed was the right call at the time. That is what makes the data architecture expensive to unwind.
The readiness number Malaysia should watch
Malaysia’s most useful AI statistic this year came out of its most regulated sector. The AICB–Ecosystm “AI in Practice” report surveyed 87 senior leaders across Malaysian commercial, digital and Islamic banks and development financial institutions. It found 44% still in the “developing” stage of AI readiness, with fragmented capabilities across data, skills and operating models. Only 17% have reached established or advanced maturity.
Then the number that should stop any Malaysian CDO cold: Just 25% trust AI-generated outputs enough to act on them in key business decisions.
That is banking, an industry that has run under Bank Negara Malaysia’s Risk Management in Technology policy for years. BNM says more than 70% of financial service providers have deployed at least one AI application. Adoption is not the constraint; confidence in the underlying data is.
The policy layer has moved faster still. On July 28, 2026, the government launched AI Malaysia Berhad, converting the National AI Office into a permanent corporation under the Ministry of Digital, and unveiled the National AI Action Plan 2026–2030: 28 initiatives across five enablers, one of them data and computing infrastructure. A risk-based AI governance bill is out for consultation. Budget 2026 allocated MYR2 billion for a sovereign AI cloud through the MCMC.
So the national agenda now runs ahead of most enterprise data estates. That inversion is the story for anyone holding a CDO, CISO or CAIO title here.
Want to join the Sept. 23, 2026, IBM Executive Roundtable titled “Trusted Data, Scalable AI: Malaysia’s Path Forward? It will be held right after the Chief Digital & Data Officer Malaysia Summit and gives Malaysian data leaders the opportunity to map their own data strategy against a tightened PDPA and a national post-quantum migration plan. Register here, or contact Usha G [email protected] for additional information.
Woo’s contrarian call: It is not data quality
Woo expects Malaysian leaders to name three obstacles. Fragmentation, where data exists but never where it is needed; trust and governance; and the distance between a pilot and enterprise-wide impact.
“Organizations don’t have a data problem,” he observes. “They have a connectivity problem.” Then Woo takes aim at the answer he expects most often. “We often say that our biggest challenge is data quality. I don’t think it is.”
You can improve data quality, modernize platforms, and retrain models. What resists purchase is breaking silos, assigning accountability for data across business lines, and changing how people decide. IBM’s 2026 CEO Study data for Malaysia, shared with CDOTrends, puts 80% of surveyed Malaysian CEOs behind the view that AI success depends more on adoption than on the technology. A third of the respondents cite poorly integrated data as a top barrier to innovation.
Connectivity is an architecture question, which is where sovereignty stops being a policy debate.
Sovereignty, translated into procurement
Sovereignty has outgrown data residency. “That was yesterday’s conversation,” Woo says. He splits it four ways: data, operational, technology and AI sovereignty. Control over where data sits, but also over who operates the environment, what the architecture commits you to, and where models run. His keenest observation came earlier this year. “Sovereignty is not defined by who provides the technology — it’s defined by who remains in control.”
Malaysia has written much of this into policy. The National Cloud Computing Policy, adopted in August 2025, sets four data classification tiers — public, internal, restricted and confidential — each with defined deployment requirements. Public data can sit on public cloud with basic protections. Confidential data must be processed on sovereign cloud infrastructure inside Malaysia, under national encryption, access control and monitoring standards. Cross-border movement tightened at the same time. Since April 2025, transfers under the amended Personal Data Protection Act turn on a transfer impact assessment rather than a whitelist of approved countries.
Turn that into board questions, per critical system:
- Who operates the control plane?
- Where do the encryption keys live?
- Where does inference run?
- Who could compel disclosure under a foreign statute?
If assembling those four answers takes more than a week, you have a sovereignty posture you have never audited.
IBM has a commercial answer. Sovereign Core went generally available at Think 2026 in May 2026, built on Red Hat OpenShift, with a customer-operated control plane, in-boundary identity and encryption keys, governed AI inference and continuous compliance monitoring. Version 1.1 in July nearly doubled its embedded compliance frameworks to 235. Sovereignty, in Woo’s phrasing, “should be engineered into the platform, not layered on through policy or contractual assurances.”
Woo’s four pillars — data, operational, technology and AI sovereignty — work as an architecture review regardless of who you buy from. They also raise a timing question: Control matters most at the moment a system acts on its own.
Agents removed the person who caught the error
IBM closed its acquisition of Confluent on March 17, 2026, at roughly USD11 billion in enterprise value (about USD9.3 billion in equity value, at USD31 a share). Woo says client conversations shifted immediately.
“A year ago, clients were asking how to build AI. Today, they’re asking how do we ensure every AI decision is powered by trusted, real-time data.”
“Organizations don’t have a data problem. They have a connectivity problem.” — Dickson Woo @ IBM
The reason is structural. Analytics could tolerate yesterday’s data because a person sat between the dashboard and the decision, catching the obvious errors. Agents remove that person. Stale data stops being an inconvenience.
BNM Governor Abdul Rasheed Ghaffour put the governance half plainly in July. AI “belongs firmly on the board agenda,” he said, and accountability for AI-driven decisions stays with human leaders. Boards that accept that accountability will ask what the foundation returns.
What the foundation pays for
Platform work rarely shows up in an earnings call, which is why this part of the argument usually goes missing.
A regional example makes it concrete. TPBank, a Vietnamese digital bank with 12 million customers, spent three years modernizing its data infrastructure on IBM Cloud Pak for Data. Then a credit card acquisition program underperformed. The data team built propensity models on that foundation and reported a 24% increase in customer conversion, more than 15 models deployed in 2024, and model development time cut by 30% to 40%.
The sequence matters more than the numbers. The platform came first, and it looked like cost for three years.
Two reads on the same problem
If you are the CDO, take Woo’s reframe: connectivity, not quality. The metric is not how clean the warehouse is. It is whether an agent can reach governed data without a human assembling an extract, and how many contested business terms have a named owner. The 25% trust figure is your budget argument.
If you are the CISO, the operative deadline is 72 hours. Under the amended PDPA, controllers must notify the Commissioner as soon as practicable and within 72 hours where a breach causes or is likely to cause significant harm, and tell affected individuals within seven days. Maximum fines for breaching the data protection principles rose to MYR1 million, with imprisonment up to three years.
That clock is a lineage test more than a legal one. It asks whether you can enumerate, under pressure, what data was in the blast radius, who touched it, and which model or agent consumed it.
Woo’s version: “The laggards prepare for audits. The leaders build for trust.” The shift he wants from boards is from asking whether the organization is compliant to asking whether it can demonstrate control at any moment.
Twelve months out, he wants AI in Malaysian organizations to be “as invisible as electricity,” embedded in decisions and workflows rather than announced as a strategy.
Electricity earns that invisibility by being engineered before anyone flips a switch. Sovereignty works the same way, and it costs far less to build in than to retrofit.
Image credit: iStockphoto/tampatra
Stay ahead with CDO Nexus
Join an exclusive community of CDOs and data leaders
- Access curated trends and thought leadership from IBM and industry experts.
- Participate in private roundtables and webinars to solve regional CDO challenges.
- Connect with a network of like-minded leaders navigating the same data landscape.
Winston Thomas
Winston Thomas is the editor-in-chief of CDOTrends. He likes to piece together the weird and wondering tech puzzle for readers and identify groundbreaking business models led by tech while waiting for the singularity.