DPO Radio

Decree 53 Cybersecurity Implementation Vietnam

Overview Image

Decree 53/2022/ND-CP: Scope and Current Status

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:

  • Information systems important to national security. How a system is added to or removed from the national list, and the conditions its owner must meet (Articles 3–12).
  • Protection measures. The procedures for cybersecurity appraisal, condition assessment, monitoring, inspection, incident response, removal of unlawful information, collection of electronic data, and suspension of systems (Articles 13–22).
  • State agencies and political organizations. Network-use rules, security plans and incident response plans (Articles 23–25).
  • Data storage and local presence in Vietnam. Which data must be stored in Vietnam, by whom, and for how long (Articles 26–27).

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.

Legal status and transition

  • The parent law has ended. Article 44(2) of Law 116/2025/QH15 ended Law 24/2018/QH14 on 1 July 2026, the day Law 116 took effect.
  • A new general implementing decree is in force. Decree 333/2026/ND-CP details Law 116. It was issued on 19 August 2026 and took effect the same day (Article 30).
  • Decree 333 does not expressly repeal Decree 53. Its Article 31 keeps two kinds of dossier on Decree 53. Cybersecurity appraisal and condition-assessment dossiers validly received under Decree 53 before 19 August 2026, and not yet decided, are still decided under Decree 53.
  • The general rule on implementing decrees. When a law is replaced, the decree detailing it ceases to have effect with it, unless it is formally announced to continue. The announcement must be published in the electronic Official Gazette and the national legal database (Article 57(2) of Law 64/2025/QH15, as amended by Law 87/2025/QH15).

Confirm with qualified advisers how these rules apply to any Decree 53 matter you still hold.

Overview Image

How Decree 53 Relates to the Vietnam Cybersecurity Law 2025

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.

  • For the obligations that apply now, see the Vietnam Cybersecurity Law 2025 (Law 116/2025/QH15) compliance page.
  • For the procedures that replace Decree 53's in new work, see the Decree 333/2026 page.
  • For Law 24/2018 and the transition, see the Vietnam Cybersecurity Law 24/2018 page.

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.

Technical Provisions and Compliance Obligations

Decree 53 applied different duties to domestic and foreign enterprises. Your in-scope record should show which applied to you, and why.

QuestionWhat Decree 53 saysSource
Are you a domestic enterprise?A domestic enterprise stores the data listed in Article 26(1) in VietnamDecree 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 servicesDecree 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 takenDecree 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–17Decree 53, Articles 3–17

Data CategoryLocalization RequirementSource
Personal information of service users in VietnamStored in VietnamDecree 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 accountStored in VietnamDecree 53, Article 26(1)
Data on users' relationships: the friends and groups a user connects or interacts withStored in VietnamDecree 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 decisionDecree 53, Article 26(3) and 26(6)
Storage periodAt least 24 months, from receipt of the storage request until the request endsDecree 53, Article 27(1)

Cooperation TypeObligationTimelineSource
User informationGive user information to MPS's specialised cybersecurity force on written requestOn written request Law 24, Article 26(2)(a)
Content removalStop the sharing of, and delete, unlawful contentWithin 24 hours of the requestLaw 24, Article 26(2)(b); procedure in Decree 53, Article 19
System logsKeep system logs for investigating cybersecurity violationsAt least 12 monthsLaw 24, Article 26(2)(b); Decree 53, Article 27(3)
Service to offending usersStop providing service to those who post unlawful content, on requestOn requestLaw 24, Article 26(2)(c)
Other protection measuresCooperate when the authorities collect electronic data or suspend a systemPer the procedure in each articleDecree 53, Articles 20–22
Overview Image

How ComplianceOne Supports Decree 53 Compliance

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:

  • Authority Requests, for MPS requests linked to an incident. Each request moves through eight stages in a fixed order: received, verified, scope assessed, assembling, response packaged, legal review, submitted, closed. ComplianceOne refuses a move that skips a stage, so a request cannot jump from received to submitted.
  • Regulator inquiry cases in Monitoring Programs, for requests that arrive outside an incident. They run their own ordered sequence: receipt, triage, evidence gathering, response drafting, internal review, submission, follow-up and closure.

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.

Built for Cybersecurity Implementation Operations

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.

Built for In-Scope Determination and Localization Evidence

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.

Related Modules

Program GovernanceProgram Governance

Provides in-scope determination workflows and data localization compliance documentation.

Explore Program Governance

Incident ResponseIncident Response

Holds the Authority Requests register — eight ordered stages with a verification checklist, and the Disclosure Register that records each disclosure event.

Explore Incident Response

Monitoring ProgramsMonitoring Programs

Runs MPS inquiries that arrive outside an incident through their own ordered sequence, from receipt to closure, with tasks and linked programme evidence.

Explore Monitoring Programs

Data MappingData Mapping

Tracks data storage locations, in-scope data categories, and localization compliance status across all processing activities.

Explore Data Mapping

Vendor GovernanceVendor Governance

Supports third-party security assessment for vendors that store or process the data Decree 53 required to be kept in Vietnam.

Explore Vendor Governance

Audit TrailAudit Trail

Maintains tamper-evident records of in-scope determination actions, localization compliance reviews, and authority cooperation history.

Explore Audit Trail

Compliance Readiness Checklist

Organizations holding a Decree 53/2022/ND-CP compliance record should confirm:

The in-scope determination is complete and documented against Article 26 of Decree 53: domestic or foreign enterprise, listed sector, and the Article 26(3) conditions.

Any appraisal or condition-assessment dossier still pending under Decree 53 is tracked to its outcome under the Decree 333 Article 31 transition, not re-filed.

The in-scope determination is reviewed whenever your service catalog, data inventory or organizational structure changes materially.

Storage location is tracked in Data Mapping for every data type listed in Article 26(1).

Data subject to localization is confirmed as stored in Vietnam.

Where you are a foreign organization, your data storage compliance is documented.

Owners of any system on the list of information systems important to national security have evidence for the conditions in Articles 8–12.

Authority requests are recorded in the Authority Requests register, with the verification checklist completed and the legal-review stage reached before submission.

If your own policy requires management sign-off before an authority response goes out, that approval is evidenced outside the register. Its eight stages do not include one.

Every disclosure is entered in the Disclosure Register with its recipient, authority, date, type, channel and summary, linked to the incident or authority request it came from.

The legal basis for each disclosure, and the internal approval behind it, are recorded on the linked authority request. The Disclosure Register has no field for either.

Vendors handling in-scope data have been assessed against the localization and security requirements.

An evidence pack can be produced for the in-scope determination, localization compliance and authority cooperation history.

Background Image

See Decree 53 Compliance in Action

See how ComplianceOne handles Decree 53's in-scope determination, data localization and authority cooperation, using your own cybersecurity scenarios.

Demo Image
Ronni K. Gothard Christiansen

Ronni K. Gothard Christiansen - Technical Privacy Engineer & CEO

Technical Compliance Expert, 32+ Years Open Source Advocate, X-BoD Open Source Matters Inc.

Or contact via

ronni@aesirx.io+84 909 500 760

Frequently Asked Questions

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.

Next Steps

Icon Image

Start a Compliance Pilot

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

Icon Image

Discuss Your Compliance Needs

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