DPO Radio

Decree 53/2022/ND-CP set out how Vietnam's Cybersecurity Law (Law 24/2018/QH14) worked in practice. The Government of Vietnam issued it on 15 August 2022, and it took effect on 1 October 2022 (Article 29). Most of its procedures run through the Ministry of Public Security (MPS).
It covered four areas:
Decree 53 does not grade information systems into security levels. Levels come from a different regime: Decree 85/2016/ND-CP, made under the Law on Network Information Security 86/2015/QH13.
Inspection readiness needs two kinds of evidence, kept current. Implementation evidence shows the measures work: technical configurations and security assessments. Governance evidence shows they are owned: policies, procedures and role assignments.
Confirm with qualified advisers how these rules apply to any Decree 53 matter you still hold.

Keep your Decree 53 record complete: it shows what you did while Law 24 applied, and it is where your Law 116 gap analysis starts. The Vietnam Cybersecurity Law 2025 (Law 116/2025/QH15) has governed since 1 July 2026. Decree 333/2026/ND-CP is its general implementing decree.
Decree 53 still matters in two ways. First, appraisal and condition-assessment dossiers already pending under it are decided under it, so track them to their outcome rather than re-filing. Second, it is the baseline your cybersecurity programme was built on since 2022. Comparing it with Law 116 and Decree 333 shows what has to change.
Decree 53 applied different duties to domestic and foreign enterprises. Your in-scope record should show which applied to you, and why.
| Question | What Decree 53 says | Source |
|---|---|---|
| Are you a domestic enterprise? | A domestic enterprise stores the data listed in Article 26(1) in Vietnam | Decree 53, Article 26(2) |
| Are you a foreign enterprise in a listed sector? | The listed sectors are: telecommunications; storing and sharing data in cyberspace; providing national or international domain names to users in Vietnam; e-commerce; online payment; payment intermediation; transport-connection services; social networks and social media; online games; and messaging, voice call, video call, email and online chat services | Decree 53, Article 26(3) |
| Did the storage and presence duty reach a foreign enterprise? | Only where its service was used to break cybersecurity law, MPS notified it and asked in writing for cooperation, and it did not comply, complied only in part, or obstructed the measures taken | Decree 53, Article 26(3) |
| Does one of your systems appear on the national list? | Owners of information systems important to national security must meet the conditions in Articles 8–12 and follow the procedures in Articles 13–17 | Decree 53, Articles 3–17 |
| Data Category | Localization Requirement | Source |
|---|---|---|
| Personal information of service users in Vietnam | Stored in Vietnam | Decree 53, Article 26(1) |
| Data created by service users in Vietnam: account name, time of use, credit card information, email address, IP address of the last login and logout, and the registered phone number linked to the account | Stored in Vietnam | Decree 53, Article 26(1) |
| Data on users' relationships: the friends and groups a user connects or interacts with | Stored in Vietnam | Decree 53, Article 26(1) |
| Foreign enterprise in scope under Article 26(3) | Stores the data above and sets up a branch or representative office in Vietnam, within 12 months of the Minister of Public Security's decision | Decree 53, Article 26(3) and 26(6) |
| Storage period | At least 24 months, from receipt of the storage request until the request ends | Decree 53, Article 27(1) |
| Cooperation Type | Obligation | Timeline | Source |
|---|---|---|---|
| User information | Give user information to MPS's specialised cybersecurity force on written request | On written request | Law 24, Article 26(2)(a) |
| Content removal | Stop the sharing of, and delete, unlawful content | Within 24 hours of the request | Law 24, Article 26(2)(b); procedure in Decree 53, Article 19 |
| System logs | Keep system logs for investigating cybersecurity violations | At least 12 months | Law 24, Article 26(2)(b); Decree 53, Article 27(3) |
| Service to offending users | Stop providing service to those who post unlawful content, on request | On request | Law 24, Article 26(2)(c) |
| Other protection measures | Cooperate when the authorities collect electronic data or suspend a system | Per the procedure in each article | Decree 53, Articles 20–22 |

ComplianceOne covers Decree 53's three main areas: deciding and documenting whether you are in scope, governing data localization, and cooperating with the authorities.
In-scope determination.
Program Governance records your in-scope determination: the criteria you applied, the evidence behind each one and the outcome. Evidence can include service catalog extracts, data inventory references and records of any national-list designation. When your services, users or data categories change, you reassess, and ComplianceOne tracks the change and compares it with the previous determination.
Data localization.
Data Mapping records where data is stored alongside your processing activities. You can tag activities with their storage location, flag any that store data outside Vietnam, and produce localization reports. Those reports list your in-scope data categories and confirm where each is stored. Kept current, this is your main evidence for MPS inspections and internal audit.
Authority cooperation runs on two registers with different jobs:
Verification is an item-by-item checklist on the request. ComplianceOne records what was ticked and by whom, but does not hold the next stage until every item is ticked. Neither register has a separate management-approval stage.
The Disclosure Register then records each disclosure: recipient, authority, date, disclosure type, channel and a summary of what was disclosed. Each entry links to the incident or authority request it came from, is never edited once added, and is audited.
The Disclosure Register has no field for the legal basis or the approval chain. Where you need to evidence those, record them on the linked authority request. Its verification checklist and request detail are free text and audited.
Third parties.
The Governance module supports security assessments of vendors that process or store in-scope data. You can check whether the storage and security duties that apply to you are met where a vendor holds the data.
An in-scope determination is a record, not a spreadsheet cell. It has an owner, the criteria applied, the evidence behind each criterion and the outcome reached. It is reviewed on a schedule rather than frozen on the day it was made. Every change is audited, so you can show an inspector what was decided and when.
Storage location sits where the rest of your inventory already is. The register entry holds its storage locations; the system record holds hosting location and data-residency country. Your localization view reads the inventory you maintain anyway, not a second one kept for the decree that goes stale within a quarter.
Authority cooperation uses two registers with different jobs, and neither adds a stage the process does not have. Requests linked to an incident follow the eight ordered stages of Authority Requests. Inquiries that arrive on their own run as regulator inquiry cases in Monitoring Programs. The Disclosure Register is append-only: what left the organization, to whom, on what date and by what channel.
Every step on both registers is audited with a person and a timestamp. Your authority-cooperation history comes from the record, not from anyone's memory.
Each criterion is answered separately, with its own evidence. You can defend the outcome criterion by criterion, not as a single verdict.
A reassessment is compared with the determination it replaces. A change in scope shows as a change, with its history, not as a fresh document.
Storage location sits on the processing activity itself. That is where anyone asking whether data left the country has to look anyway.
A request from an authority moves through receipt, legal review, response and closure as recorded steps, each showing who took it.
Duties that apply to your organization are checked against the third parties handling the same data, not stopped at your own boundary.
Provides in-scope determination workflows and data localization compliance documentation.
Explore Program GovernanceHolds the Authority Requests register — eight ordered stages with a verification checklist, and the Disclosure Register that records each disclosure event.
Explore Incident ResponseRuns MPS inquiries that arrive outside an incident through their own ordered sequence, from receipt to closure, with tasks and linked programme evidence.
Explore Monitoring ProgramsTracks data storage locations, in-scope data categories, and localization compliance status across all processing activities.
Explore Data MappingSupports third-party security assessment for vendors that store or process the data Decree 53 required to be kept in Vietnam.
Explore Vendor GovernanceMaintains tamper-evident records of in-scope determination actions, localization compliance reviews, and authority cooperation history.
Explore Audit TrailOrganizations holding a Decree 53/2022/ND-CP compliance record should confirm:
See how ComplianceOne handles Decree 53's in-scope determination, data localization and authority cooperation, using your own cybersecurity scenarios.

Three types, listed in Article 26(1). First, personal information of service users in Vietnam. Second, data those users create: account name, time of use, credit card information, email address, last login and logout IP address, and the registered phone number. Third, data on their relationships: the friends and groups they connect or interact with. Storage lasts at least 24 months under Article 27(1).
For pending dossiers, yes. Under Article 31 of Decree 333, appraisal and condition-assessment dossiers validly received under Decree 53 before 19 August 2026, and not yet decided, are still decided under Decree 53. New filings follow Decree 333. Decree 333 does not expressly repeal Decree 53, but it does not need to. Any other Decree 53 matter lapsed with Law 24 on 1 July 2026 and now falls under Law 116 and Decree 333. Take advice on how that applies to a specific matter.
Only in defined circumstances. A foreign enterprise in one of the sectors listed in Article 26(3) had to store the listed data in Vietnam and set up a branch or representative office there. That duty applied only where its service was used to break cybersecurity law and it did not comply with MPS's written request. The deadline was 12 months from the Minister of Public Security's decision.
They overlap for personal data. Personal information of service users in Vietnam is one of the data types Article 26(1) of Decree 53 required to be stored in Vietnam. The same data is subject to the PDPL's consent, rights, DPIA and breach notification requirements. ComplianceOne runs both in one workflow engine. Data Mapping tracks personal data records for the PDPL and storage locations for Decree 53.

Test Decree 53 workflows with your team: in-scope determination records, data localization tracking and MPS cooperation.

Talk to us about your Decree 53 record, localization evidence and how to structure your cybersecurity program for Law 116 and Decree 333.