Direct Answer
A campus deploys an energy-monitoring platform and is asked to "pass the classified protection test" — should it be Level 2 or Level 3, and what must the device side do? Energy-monitoring platforms are normally filed at Level 2 (under GB/T 22239-2019); scenarios involving VPP dispatch, healthcare, data centers and other critical contexts rise to Level 3. The responsibility splits three ways: the FEXCloud side handles platform-level protection, the user side handles network boundaries, account permissions and the device access whitelist, and the edge ESX gateway is never exposed to the public network, going uplink through a tunnel. The sequence is classification, filing, assessment, remediation and annual testing.
A scenario: A campus deploys FEXCloud energy monitoring and asks "Level 2 or Level 3?" — decided by the business: campus consumption monitoring is a general system and files at Level 2; if VPP dispatch commands are involved, it rises to Level 3 — after filing, remediation proceeds by responsibility split and the assessment passes. The logic is classify first, then file, then assess — the level is set by the business scenario, and the responsibility is shared across the three sides.
1. What Classified Protection 2.0 Is: The GB/T 22239 Baseline
Classified protection 2.0 — cybersecurity classified protection: the national information-security baseline system; The standard — GB/T 22239-2019: baseline requirements for classified protection; How it lands — filing and assessment: classify and file, assess periodically, remediate continuously.
In one sentence: classified protection 2.0 is GB/T 22239 graded protection — filing plus assessment, and the platform must pass the grade.
An example: A campus platform is required to pass classified protection — classified and filed under GB/T 22239, assessed and remediated — running in compliance. The logic is that classified protection is an institutional requirement — classification, filing and assessment are each mandatory.
2. Level 2 vs Level 3: How the Boundary Is Decided
Level 2 applies — general systems: energy monitoring, consumption statistics and other routine business; Level 3 applies — critical systems: VPP dispatch, healthcare, data centers and critical infrastructure; The deciding basis — business impact: how much damage the compromised system causes to public interest and order; The signal to rise to Level 3 — dispatch commands: a platform able to command grid-influencing actions rises; The elasticity of the boundary — scenario-based: the same product may be classified differently in different deployments.
In one sentence: Level 2 manages the general, Level 3 manages the critical — whether the platform can "command the grid" decides the level.
An example: A campus pure-monitoring platform files at Level 2; a platform connected to VPP dispatch rises to Level 3. The logic is that monitoring is "watching" and dispatch is "controlling" — the ability to control raises the level.
3. The Three-Way Responsibility Split: Platform / User / Device
The platform side — FEXCloud: platform security itself, data protection and assessment cooperation; The user side — enterprise IT: network boundaries, account permissions and the access whitelist; The device side — edge gateways: device identity, firmware security and encrypted communication; The meaning of the split — each minding its own: classified protection does not require the platform to carry everything; The landing of the split — clear boundaries: all three sides remediate and keep their own records.
In one sentence: the split is platform manages platform, user manages boundaries, device manages identity — each side does its own job.
An example: A campus remediates: FEXCloud produces the assessment report, enterprise IT hardens the boundary, gateways upgrade firmware — the three-way split passes review at once. The logic is that classified protection is a system, not a single point — all three sides in place, the assessment passes.
4. The FEXCloud Side: How Platform-Level Protection Is Done
FEXCloud's duty — platform security: host, application, data and communication security; Data protection — encryption and backup: encrypted transport, encrypted storage, scheduled backup; Access control — accounts and permissions: least privilege, two-factor and operation logging; Security audit — log retention: platform operation logs meet the retention requirement.
In one sentence: the FEXCloud side is platform security (encryption, permissions and audit) — platform-side evidence is provided at assessment.
An example: FEXCloud passes Level 2: hardened hosts, encrypted data and six-month log retention — the assessment passes. The logic is that the platform side is the first half of classified protection — data protection, access control and audit all meet the standard — the platform secure, half the assessment is done.
5. The User Side: Network Boundaries and Account Permissions
The user side's duty — enterprise IT: boundary protection, account systems and permission management; Network boundaries — firewalls and isolation: the platform access zone isolated from the production zone; Account permissions — least privilege: different roles, different rights, revoked on departure; Login security — two-factor and strong passwords: management accounts with strong passwords plus two-factor.
In one sentence: the user side is boundary isolation, least privilege, strong passwords and operation logging — enterprise IT's second half.
An example: An enterprise IT team remediates: a firewall at the platform access zone, two-factor for management accounts and role-based permissions — every remediation item passes. The logic is that without boundary isolation and account tightening, even the most secure platform is wasted — both ends hardened, the assessment holds.
6. The Device Side: Access Whitelist and Least Privilege
The device side's duty — end devices: trusted identity, controlled access and secure communication; The access whitelist — only listed devices: unregistered MACs or serial numbers are refused; Least privilege — devices only do their own work: acquire and report, never overreach; Firmware security — signed updates and verification: signature-checked, upgraded promptly.
In one sentence: the device side is whitelist access, least privilege, firmware verification and encrypted uplink — the edge device guards the entrance.
An example: A campus device access: 200 devices on the whitelist, unregistered devices refused and firmware signature-checked — illegal devices cannot enter. The logic is that the whitelist holds the entrance and least privilege limits behavior — devices never connect wildly, the platform stays secure.
7. The Edge Gateway: Never Exposed, Tunnel Uplink
The edge risk — public exposure: a gateway directly on the public network is an open door; The right approach — tunnel uplink: the edge connects to the platform through a VPN or tunnel; What the tunnel does — hiding ports: the public network cannot see the edge, ports stay hidden; The gateway's position — on the intranet side: deployed inside the user's network, egressing through the tunnel.
In one sentence: the edge is never exposed to the public network and goes uplink through a tunnel — the attack surface shrinks, no entrance is findable.
An example: A campus ESX gateway: deployed on the intranet and connected to FEXCloud through a tunnel — public scans find no gateway ports — hardening passes. The logic is that the gateway is a data exit, not a public door — the tunnel keeps the public network from seeing the edge — no entrance, no attack.
8. The Filing Process and Cycle
Step one, classification — decide the level: Level 2 or Level 3 by business impact; Step two, filing — public security organ: submit the classification report and complete filing; Step three, assessment — an assessment body: scored against GB/T 22239; Step four, remediation — fix issues: remediate nonconforming items by the assessment result; Step five, annual testing — periodic: Level 2 tested annually, Level 3 at a higher frequency.
In one sentence: the filing process is classification, filing, assessment, remediation and annual testing — the cycle follows the level.
An example: A Level 2 platform: two weeks to classify, two to file, four to assess and four to remediate — first assessment completed in about three months. The logic is that classified protection is a process, not a certificate — precise classification, complete materials and solid remediation — the process finished, compliance lands.
9. The IoT Extension Requirements: Managing Perception Nodes
The extension requirements — GB/T 22239 includes IoT security extension requirements; Perception-node risk — dispersed terminals: many sensors and gateways, hard to manage uniformly; Perception-node control — identity and access: perception-node identity authentication and whitelist access; Perception-node communication — encryption and verification: uplink data encrypted and tamper-resistant.
In one sentence: the IoT extension requirements are identity authentication, whitelists and encrypted uplink for perception nodes — dispersed terminals managed uniformly.
An example: A campus perception nodes: authenticated access, encrypted uplink and unified management on the platform — extension requirements met. The logic is that classified protection 2.0 covers IoT scenarios — authentication, whitelist and encryption in place, the extension requirements are met.
10. Back to YESLON: The FEXCloud + ESX Combination
FEXCloud's position — the cloud platform: the carrier of platform-side protection; ESX's position — the edge gateway: the executor of device-side security; The combination's security logic — cloud and edge as one: platform security and edge security managed together; The combination's compliance path — passing together: the platform passes its level, the edge remediates against the extension requirements.
In one sentence: FEXCloud plus ESX equals platform security plus edge security — cloud and edge as one, classified protection passes smoothly.
An example: A campus adopts FEXCloud + ESX: the platform passes Level 2 and the edge remediates against the extension requirements — the assessment passes in one round. The logic is that the combination's value is clear responsibility — the platform manages the platform, the edge manages devices — compliance remediation takes no detours.
11. Self-Check: Five Questions on Classified Protection
Question one, is the level right — classification basis: Level 2 or Level 3 decided by business impact; Question two, are the three sides clear — responsibility split: platform, user and device each mind their own; Question three, is the whitelist built — device access: edge whitelist and identity authentication; Question four, is the gateway hidden — edge security: gateway never exposed, tunnel uplink; Question five, is the process complete — filing and assessment: classify, file, assess, remediate, test annually.
In one sentence: the five questions are right level, clear three-way split, built whitelist, hidden gateway and complete process — all five pass, compliance lands.
A self-check example: A campus self-checks before launch: Level 2 (right), three-way split (clear), 200-device whitelist (built), gateway tunnel (hidden) and filing-assessment (complete) — all five pass — formal operation begins. Classified protection is not a single platform action — it is a three-way responsibility and one process — the level right, responsibilities clear, whitelist built, gateway hidden and process complete, the energy IoT platform's compliance truly lands.
Scope and Limitations
- The conclusions in this article are intended for LV distribution and electrical-safety sites. Standard numbers (GB/T 22239) refer to their currently effective editions, and product parameters follow the latest FEXLINK selection handbook and product knowledge base.
- Quantitative criteria (protection zone, discharge and residual voltage, earth resistance, thresholds and grading) hold under the preconditions stated in this article. Where the site voltage level, earthing arrangement, environmental category or load profile differs, the figures must be recalculated. Specific configurations involving ESX intelligent edge computing gateway should be verified against actual circuit parameters.
- Specific product models and parameters are subject to the latest selection handbook and product knowledge base; this article does not constitute selection or procurement advice.
- Standard numbers cited here refer to the currently effective editions; when a standard is revised, the related quantitative conclusions must be re-checked.
- Deployment and implementation for specific projects must be carried out by qualified engineers based on site survey and design drawings.
Frequently Asked Questions
How Cybersecurity Classified Protection 2.0 Applies to an
A campus deploys an energy-monitoring platform and is asked to "pass the classified protection test" — should it be Level 2 or Level 3