DPO Radio

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 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:
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.

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.
| Provision | What It Establishes | Operational Implication |
|---|---|---|
| Article 7, Article 8 | Identify and scope each system by how it actually operates, without splitting or merging systems for form's sake | Record a defensible operational reason for each scoping choice |
| Article 9 | Classify the information a system processes into four secrecy classes, and the system itself into the stated kinds | Classify the information first, then the system |
| Article 10 | Risk assessment in five prescribed cases, with seven minimum contents | A risk assessment is triggered by an event and has a set list of contents; it is not a free-form review |
| Articles 11–15 | Criteria for levels 1–5, including thresholds of 100,000 data subjects (basic personal data) and 10,000 (sensitive personal data) between levels 2 and 3 | Data-subject counts become classification evidence |
| Article 16, Article 17 | Criteria for systems critical to national security. Every level-5 system is automatically on the critical list | A level-5 determination brings the critical-system regime with it |
| Articles 18–24 | The level-proposal dossier, where it goes for each proposed level, and which authority appraises and approves it | The statutory clocks depend on the dossier's quality; the proposed level decides which authority handles it |
| Articles 26–27 | Inspection and assessment of systems outside the national-security-critical list: notice, inspection records, results and evidence of corrective action | Keep the basis, scope, minutes, result and remediation record of each inspection |
| Article 28, Article 30 | Condition assessment before operation, where a result that does not qualify blocks go-live; and the internal cybersecurity Regulation, which must be issued before dossier approval | Go-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 organizations | Treat 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 systems | Your hosting architecture is a compliance fact at each level |
| Article 31 | The 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 accountable | Keep timestamped evidence for each step |
| Article 35, Article 36 | The annual reporting cycle, with dates and twelve required contents set by the decree | Your reporting calendar is fixed by the decree, not by internal policy |
| Obligation | Timeline | Reference |
|---|---|---|
| Decree takes effect | 19 August 2026 | Article 38 |
| Authority responds to an incomplete level-proposal dossier | 5 working days | Article 23(2) |
| Appraisal of a level-3 dossier | 15 working days | Article 23(3)(a) |
| Appraisal of a level-4 or level-5 dossier | 25 working days | Article 23(3)(b) |
| Processing of the level-approval dossier | 7 working days | Article 24(2) |
| Report incident cause, scope and remediation | 72 hours from detection | Article 31(2)(d) |
| Initial notice of a serious incident | 24 hours from detection | Article 31(2)(d) |
| Report incidents showing signs of a national-security impact or serious disruption | Immediately on detection | Article 31(2)(d) |
| Annual report data window | 15 December to 14 December | Article 35(3) |
| Annual report to the system owner | Before 20 December each year | Article 35(4)(a) |
| Annual report to the Ministry of Public Security | Before 25 December each year | Article 35(4)(b) |
| Ministry publishes the categorized system list | Before 15 January each year | Article 9(2)(e) |
| Transitional appraisal under Decree 85/2016 | 6 months from the Law's effective date | Article 39(1) |
| Transitional per-level compliance under Decree 331 | 12 months from the Law's effective date | Article 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.
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.

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.
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.
Assigns level-determination, dossier and transition work with dated obligations
Explore Program GovernanceRuns the five trigger cases and records the seven minimum contents
Explore Risk AssessmentKeeps the information-classification evidence the level criteria depend on
Explore Data ClassificationRuns the immediate, 24-hour and 72-hour reporting steps with timestamps
Explore Incident ResponseTracks the annual cycle, re-determination triggers and recurring reviews
Explore Monitoring ProgramsPreserves the history of each determination, appraisal, approval and report
Organizations operating under Decree 331 should confirm:
See how ComplianceOne handles level criteria, dossier deadlines, the incident ladder and the evidence an appraisal asks for.

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.

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

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