Comparison: MLPS 2.0 Level-3 Filing vs a Voluntary ISO 27001 Certificate for a Foreign Manufacturer’s China Data Room — What the Public Security Bureau Tests, the Annual Reassessment and Which One a Client Security Questionnaire Accepts

Date:

Share post:

Information date: 12 November 2026 — MLPS 2.0 is mandatory under Article 21 of the Cybersecurity Law. A system graded Level 3 must be filed with the local public security bureau, remediated, and assessed annually by a qualified testing institution. The bureau’s checks are concrete: boundary protection, identity authentication, access control, log retention of at least six months, intrusion prevention, backup, and a security management regime that is actually operated. ISO/IEC 27001 is voluntary — an ISMS certificate issued by a CNCA-approved body, on a three-year cycle with surveillance audits. It examines risk management and continual improvement, not individual firewall rules. Client questionnaires often accept either; public procurement and critical-information-infrastructure status accept only MLPS. If any system reaches Level 3, budget for MLPS — it is compulsory and non-negotiable. Pursue ISO 27001 only if a client contract or another market demands it, or if the ISMS work has independent value. If a system is neither critical infrastructure nor Level 3 but customers keep asking, answer with a Level-2 assessment report rather than an ISO certificate, and say plainly which question each document answers.

Verified facts and scope

MLPS 2.0 is mandatory under Article 21 of the Cybersecurity Law. A system graded Level 3 must be filed with the local public security bureau, remediated, and assessed annually by a qualified testing institution. The bureau’s checks are concrete: boundary protection, identity authentication, access control, log retention of at least six months, intrusion prevention, backup, and a security management regime that is actually operated. ISO/IEC 27001 is voluntary — an ISMS certificate issued by a CNCA-approved body, on a three-year cycle with surveillance audits. It examines risk management and continual improvement, not individual firewall rules. Client questionnaires often accept either; public procurement and critical-information-infrastructure status accept only MLPS.

Scope has to be fixed before the numbers mean anything: Establish which MLPS grade each system falls into — Level 2, Level 3 or higher — and whether any client questionnaire names a specific artefact. Confirm whether the system might be designated critical information infrastructure, and whether the data room sits onshore or offshore, since the grading applies to systems operated in China. Anything outside that set is a separate question with its own evidence requirement, and mixing the two is the most common way a workable plan turns into an unusable one.

For a decision on “Comparison: MLPS 2.0 Level-3 Filing vs a Voluntary ISO 27001 Certificate for a Foreign Manufacturer’s China Data Room — What the Public Security Bureau Tests, the Annual Reassessment and Which One a Client Security Questionnaire Accepts”, keep three layers apart: the published rule or statistic, the company’s own orders and process records, and the assumptions nobody has tested yet. The first layer defines the external conditions, the second proves what is true for this business, and the third is where the risk actually sits. Public material cannot substitute for a contract, a system log, a sample or a live test.

A practical way to test the scope is to ask which parts of “Comparison: MLPS 2.0 Level-3 Filing vs a Voluntary ISO 27001 Certificate for a Foreign Manufacturer’s China Data Room — What the Public Security Bureau Tests, the Annual Reassessment and Which One a Client Security Questionnaire Accepts” would still be true if the company changed supplier, entity or product line tomorrow. Items that survive that change belong to the rule layer and can be taken from official publications; items that do not survive belong to the operating layer and have to be rebuilt from invoices, warehouse records, customs entries or platform statements. Where Establish which MLPS grade each system falls into — Level 2, Level 3 or higher — and whether any client questionnaire names a specific artefact. Confirm whether the system might be designated critical information infrastructure, and whether the data room sits onshore or offshore, since the grading applies to systems operated in China, the two layers are frequently mistaken for each other, and an action plan built on the wrong one either over-complies or misses a deadline it never saw coming.

How the effect reaches operations

The two regimes answer different questions. MLPS asks whether a system meets a baseline the state defines and the police inspect, and the answer is binary per control item. ISO 27001 asks whether the organisation can be audited on how it manages and improves risk, and the answer is process-based. That is precisely why an ISO certificate cannot substitute for a filing, and a filing cannot satisfy a questionnaire that asks for a certified management system.

Recurring errors: assuming ISO 27001 removes the need to file; assuming an annual Level-3 assessment is the only scrutiny when the bureau can inspect between assessments; filing production systems while leaving the corporate file server ungraded; and submitting a beautifully written security policy that no one in the data room has ever executed.

Translated into an operating sequence, The two regimes answer different questions. MLPS asks whether a system meets a baseline the state defines and the police inspect, and the answer is binary per control item. ISO 27001 asks whether the organisation can be audited on how it manages and improves risk, and the answer is process-based. That is precisely why an ISO certificate cannot substitute for a filing, and a filing cannot satisfy a questionnaire that asks for a certified management system. That ordering matters: check applicability first, then the transmission step, and only then the size of the gap in cost or timing. When an intermediate step cannot be confirmed, the honest response is to narrow the scope of the conclusion rather than to substitute an industry average for the company’s own figures.

The cost of getting the order wrong is asymmetric. A team that checks applicability too late usually discovers it at the point where the shipment, the filing or the invoice can no longer be changed without penalty, and by then the only remaining lever is price. A team that checks early spends a few hours on questions that turn out to be irrelevant, which is cheap by comparison. On “Comparison: MLPS 2.0 Level-3 Filing vs a Voluntary ISO 27001 Certificate for a Foreign Manufacturer’s China Data Room — What the Public Security Bureau Tests, the Annual Reassessment and Which One a Client Security Questionnaire Accepts” the practical rule is therefore to spend the first hour on scope and the second on the numbers, never the other way round.

Decision

If any system reaches Level 3, budget for MLPS — it is compulsory and non-negotiable. Pursue ISO 27001 only if a client contract or another market demands it, or if the ISMS work has independent value. If a system is neither critical infrastructure nor Level 3 but customers keep asking, answer with a Level-2 assessment report rather than an ISO certificate, and say plainly which question each document answers.

The conditions should be written down so the decision can be re-run by someone else: Establish which MLPS grade each system falls into — Level 2, Level 3 or higher — and whether any client questionnaire names a specific artefact. Confirm whether the system might be designated critical information infrastructure, and whether the data room sits onshore or offshore, since the grading applies to systems operated in China. When those hold, proceed as described; when one is missing, close the gap first and decide afterwards. This comparison is general research, not cybersecurity, audit or legal advice. Grading decisions are made by the operator and confirmed by the bureau; engage a qualified testing institution before relying on any conclusion.

Two workstreams usually have to move in parallel. The compliance workstream closes the document side of “Comparison: MLPS 2.0 Level-3 Filing vs a Voluntary ISO 27001 Certificate for a Foreign Manufacturer’s China Data Room — What the Public Security Bureau Tests, the Annual Reassessment and Which One a Client Security Questionnaire Accepts” — registrations, confirmations, filings — while the commercial workstream protects the delivery date, the pricing already quoted and the customer commitments that were made on the earlier reading of the rules. Running them as one queue is how small documentation gaps become missed shipment dates: the commercial side waits for a certificate that could have been requested a week earlier. If any system reaches Level 3, budget for MLPS — it is compulsory and non-negotiable. Pursue ISO 27001 only if a client contract or another market demands it, or if the ISMS work has independent value. If a system is neither critical infrastructure nor Level 3 but customers keep asking, answer with a Level-2 assessment report rather than an ISO certificate, and say plainly which question each document answers. Set one owner per workstream and one shared status sheet, and treat a red item on either side as a reason to freeze only the affected order.

Implementation checklist

  1. Grade every system before the next security review meeting.
  2. File with the public security bureau before the first assessment, not after.
  3. Prove six-month log retention with a live query during the audit.
  4. Name one decision owner, one execution owner and one review date.
  5. Keep the source page, access date, entity and internal evidence.
  6. On any change, reopen only the affected judgement.

Evidence and review

Start with the smallest test that can change the answer: Grade every system before the next security review meeting. Pick one real entity or one representative case, write down the continue, watch and stop conditions in advance, and record the input version, the owner, the start time and the actual result. The first pass should only look at facts that move the decision; formatting preferences are not risk.

The second pass is completed by “File with the public security bureau before the first assessment, not after”, and someone who did not prepare the file should spot-check one piece of critical evidence. Recurring errors: assuming ISO 27001 removes the need to file; assuming an annual Level-3 assessment is the only scrutiny when the bureau can inspect between assessments; filing production systems while leaving the corporate file server ungraded; and submitting a beautifully written security policy that no one in the data room has ever executed. A single small deviation can be corrected in place; a repeated deviation, or one that touches a statutory duty or changes the economics, is what justifies pausing the affected part.

After “Prove six-month log retention with a live query during the audit”, compare the actual result with the baseline rather than with the impression of the team. If any system reaches Level 3, budget for MLPS — it is compulsory and non-negotiable. Pursue ISO 27001 only if a client contract or another market demands it, or if the ISMS work has independent value. If a system is neither critical infrastructure nor Level 3 but customers keep asking, answer with a Level-2 assessment report rather than an ISO certificate, and say plainly which question each document answers. When the arrangement is extended to more products, customers or processes, keep the same success test and one complete record per batch. If later information changes, update only the affected fields.

One last discipline keeps the file usable next quarter: write the closing note as if a colleague who has never spoken to the supplier has to act on it. That note states what was verified, on which date, against which source, and what remains open — on “Comparison: MLPS 2.0 Level-3 Filing vs a Voluntary ISO 27001 Certificate for a Foreign Manufacturer’s China Data Room — What the Public Security Bureau Tests, the Annual Reassessment and Which One a Client Security Questionnaire Accepts” it also states which of the three actions was actually finished and which was only scheduled. Teams that skip the closing note re-litigate the same question every month, and each round costs more than the documentation would have. This comparison is general research, not cybersecurity, audit or legal advice. Grading decisions are made by the operator and confirmed by the bureau; engage a qualified testing institution before relying on any conclusion.

Limits of the conclusion

This comparison is general research, not cybersecurity, audit or legal advice. Grading decisions are made by the operator and confirmed by the bureau; engage a qualified testing institution before relying on any conclusion.

The limits are structural rather than cautious wording. Public sources describe rules and market conditions; they do not observe “Comparison: MLPS 2.0 Level-3 Filing vs a Voluntary ISO 27001 Certificate for a Foreign Manufacturer’s China Data Room — What the Public Security Bureau Tests, the Annual Reassessment and Which One a Client Security Questionnaire Accepts” inside a specific company. Where the analysis quotes a second-hand interpretation, the original release has to remain reachable, and a figure that cannot be traced back does not enter the decision table. Where the point depends on Establish which MLPS grade each system falls into — Level 2, Level 3 or higher — and whether any client questionnaire names a specific artefact. Confirm whether the system might be designated critical information infrastructure, and whether the data room sits onshore or offshore, since the grading applies to systems operated in China, the conclusion is only as current as the last check of those conditions.

Primary sources

Related articles

News: After Han Zheng Meets the US Second-Track Dialogue Delegation, China Deal Teams Re-Paper the Sanctions and Unreliable-Entity Representations in the SPA — What...

Information date: 21 November 2026 — On 5 June 2025 People's Daily reported that Vice Premier Han Zheng met a US high-level second-track dialogue delegation, the kind of contact that shifts deal teams' assumptions about

News: After Liu Guozhong’s Anhui Harvest Inspection, a Foreign Grain-Dryer Maker Checks Its Machine Against the Subsidy Catalogue — the MARA Promotion Certificate, the...

Information date: 21 November 2026 — On 5 June 2025 People's Daily reported that Vice Premier Liu Guozhong, during an inspection in Anhui, called for securing the summer grain harvest and laying the foundation for autumn

FAQ: Does My Plant Really Qualify for the 15% Corporate Rate — Hainan, Lingang, the Greater Bay Area and the Western Encouraged-Catalogue Route Compared...

Information date: 21 November 2026 — The 15% rate is available through several distinct routes: the Hainan Free Trade Port for encouraged-industry enterprises, the Lingang new area of the Shanghai pilot free trade zone,

Comparison: Dispatch Labour vs Post-Service Outsourcing at a China Plant — the 10% Headcount Cap, the Same-Pay Rule, the Joint-Liability Exposure and Which of...

Information date: 21 November 2026 — Dispatch labour is capped at 10% of the employer's total headcount and is confined to temporary, auxiliary or substitute positions, while post-service outsourcing is not capped but is