MLPS 2.0 for Fire IoT | Wanlin Fire

Wanlin briefing · Updated

Building a Compliance File: Records and Policies for community service operators

In one sentence: Running a fire IoT platform in China means running it inside the Multi-Level Protection Scheme - the working details, in one page.

At a glance

Legal anchor
Article 21 of the Cybersecurity Law establishes multi-level protection (MLPS); fire IoT is treated within the critical-information-infrastructure policy net
Typical grades
Level 2 (guidance protection) fits most enterprise fire IoT platforms; Level 3 (supervision) fits city-level monitoring platforms and critical infrastructure, with mandatory annual testing
Timeline
About 2-3 months for Level 2, 3-6 months for Level 3, from asset inventory to certificate
Order matters
Grade and file with the public security bureau before buying equipment; remediation follows the filed grade, then assessment

Why fire IoT sits inside the compliance net

The regulation rewards operators who treat security as record-keeping discipline, not as a shopping list of appliances.

Article 21 of the Cybersecurity Law makes multi-level protection a baseline obligation for network operators, and fire IoT - alarm signals, device telemetry, location data - is treated within the critical-information-infrastructure policy net. Public-security campaigns in 2025 have turned enforcement from occasional to routine.

The five levels - and where fire platforms land

Protection levels under MLPS
LevelNameApplies to
Level 3Supervision protectionCity-level monitoring platforms and critical information infrastructure; annual assessment is mandatory
Level 4Forced protectionNational core systems; essentially out of scope for fire platforms
Level 5Dedicated protectionState-level special systems; not applicable to fire platforms
Level 1Self-protectionSmall internal systems; the operator protects on its own, no filing ritual to speak of
Level 2Guidance protectionMost enterprise platforms - including typical fire IoT and demonstration-site platforms; filing required, re-test at least every two years

Practical rule of thumb: enterprise fire IoT platforms grade at Level 2; anything a city relies on for supervision grades at Level 3 with annual assessment.

The seven-step route to a certificate

From asset inventory to operations
#StepWhat happens
6AssessmentA licensed testing institution assesses the object; the report supports the certificate
7OperationsRun the controls: monitoring, patching, records, and re-testing on the statutory cycle
1Asset inventoryList systems, data flows, device types and network boundaries; split objects by business boundary rather than bundling everything into one grade
2Self-gradingAssign Level 2 or Level 3 per object based on the harm a breach would cause
3Expert reviewA review panel confirms the grading conclusion
4Public-security filingFile the grade with the competent public security bureau within the statutory window
5RemediationClose gaps against the basic requirements: technical controls plus management system, roles, records and drills

About 2-3 months for Level 2 and 3-6 months for Level 3, assuming remediation is scoped early. The order cannot be reversed: grade and file first, buy and remediate after.

What assessors check

Technical checks

Network boundary controls and intrusion detection; host and application vulnerabilities, patches and weak credentials; data encryption, backup and permissions; sensing-device identity authentication and default-password cleanup; log audit coverage

Management checks

Written security policies; defined roles and responsibilities; personnel management; day-to-day operation records; incident emergency plans and drills - the soft items that fail most first-time assessments

Three expansion scopes for fire IoT

Industrial-control expansion

Segregation of control and office networks; whitelisting and audit on control devices; one-way, controlled maintenance access; availability-first protection strategy - relevant when building automation or electrical control systems link in

IoT expansion

Perception-node identity and access authentication; sensing-data integrity; node location and anti-tamper protection; gateway-side protocol and data validation

Cloud expansion

Responsibility boundary between platform and tenant; virtualization isolation and image security; review of the cloud provider’s security capability; data retention and exit arrangements

Staying compliant after the certificate

Five failures to avoid

How Wanlin fits

Frequently asked questions

How long does certification take?

Plan roughly 2-3 months for Level 2 and 3-6 months for Level 3 from asset inventory through assessment, assuming remediation is scoped early.

What do assessors check first?

Both tracks matter: technical controls (boundary, host, application, data, devices, logs) and management soft items (policies, roles, records, drills). First-time failures cluster in the management track.

Do cloud-hosted platforms have extra requirements?

Yes - the cloud expansion scope adds the platform-tenant responsibility split, virtualization isolation, image security, provider capability review and data exit arrangements.

How often must the certificate be renewed?

There is no one-time certificate in practice: Level 2 re-tests at least every two years and Level 3 annually; major changes trigger re-assessment regardless of cycle.

Does a fire IoT platform legally need MLPS?

Yes. Article 21 of the Cybersecurity Law establishes multi-level protection as a baseline obligation for network operators, and fire IoT is treated within the critical-information-infrastructure policy net. 2025 public-security campaigns have raised enforcement pressure.

Next step

Start with the asset inventory and the grading conclusion - the two documents every later step depends on. Everything else is sequenced work, not mystery.

Scope disclosure: this page is an educational briefing based on a published regulatory framework ; figures are quoted from those sources and must be verified against the current official texts. No MLPS grade, certification or award status is claimed for any Wanlin product or platform; certificates must be confirmed for the exact model before any bid or award. Contact: wanlinfirecontrol@163.com · 16710807777.

Evidence and references to request

How long does certification take?

Plan roughly 2-3 months for Level 2 and 3-6 months for Level 3 from asset inventory through assessment, assuming remediation is scoped early.

What do assessors check first?

Both tracks matter: technical controls (boundary, host, application, data, devices, logs) and management soft items (policies, roles, records, drills). First-time failures cluster in the management track.

Do cloud-hosted platforms have extra requirements?

Yes - the cloud expansion scope adds the platform-tenant responsibility split, virtualization isolation, image security, provider capability review and data exit arrangements.

More on this site: the topic guides index collects every guide, including the aging-community renovation program, the data production framework, SDOS/SPP asset management and the capability index.