You are using an outdated browser and your browsing experience will not be optimal. Please update to the latest version of Microsoft Edge, Google Chrome or Mozilla Firefox. Install Microsoft Edge

April 15, 2020

Vietnam Issues Guidelines on Cloud Computing for E-Government Deployment

Subscribe to Updates

On April 3, 2020, Vietnam’s Ministry of Information and Communication (MIC) issued Official Letter No. 1145/BTTTT-CATTT to provide guidelines on a set of technical criteria and specifications for cloud computing solutions for e-government deployment (the “Guidelines”).

State agencies and organizations will rely on these Guidelines to assess and select solutions or lease cloud computing services for the development of e-government. Private-sector entities are also encouraged to refer to these Guidelines when setting up and deploying their own cloud computing platform solutions.

The set of technical criteria and specifications include two groups of criteria: Group 1 – technical criteria and specifications, and Group 2 – criteria for information security.

Group 1 includes criteria, specifications, and features related to: (1) virtual machines, (2) storage devices, (3) networks and software-defined networking, (4) physical machines, (5) administration and operation, and (6) integration and other relevant requirements.

Group 2 includes requirements related to: (1) basic requirements on information security features and (2) requirements for setting up security configurations for cloud computing infrastructure.

These two groups are specified in detail in the Guidelines and its annexes. Annex 1 related to Group 1 sets out the minimum technical criteria and specifications for cloud computing infrastructure, and sets out a table to describe features, criteria, and specifications for each specific feature. If a feature has only one criterion or technical specification, a cloud computing solution is evaluated as “passing” when the solution provides that feature and “not passing” if the solution does not provide that feature. If a feature has many different criteria and specifications, that feature is evaluated as “passing” when all criteria and technical specifications are met or “not passing” when at least one of the criteria or technical specifications is not achieved. Similarly, Annex 2 related to Group 2 sets out the minimum technical criteria and specifications for information security of cloud computing infrastructure.

The Guidelines also provide the concept of cloud computing (definition and basic characteristics of cloud computing), the classification of methods for deploying cloud computing (public cloud, private cloud, hybrid cloud, and multi-cloud) and the classification of cloud computing service provision models: IaaS (Infrastructure as a Service) – suitable for private cloud deployment; PaaS (Platform as a Service) – suitable for public cloud deployment; and SaaS (Software as a Service) suitable for public cloud.

Furthermore, the Guidelines provide two options for deploying a cloud computing platform: self-deployment, administration, and operation; or leasing professional cloud computing services from other companies.

With regard to the option of self-deployment, administration, and operation, state agencies and organizations are required to have an experienced, capable team to build, administrate, operate, maintain, and ensure information security of the platform. Therefore, they are recommended to implement the second option of leasing professional cloud computing services. However, for certain information systems with specific requirements and which require system administrators to self-manage and operate, state agencies and organizations need to consider hiring professional enterprises to build cloud computing infrastructure. After the system is built, the professional enterprises will hand it over, transfer technology, and provide training and guidance on system administration and operation.

With the option of leasing professional cloud computing services, the MIC recommends that state agencies and organizations prioritize the selection of cloud computing service providers which meet technical criteria and specifications and are on the list announced by the MIC. Selected cloud computing service providers must comply with relevant laws and regulations on network information security, comply with stipulated technical standards, and fulfill technical criteria and specifications stipulated in these Guidelines.

For more information on the cloud computing technical criteria and specifications, please contact us at [email protected].

Related Professionals

Industries

Technology

Location

RELATED INSIGHTS​ 

August 11, 2026
On July 27, 2026, the State Bank of Vietnam (SBV) released a draft decree proposing amendments to Decree No. 52/2024/ND-CP dated May 15, 2024, on non-cash payments (Decree 52). The draft decree would amend 17 of Decree 52’s 38 articles, with several key changes directly affecting providers of intermediary payment service (IPS). The key proposed changes affecting IPS providers are outlined below. Streamlining IPS Licensing Procedures A central objective of the draft decree is to simplify regulatory procedures for IPS providers. Notably, it would significantly reduce IPS licensing documentation requirements by removing the need to submit enterprise registration certificates, investment registration certificates, and documents evidencing the qualifications of the legal representative and general director. Instead, the SBV would retrieve this information directly from national business registration and other specialized databases, requesting additional documents only where the relevant information cannot be verified electronically or is incomplete. The draft decree also removes the current limit of two rounds for dossier supplementation and shortens processing timelines for several IPS licensing procedures such as issuance, amendment, and reissuance of IPS licenses. The processing time for new IPS license applications would be thereby reduced from 90 to 60 working days. In addition, several continuing IPS business conditions would be removed. For example, IPS providers would no longer be required to maintain certain representations relating to corporate restructuring or the legality of contributed capital. Likewise, the IPS project plan (đề án) would become a one-time application document rather than an ongoing licensing condition. If retained in the final decree, this change could provide IPS providers with significantly greater flexibility to implement post-licensing technology upgrades, system integrations, and corporate restructuring transactions without needing to revisit the originally approved project plan. The draft decree also removes the requirement for the SBV to consult the Ministry of Public
Read More
August 10, 2026
Thailand has finalized its social media KYC (“know your customer”) rules under Notification of the Electronic Transactions Commission on Measures to Prevent Technological Crimes for Social Media Service Providers (No. 2), which was published in the Government Gazette on May 5, 2026, and will take effect on November 1, 2026. While an early draft of the notification proposed requiring social media platforms to arrange identification of every user account, the final notification is significantly more targeted, focusing on paid online advertising and advertiser identity verification. Though the regulatory initiative primarily aims to combat online fraud and technology-related crimes, it also has important consequences for intellectual property enforcement, because the verified platform records that will be generated under the new requirements can help IP rights holders to identify anonymous online infringers. Key Regulatory Mandates The notification requires social media service providers to verify the identity of advertisers before their paid advertisements are published and disseminated in Thailand through social media, regardless of whether the advertising fees come from the advertisers or third parties. Verification of an advertiser is valid for one year, after which verification would have to be performed again before the platform could publish additional paid advertisements from the advertiser. Permitted verification methods are specified under the notification. A platform may verify an advertiser by checking identity evidence and confirming the connection between the advertiser and that identity evidence, with the notification giving facial comparison against certain government-issued identity documents as an example. Alternatively, platforms may verify advertisers through a digital identity verification and authentication system with an identity-proofing assurance level not lower than the level prescribed by Thailand’s Electronic Transactions Commission. The notification further requires platforms to retain only the advertiser’s information necessary to identify the advertiser, beginning from the start of the advertising activity and for
Read More
August 10, 2026
On July 31, 2026, Thailand’s Big Data Institute (BDI) launched a public consultation on the principles of a proposed new data-sharing law, with comments accepted until August 31, 2026. If enacted, the law would establish Thailand’s first comprehensive framework for government and private-sector data sharing, creating a systematic, secure, and transparent regime to support analytics, policymaking, research, and innovation. Central Data-Sharing Platform The draft law establishes a central system for data sharing, managed by the BDI. Government agencies would be required to connect to the BDI’s Data Integration and Intelligence Platform (also referred to as D2), in accordance with the BDI’s rules and procedures. Five Dimensions of Data Sharing The draft law covers five key types of data sharing between government (G), businesses (B), and consumers (C): G2B: Private organizations may request government data specifically for research and development purposes. The BDI will assess the applicant’s data governance, security, and privacy capabilities whether such measures meet prescribed standards before forwarding the request to the relevant government agency within 90 days. Any dispute may be escalated to a newly established Data-Sharing Promotion Committee for final determination. G2G: Government agencies may request data from other agencies through the central system. The data-holding agency must respond within 90 days, taking legality, necessity, proportionality, public interest, and personal data protection into account. Disputes may be referred to the Data-Sharing Promotion Committee for adjudication. B2G: In emergency situations involving public safety, economic security, or disaster response, the Minister of Digital Economy and Society may require private entities to provide data through the central data-sharing system. Government agencies must specify the data requested, demonstrate its necessity and expected benefits, and request only data reasonably available to the data holder. Requests for personal data must be limited to the minimum amount necessary. B2C: Royal decrees may
Read More
August 10, 2026
Thailand’s Office of the Personal Data Protection Committee (PDPC) recently released draft guidance on records of processing activities (ROPA) for personal data controllers and processors under the Personal Data Protection Act B.E. 2562 (2019) (PDPA). The draft guidance, which was presented to the public on July 7, 2026, addresses both controller records of collection, use, and disclosure of personal data and processor records of processing activities carried out on behalf of controllers. If implemented, the guidance will significantly expand organizational expectations for ROPA preparation, maintenance, and use across all sectors. Key Takeaways The draft guidance contains several important implications for organizations subject to the PDPA: ROPA reframed as a core accountability tool. The guidance elevates ROPA from an administrative record to a central accountability mechanism, connecting controller duties with recordkeeping obligations. ROPA as a source for privacy notices and governance documents. ROPA should serve as the primary source for privacy notices and align with consent management, retention schedules, DPIAs, incident response plans, and vendor contracts. Expanded scope across all activities. ROPA must cover all processing activities across the organization—including security, finance, HR, and external contractors—with correct controller or processor classification for each. Ongoing maintenance and auditability. ROPA must be updated for any change to systems, purposes, or processors, reviewed at least annually, and maintained with version control and a designated owner. Enhanced vendor, processor, and cross-border transfer requirements. Organizations must document all processors, external recipients, and cross-border transfers, specifying purposes, access scope, and destination countries. Linkage with risk assessment, DPIAs, and LIAs. ROPA should assign risk levels to each activity and identify when data protection impact assessments (DPIAs) or legitimate interests assessments (LIAs) are required, functioning as a risk-management tool. ROPA and data breach readiness. Incomplete ROPA can delay breach response and notification. Organizations should map data flows, vendors,
Read More