Lee Sun-woong, CEO of Cloudike: For Public Institutions Adopting AI, Data Environment Design Is as Critical as Model Selection
In an interview with ZDNet Korea, Lee Sun-woong, CEO of Cloudike, emphasized that for public institutions and high-security organizations such as financial and healthcare sectors introducing generative AI, designing the data environment is as important as model selection but often overlooked. He clarified that CSAP certification covers only the cloud service itself and does not automatically guarantee the security of the entire AI system; he advised organizations to first define business scenarios and document permissions, then conduct small-scale validation in controlled environments before gradually expanding.
Many enterprises wish to use AI to process internal documents, yet they often overlook a critical issue as vital as model selection: where exactly is the data stored, where is it processed, and who has access? In an interview with ZDNet Korea, Lee Sun-woong, CEO of the Korean enterprise cloud SaaS company Cloudike, identified this factor as one of the primary bottlenecks preventing public institutions from adopting generative AI.
By 'data location,' he does not merely refer to which server room houses the hardware. In his framework, this question encompasses where documents are processed, who has access rights, and where Q&A records are ultimately stored. He argues that the requirements for using public information differ significantly from those for processing sensitive internal documents. Organizations with high security standards must first distinguish which data can be used in which services before considering model performance comparisons.
For institutions unable to export data to external environments, he proposes an alternative: running AI within the environment where the data resides—deploying models on intranets or dedicated infrastructure controlled by the institution to complete document retrieval and summarization within that setting. However, he notes that simply installing the model inside the intranet is insufficient: every step, including text extraction, search indexing, Q&A log recording, and any connectivity features that might send data to external services, must be individually verified.