DPO Radio

AesirX ComplianceOne | Decree 331 Vietnam Five-Level Classification

Overview Image

Decree 331/2026/NĐ-CP: Scope and Current Status

Decree 331/2026/NĐ-CP is final law, not a proposal. The Government issued it on 19 August 2026 and it took effect the same day. It has 40 articles in six chapters, and the Ministry of Public Security is the lead authority.

The decree sets out how information systems are classified and protected:

  • The criteria for levels 1 through 5.
  • The level-determination dossier, and how it is appraised and approved.
  • The criteria for systems critical to national security.
  • The protection duties at each level, including separation rules for cloud and data-centre hosting.
  • The incident-reporting ladder and the annual reporting cycle.

The level criteria include hard numbers. Between levels 2 and 3, the thresholds are 100,000 data subjects for basic personal data and 10,000 for sensitive personal data. Industrial control systems are graded on a construction-grade ladder. A threshold is one input to a determination, not a formula: the level is set through the decree's appraisal and approval procedure.

Transition from Decree 85/2016. The signed text of Decree 331 contains no repeal of Decree 85/2016/NĐ-CP. Article 39 sets two steps for systems already under investment or construction before 1 July 2026:

  • Complete level appraisal and approval under Decree 85/2016 within 6 months of the Law's effective date.
  • Then meet Decree 331's per-level conditions within 12 months.

The two routes stay separate, so every determination must name the instrument it was made under. Under Article 39(2), references to ‘network information security’ or ‘information system safety’ in standards and technical regulations are read as ‘cybersecurity’ within Decree 331. That change of wording does not make every legacy control or item of evidence sufficient for the new requirements.

Decree 331 replaced the priority consultation draft on the same subject. If your organization prepared readiness work against the draft, ComplianceOne keeps that history as a legacy record so it can be compared with the enacted decree.

Overview Image

How Decree 331 Relates to the Vietnam Cybersecurity Law 2025

Decree 331 is the classification decree the Cybersecurity Law called for. Cybersecurity Law 116/2025/QH15 grades information systems into five levels, and left the criteria, competence and procedure to a Government decree. Decree 331 details Articles 8(2), 9(5), 10(6) and 12(5) of the Law.

Decree 85/2016 still matters during the transition, and its five levels are a different scale. The transition rules are set out under Scope and Current Status above.

Fines are set in a different decree. Decree 331 sets no fines of its own. The sanctions for breaching its duties are in Decree 330/2026/NĐ-CP. Quote any figure from Decree 330 together with its rule on what individuals and organizations pay.

Technical Provisions and Compliance Obligations

ProvisionWhat It EstablishesOperational Implication
Article 7, Article 8Identify and scope each system by how it actually operates, without splitting or merging systems for form's sakeRecord a defensible operational reason for each scoping choice
Article 9Classify the information a system processes into four secrecy classes, and the system itself into the stated kindsClassify the information first, then the system
Article 10Risk assessment in five prescribed cases, with seven minimum contentsA risk assessment is triggered by an event and has a set list of contents; it is not a free-form review
Articles 11–15Criteria for levels 1–5, including thresholds of 100,000 data subjects (basic personal data) and 10,000 (sensitive personal data) between levels 2 and 3Data-subject counts become classification evidence
Article 16, Article 17Criteria for systems critical to national security. Every level-5 system is automatically on the critical listA level-5 determination brings the critical-system regime with it
Articles 18–24The level-proposal dossier, where it goes for each proposed level, and which authority appraises and approves itThe statutory clocks depend on the dossier's quality; the proposed level decides which authority handles it
Articles 26–27Inspection and assessment of systems outside the national-security-critical list: notice, inspection records, results and evidence of corrective actionKeep the basis, scope, minutes, result and remediation record of each inspection
Article 28, Article 30Condition assessment before operation, where a result that does not qualify blocks go-live; and the internal cybersecurity Regulation, which must be issued before dossier approvalGo-live is gated, and the internal Regulation is a prerequisite, not an afterthought
Article 31(2)(c)Internal assessments must be independent of the operating unit and use the competent authority's forms, criteria and methods. Specified cases must use qualified professional or public-service organizationsTreat assessor independence and competence as evidence to keep, not assumptions
Article 30(8)–(9)Cloud and data-centre separation: logical for levels 3–4, physical for level 5 and critical systemsYour hosting architecture is a compliance fact at each level
Article 31The incident ladder: report immediately on signs of a national-security impact; send an initial notice within 24 hours for a serious incident; report cause, scope and remediation within 72 hours. The head of the system owner is accountableKeep timestamped evidence for each step
Article 35, Article 36The annual reporting cycle, with dates and twelve required contents set by the decreeYour reporting calendar is fixed by the decree, not by internal policy

ObligationTimelineReference
Decree takes effect19 August 2026Article 38
Authority responds to an incomplete level-proposal dossier5 working daysArticle 23(2)
Appraisal of a level-3 dossier15 working daysArticle 23(3)(a)
Appraisal of a level-4 or level-5 dossier25 working daysArticle 23(3)(b)
Processing of the level-approval dossier7 working daysArticle 24(2)
Report incident cause, scope and remediation72 hours from detectionArticle 31(2)(d)
Initial notice of a serious incident24 hours from detectionArticle 31(2)(d)
Report incidents showing signs of a national-security impact or serious disruptionImmediately on detectionArticle 31(2)(d)
Annual report data window15 December to 14 DecemberArticle 35(3)
Annual report to the system ownerBefore 20 December each yearArticle 35(4)(a)
Annual report to the Ministry of Public SecurityBefore 25 December each yearArticle 35(4)(b)
Ministry publishes the categorized system listBefore 15 January each yearArticle 9(2)(e)
Transitional appraisal under Decree 85/20166 months from the Law's effective dateArticle 39(1)
Transitional per-level compliance under Decree 33112 months from the Law's effective dateArticle 39(1)

The decree sets no appraisal time limit for level-1 and level-2 dossiers, which the owner's own specialized unit handles. ComplianceOne leaves that deadline empty rather than inventing a number.

Forms and Data Requirements

The decree's appendix sets eight official forms, Form No. 01 (Mẫu số 01) through Form No. 08 (Mẫu số 08). They cover the level-proposal dossier, the appraisal and approval records and the annual report. ComplianceOne includes all eight as published, with their titles and section structure. Any other template it provides for Decree 331 is labelled as a preparation template, not an official form.

Overview Image

How ComplianceOne Supports Decree 331 Compliance

You get the five levels with their criteria taken from the signed articles. Each data-subject threshold sits inside the criterion it belongs to. Every level carries a note that the decree's appraisal and approval procedure sets it, so a level is a defended conclusion rather than a dropdown choice.

Procedure deadlines are tracked with their citations: the 5, 15, 25 and 7 working-day windows, the three steps of the incident ladder and the four annual reporting dates.

The two five-level scales stay separate. A determination made under Decree 85/2016 keeps that label through the transition, next to the levels Decree 331 defines. Nothing silently converts one scale into the other.

Incident, assessment and reporting evidence links to the system record, its approved level and its hosting-separation facts. That is the shape of the questions an inspection under Decree 331 asks.

Built for Defensible Level Determinations

A level is only as strong as its dossier. The criteria, the counts and the appraisal opinion stay attached to the determination, so you can defend it when it is re-examined.

Both five-level scales keep their identity. The transition runs on Decree 85/2016 while new duties run on Decree 331, and no record treats the two scales as interchangeable.

Every deadline cites its article. The working-day windows, the incident steps and the annual dates come from the decree, not from house conventions.

Where the decree sets no limit, ComplianceOne shows none. The missing deadline for level-1 and level-2 dossiers is not papered over with an invented number.

Related Modules

Program GovernanceProgram Governance

Assigns level-determination, dossier and transition work with dated obligations

Explore Program Governance

Risk AssessmentRisk Assessment

Runs the five trigger cases and records the seven minimum contents

Explore Risk Assessment

Data ClassificationData Classification

Keeps the information-classification evidence the level criteria depend on

Explore Data Classification

Incident ResponseIncident Response

Runs the immediate, 24-hour and 72-hour reporting steps with timestamps

Explore Incident Response

Monitoring ProgramsMonitoring Programs

Tracks the annual cycle, re-determination triggers and recurring reviews

Explore Monitoring Programs

Audit TrailAudit Trail

 Preserves the history of each determination, appraisal, approval and report

 
Explore Audit Trail

Compliance Readiness Checklist

Organizations operating under Decree 331 should confirm:

Every information system is identified and scoped by how it actually operates, with the reasoning recorded.

Data-subject counts for basic and sensitive personal data are known wherever the level 2/3 thresholds may apply.

Level-proposal dossiers are complete before filing, because the statutory clocks run from a valid dossier.

The internal cybersecurity Regulation is issued before dossier approval, and the pre-operation assessment gate is in the project plan.

Inspection and assessment records cover scope, minutes, results, assessor independence or eligibility, corrective actions and completion evidence, as Articles 26–27 and Article 31(2)(c) require.

Hosting separation matches the level: logical for levels 3–4, physical for level 5 and critical systems.

Incident reporting can meet all three steps (immediately, within 24 hours, within 72 hours) with timestamped evidence.

The annual dates are in the calendar: data cut-off 14 December, owner report before 20 December, ministry report before 25 December.

Systems under investment or construction before 1 July 2026 are on the 6-month and 12-month transitional tracks.

Every determination names the instrument it was made under: Decree 331 or Decree 85/2016.

Level-5 candidates are reviewed against the critical-system criteria, since level 5 means automatic listing.

Background Image

See Decree 331 Compliance in Action

See how ComplianceOne handles level criteria, dossier deadlines, the incident ladder and the evidence an appraisal asks for.

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

Yes. Decree 331/2026/NĐ-CP was issued on 19 August 2026 and took effect the same day under Article 38. Its level criteria, procedures and duties are final law. The Article 39 transition governs systems that predate the Cybersecurity Law.

Not expressly. The signed text of Decree 331 contains no repeal of Decree 85/2016, and Article 39 expressly runs the appraisal of specified pre-existing systems under it. Under Article 57(2) of Law 64/2025/QH15, as amended by Law 87/2025/QH15, an implementing decree lapses with the law it implements unless it is officially announced as continuing, in whole or in part. Treat Decree 85/2016 as a qualified transitional reference while Decree 331's duties apply, and name the instrument on each determination.

No. Each threshold is one branch of one criterion between levels 2 and 3 of Decree 331. The level itself is set through the decree's dossier, appraisal and approval procedure. Other criteria, including the construction-grade ladder for industrial control systems, can drive the outcome.

There are three steps. Report immediately on detection if an incident shows signs of a national-security impact or serious disruption. Send an initial notice within 24 hours for a serious incident. Report the cause, scope and remediation within 72 hours of detection. Systems managed by the Ministry of National Defence report to its counterpart agency.

Systems under investment or construction before 1 July 2026 complete level appraisal and approval under Decree 85/2016 within 6 months of the Law's effective date. They then meet Decree 331's per-level conditions, standards and measures within 12 months of that date.

Next Steps

Icon Image

Start a Compliance Pilot

Test level determination, dossier preparation, incident-deadline evidence and the annual cycle against the signed decree.

Icon Image

Discuss Your Compliance Needs

Review your system inventory, your proposed levels, your hosting separation and your exposure to the transitional deadlines.