Việt Nam already has a Data Law (Luật Dữ liệu, No. 60/2024/QH15), a Personal Data Protection Law (Luật Bảo vệ dữ liệu cá nhân, No. 91/2025/QH15) and a Cybersecurity Law (Luật An ninh mạng, No. 116/2025/QH15). This afternoon the National Assembly added a fourth: a law about the security of data itself, regardless of whether it is personal, where it is stored or who owns it.
The Law on Data Security (Luật An ninh dữ liệu) passed on the afternoon of 20 November 2026, at the Second Session of the 16th National Assembly. 468 of 474 deputies voting were in favour, equal to 93.79% of all deputies. Before the vote, the Minister of Public Security, General Lương Tam Quang, presented the drafting agency’s report on how deputies’ comments had been absorbed. The law has 6 chapters and 28 articles and takes effect on 1 July 2027, except khoản 2 Điều 27, a transition clause for information systems that were already in operation before that date. The law has no number yet; numbers are assigned when the President promulgates it.
Who it covers
The scope is wide. Beyond Vietnamese agencies, organisations and individuals, the law applies to foreign organisations and individuals in Việt Nam, and also to foreign organisations and individuals outside Việt Nam when they process data under Vietnamese jurisdiction or infringe Việt Nam’s data security. That is the same extraterritorial pattern as the personal data law. A foreign cloud or AI provider that handles Vietnamese data cannot assume the law stops at the border.
Five risk levels, graded by the data controller
The core of the law is Điều 9, which grades data into five risk levels according to the harm a breach could cause:
- Level 1: no harm, or negligible harm, to the lawful rights and interests of agencies, organisations or individuals.
- Level 2: could disrupt the normal operation of an agency or organisation, or harm the lawful rights and interests of organisations or individuals.
- Level 3: could seriously or very seriously harm those rights and interests, harm social order and safety or the public interest, or harm national security.
- Level 4: could very seriously harm social order and safety or the public interest, or seriously harm national security.
- Level 5: could very seriously harm national security.
The data controller (chủ quản dữ liệu) classifies its own data and applies protection in proportion. For levels 1 and 2 this is mainly self-protection. From level 3 upward, risk-impact assessments and data security audits become much stricter. Data at levels 4 and 5 must be audited, and the audit report sent to the competent specialised agency. The State says its main tool will be after-the-fact inspection (hậu kiểm). Prior approval (tiền kiểm) is kept only for high-risk data and systems.
Two drafting choices matter in practice. First, a system that holds data at several levels must meet the requirements of the highest level it holds. Second, the minister said the risk level is a basis for choosing protective measures. It does not replace the separate “core data” and “important data” categories under the Data Law. A company may therefore have to run two classification exercises side by side. Deliberately grading data lower than it should be is explicitly prohibited.
Who appraises what
For appraisal (thẩm định) of information systems, the Ministry of Public Security handles systems that store or process level 4 and 5 data nationwide. The Ministry of National Defence handles military and defence data, and the Government Cipher Committee (Ban Cơ yếu Chính phủ) handles its own systems. Civil and commercial systems run by defence-ministry enterprises are appraised by Public Security in coordination with Defence. The stated principle is “one task, one lead agency, one procedure, one result recognised by all”, with no appraisal or inspection of the same content twice.
To cut compliance costs, the law adopts “one dossier, one focal point” (một hồ sơ, một đầu mối). A data controller may file one integrated dossier covering the assessments required under the Data Law, this law and the personal data protection law, and results of assessments, audits and certifications are to be shared and recognised across agencies. If it works as described, that is the most practical change for businesses, which until now have faced separate filings under overlapping regimes.
Security by design, cloud providers and outsourcing
Data security must be built in from the design stage and maintained across the whole data lifecycle: creation, collection, storage, processing, use, transmission, sharing, deletion and destruction.
The law gives telecom, Internet, data-centre and cloud providers responsibilities limited to the technical scope of the service they control and to the split of responsibility agreed in their customer contracts. Outsourcing does not move accountability. A data controller that hires a processor remains responsible for its own obligations. The processor must stay within the agreed scope and purpose and, when the contract ends, return or destroy all the data without keeping copies, unless another law requires otherwise.
AI: data poisoning and training restrictions
The law has a dedicated set of provisions on new technologies and AI. It defines data poisoning (đầu độc dữ liệu) as deliberately inserting false, forged or untrue data into a database or training dataset to distort or manipulate the output of an algorithm, AI model or information system. Data poisoning and the use of malicious data are banned. Controllers must monitor, classify and remove forged, distorted, malicious or malware-laden data to keep training pipelines intact.
Using level-3-or-higher defence and security data to train an AI model requires approval from a competent authority. Unlawfully using such data, or data containing state secrets, for training is prohibited. Derived data, meaning outputs generated from source data, must also be risk-graded and protected. The law also bans using data, algorithms and AI systems to manipulate information in ways that infringe national security or social order.
Incidents and emergency measures
Controllers must monitor, detect, give early warning of and respond to incidents according to the data’s risk level. Concealing a data security incident is prohibited. Where an incident could directly affect the rights and interests of organisations or individuals, the controller must notify them of the nature of the incident, the kinds of data affected and the steps they can take to protect themselves.
The law also lists emergency technical measures: freezing data; disabling access by specific accounts, devices or connections; suspending data flows; and suspending part or all of an information system, service or model that has been compromised or poisoned. Their use must have a legal basis and a defined scope and duration. Those affected may petition, complain, sue and claim compensation.
Security cryptography
The draft’s “security cryptography” (mật mã an ninh) drew questions about overlap with the Cipher Committee. The minister said it is an additional, independent technical layer and does not replace cipher cryptography. For now it is used only inside the Public Security sector. For data that is not a state secret, using it is entirely voluntary.
What businesses should do now
Just over seven months is not long to classify every dataset. Practical first steps:
- Inventory datasets and systems, and draft a provisional level 1–5 grading alongside your Data Law core/important-data mapping.
- Identify any system that might hold level 4 or 5 data. Those systems face audits, reporting and possible appraisal by the Ministry of Public Security.
- Review processor and cloud contracts for scope, end-of-contract deletion and the split of security responsibilities.
- If you train or fine-tune models, document data provenance and filtering, which is now a legal control rather than only good practice.
- Add individual notification to your incident-response plan.
Open questions
Much depends on implementing decrees not yet drafted in public: the detailed criteria for each risk level, audit standards and who may perform audits, how the integrated single dossier will actually be filed, and penalty levels. The transition rule in khoản 2 Điều 27 for systems already running before 1 July 2027 has not been published in detail. Until the full text is released, this post relies on the National Assembly briefing as reported by the press.
Sources
- Quốc hội chính thức thông qua Luật An ninh dữ liệu — Nhân Dân
- Quốc hội thông qua Luật An ninh dữ liệu, có hiệu lực từ ngày 1/7/2027 — Báo Công Thương
- Luật An ninh dữ liệu: Phân loại theo 5 cấp độ rủi ro, siết chặt bảo vệ dữ liệu — Công luận
- Nghiêm cấm chiếm đoạt, mua bán, thu thập, xóa hoặc phá hủy dữ liệu trái phép — Đại Đoàn Kết
- Quốc hội thông qua Luật Định danh và xác thực điện tử, Luật An ninh dữ liệu — LuatVietnam
This post is general information, not legal advice.