Direct Answer

For a campus energy platform that needs to pass Classified Protection (Dengbao) Level 2, what does it technically take? The core of Level 2 concentrates on five things: identity authentication and access control, operation auditing, transmission encryption, data backup and boundary protection — the platform side needs graded accounts, retained logs, encrypted transmission and scheduled backups, not a pile of security appliances. FEXCloud, the IoT cloud platform, is designed against the Level 2 requirements of GB/T 22239-2019 in accounts, permissions, auditing, encryption and backup, with a checklist to follow for remediation.

A scene: a campus platform was about to take a Level 2 assessment, and a security vendor listed a long set of appliances — firewalls, bastion hosts, log audit — the project manager saw the budget double. The real face of Level 2 is a "platform capability checklist", not an "appliance shopping list" — get four things right — graded accounts, log retention, encrypted transmission and scheduled backup — and most of the assessment is already won.

1. The Framework of Level 2 Basic Requirements

Five technical layers — secure physical environment, secure communication network, secure regional boundary, secure computing environment, and security management center — at Level 2, the platform side mostly falls in the last three; Secure computing environment — identity authentication, access control, security audit, intrusion prevention, data integrity — the main battlefield of the platform application layer; Secure communication network — communication transmission encryption: authentication data and important business data must be transmitted encrypted — the transport layer is mandatory; Secure regional boundary — boundary protection, access control, intrusion prevention — the boundary between gateways and the platform; Management requirements — security management systems, secure operations, emergency response — the institutions and records the platform operation side must have.

In one sentence: Level 2 technical requirements are organized in five layers, and the platform-side main battlefield is "secure computing environment + secure communication network + secure regional boundary" — the assessment checklist matters more than the appliance list.

A framework example: a platform went through the Level 2 items once: account password policy did not comply, operation logs were too short, transmission was unencrypted, no backup drill — after four remediation items the assessment passed. Run the framework against the current state first, then fix the gaps — assessment is not building from zero but patching the gaps.

2. Identity Authentication: Graded Accounts and Password Policy

Graded accounts — three account types: administrator, operator and read-only visitor: administrators manage configuration, operators run business, visitors only view — grading is the foundation of permission design; Password policy — length, complexity, validity period, failure lockout: weak passwords are the most common deduction item in assessments — the password policy is configurable on the platform side; Optional two-factor — Level 2 does not force two-factor, but administrator accounts are recommended to enable it — a phone verification code or dynamic token — administrator accounts are the attack focus; Login failure handling — continuous-failure lockout and login logs: against brute force — the lockout policy is also an assessment item.

In one sentence: identity authentication is "graded accounts + password policy + failure handling" — grade accounts into three types, set password complexity, lock after failures, and this checkpoint passes.

An authentication example: before remediation all users shared one administrator account — after remediation: three role accounts separated, 12-character passwords with upper/lowercase and digits, 5 consecutive failures locking for 10 minutes — the recheck passed. Graded accounts are the cheapest and most critical remediation — one account managing everything is a guaranteed deduction at Level 2.

3. Least-Privilege Design: Roles and Data Scope

Role permission matrix — functional permissions assigned by role: administrators full, operators by module, visitors read-only — the permission matrix is the starting point of the design; Data scope control — campus-level/area-level/device-level data visibility: line operations see only their own area, management sees the whole — data scope is the second dimension of permissions; Default deny — new accounts default to least privilege: no default administrator — the permission-only-grows principle; Change trace — permission changes have approval and records: who gave whom what permission and when — changes are traceable.

In one sentence: least privilege is "roles manage functions, scope manages data, default minimum, changes traced" — the two dimensions of the permission matrix and data scope are how access control lands at Level 2.

A permission example: on a campus: 2 administrators manage configuration, 5 operations staff manage their own area devices, 3 visitors view reports read-only — new employees default to read-only and get privileges by request with traces — clear permissions, smooth assessment. Least privilege is not "blocking permissions" but "granting on demand" — with roles, scope and traces in place, the permission system stands.

4. Operation Auditing: Log Retention and Traceability

Audit scope — login logs, operation logs, configuration changes, alarm handling: who did what and when — auditing covers critical operations; Log elements — time, account, source IP, operation object, result: only with all five elements can events be traced — missing one breaks the chain; Retention period — logs retained for no less than 6 months (per the requirements of GB/T 22239-2019): insufficient retention is a common remediation item; Audit protection — logs tamper-proof: read-only permissions, scheduled archiving — the audit logs themselves must be protected.

In one sentence: operation auditing is "complete scope, complete elements, retained long enough, tamper-proof" — five-element logs plus 6-month retention mean events can be found and traced when they happen.

An audit example: one day an alarm rule was deleted by mistake on a platform — the audit logs were checked: time, account, operation object and result, all five elements present — the operator was located in 5 minutes and the configuration was restored. Log retention is not "storing for the sake of storing" but "findable" — with all five elements, tracing means something.

5. Transmission Encryption: Where TLS and the National Crypto Algorithms Sit

Transmission encryption requirement — authentication data and important business data transmitted encrypted: login passwords, alarm configuration, operation commands — nothing plaintext over the public network; TLS in place — TLS/HTTPS between platform and clients: full-site HTTPS for browser access — this is the most basic transmission encryption; Optional national crypto — national crypto algorithms (SM2/SM3/SM4) for high-security scenarios: government and finance-type campuses may require them — ordinary energy campuses are fine with TLS; Gateway uplink encryption — encryption on the channel from field gateways to the platform: encrypted channel recommended for 4G uplinks — the edge-to-cloud hop is easily overlooked.

In one sentence: transmission encryption is "login and business data encrypted + full-site HTTPS + gateway uplink encryption" — national crypto is optional for high-security scenarios — plaintext transmission is a guaranteed deduction at Level 2.

An encryption example: before remediation a platform's gateway-to-platform traffic ran plaintext over 4G — after remediation the uplink channel was encrypted and the whole site went HTTPS — the transmission encryption item passed the assessment. The edge-to-cloud hop is the most easily overlooked — gateway uplink encryption is the hole most often patched in Level 2.

6. Data Backup: Retention and Recovery Drills

Backup scope — configuration data, business data, historical points: configuration and business daily, points by retention policy — backup follows the temperature of the data; Backup methods — full + incremental: configuration and business full backups on a cycle, points incremental — the dual databases (corresponding to KD-0276) back up separately; Off-site copies — backup copies stored off-site: another room in the same city or another cloud region — if the local site is destroyed, the copies survive; Recovery drills — periodic recovery drills: "can back up" does not equal "can recover" — drills are an assessment plus and a real safeguard.

In one sentence: data backup is "complete scope, right methods, off-site copies, regular drills" — configuration and business backed up daily, points by policy, copies off-site, and a recovery drill every quarter.

A backup example: a platform backed up configuration and business fully every day and points by retention policy — off-site copies plus a quarterly recovery drill — one drill found recovery too slow, and after optimization recovery time halved. Backup without drills is no backup at all — "can back up" and "can recover" are two different things, and only drills make backup actually usable.

7. Boundary Protection: What the Platform Side Does

Boundary protection — the platform opens only necessary ports externally: Web access, gateway access — all unnecessary ports closed; Access control — source-IP allowlists, management backend restricted by source: management operations limited to trusted networks — the management surface is not exposed to the public network; Intrusion prevention — patch management, antivirus, abnormal-traffic monitoring on the platform side: timely patching is the basic item of Level 2; Vulnerability management — scheduled vulnerability scanning and fixes: high-risk vulnerabilities fixed within a deadline — vulnerabilities are the hardest-hit area of assessments.

In one sentence: boundary protection is "minimal ports + management surface not exposed + timely patches + zero high-risk vulnerabilities" — platform-side security is "closing the surface", not "piling on appliances".

A boundary example: before remediation a platform's management backend was directly exposed to the public network — after remediation the management surface was limited to intranet IPs and the Web kept only port 443 — public-network scanning risk was eliminated. Keeping the management surface off the public network is the highest-value item in boundary protection.

8. The Remediation Checklist: Seven Things to Pass Level 2

The seven items — ① graded accounts, ② password policy, ③ role permission matrix, ④ audit logs retained 6 months, ⑤ transmission encryption (HTTPS + gateway uplink), ⑥ backup and recovery drills, ⑦ boundary closure (minimal ports) — with these seven done, the backbone of the Level 2 assessment passes; The comparison method — compare the current state item by item against the assessment requirements: satisfied items marked green, gaps marked red — remediation is prioritized by the red items; The remediation rhythm — platform capability remediation in 2-4 weeks, institutional items in 1-2 weeks — do not drag remediation into an "appliance procurement project".

In one sentence: passing Level 2 is not buying appliances but a "seven-item remediation checklist" — accounts, passwords, permissions, audit, encryption, backup, boundary — when the platform capability is in place, the assessment passes naturally.

A checklist example: a platform went through the seven items: graded accounts already done, password policy fixed, log retention changed from 1 month to 6, transmission encryption added, drills made quarterly — remediation completed in three weeks and the assessment passed. The remediation checklist is "patching the current state" rather than "starting over" — go through the seven items one by one and the gaps become obvious.

9. Back to FEXLINK: How FEXCloud Aligns with Level 2

FEXCloud, the IoT cloud platform, aligns with the Level 2 requirements of GB/T 22239-2019 in five dimensions — graded account management, permission matrix configuration, operation audit logs, HTTPS and uplink encryption, scheduled backup and recovery drills. The landing order: ① graded accounts → ② password and permission matrix → ③ audit log retention → ④ transmission encryption → ⑤ backup drills → ⑥ boundary closure — six steps aligned, the assessment backbone passes.

One summary: what Level 2 means for an energy platform concentrates on five things — identity authentication and access control, operation auditing, transmission encryption, data backup and boundary protection — the platform side doing graded accounts, log retention, encrypted transmission and scheduled backup matters more than piling up security appliances. Level 2 is not an "appliance list" but a "platform capability list" — with the seven-item remediation done, the assessment passes naturally.

One reminder: do not be led astray by "Level 2 = buying appliances" — compare the current state against the framework first and patch the gaps — accounts, passwords, permissions, audit, encryption, backup and boundary, seven items that can mostly be landed at the platform functional layer. The starting point of the assessment is "the comparison checklist", not "the procurement list" — compare the current state first, then patch the gaps.

Scope and Limitations

  • The conclusions in this article are intended for LV distribution and electrical-safety sites. Standard numbers (GB/T 22239-2019) 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 FEXCloud IoT cloud platform 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

What Cybersecurity Classified Protection 2.0 Means for

For a campus energy platform that needs to pass Classified Protection (Dengbao) Level 2, what does it technically take