Data Governance
Grace Wainaina sits down with Vernon Yai, a data protection and governance specialist who has spent years helping airport operations teams bring rigor, trust, and speed to geospatial digital twins. Vernon’s lens is pragmatic: integrate only what you can secure, prove, and sustain. In this conversation, he pulls back the curtain on how a modern
Boards demanded tangible AI wins while governance, budgets, and real-world references lagged behind hype-fueled timelines, and that collision of urgency and uncertainty left many technology leaders juggling speed with safety in ways that stalled momentum as often as they sparked it. The strain showed up in planning rooms and steering committees:
Budgets that once celebrated AI’s promise now carry the weight of bills, breaches, and bottlenecks as organizations realize that rapid adoption without matching governance quietly trades short-term gains for long-term costs. As enterprise IT outlays swell toward the $6.15 trillion mark cited by industry forecasts, decision-makers are recalibrating
Cranes swing above Klang Valley skylines while spreadsheets, paper forms, and siloed apps still decide whether families can get keys on time, a paradox Malaysia’s largest developer is racing to resolve. The stakes are systemic: property sets the tempo for construction, finance, and national housing priorities, yet the data that binds them remains
Vernon Yai has spent his career safeguarding data and reshaping how organizations govern it, and in 2019 he stepped into a CIDO role at Malaysia’s largest property developer to turn that rigor into real-world outcomes. In this conversation, he reflects on moving from land and bricks to code and models, the stubborn analog gaps in inspections and
An unauthenticated terminal endpoint in a popular open-source notebook platform turned routine patch notes into a live breach vector in less than half a day, proving how disclosure alone can fuel immediate, at-scale abuse by operators who know exactly where to look and what to take. The case centered on Marimo and CVE-2026-39987, a CVSS 9.3