Vulnerability Handling Policy
BMS System Security Vulnerability Handling Management Regulations
General Provisions
These regulations are formulated to standardize the handling of security vulnerabilities for the Battery Management System (BMS) and mitigate safety risks. The Company shall fully comply with applicable national laws and regulations concerning data security, cybersecurity and functional safety. Governed by three core principles – graded vulnerability disposal, full-lifecycle management and compliant closed-loop management, the regulations shall be strictly implemented across all departments and relevant staff. This document is publicly available and accessible anytime on the Company’s official website.
1. Vulnerability Risk Classification Criteria
Based on ASIL functional safety levels and hazard severity, vulnerabilities are classified into three grades: Critical, Medium and Low Risk.
- Critical Risk (ASIL‑C/D): Failures of overcharge/over‑discharge protection, insulation detection abnormalities, remote firmware tampering and similar defects.
- Medium Risk (ASIL‑B): No immediate safety hazards but compromising system precision and operational stability, including SOC calculation drift and CAN bus message injection.
- Low Risk (ASIL‑A/QM): Only UI and configuration issues with zero safety risks, such as operational log leakage and unauthorized read/write access to non‑critical parameters.
2. Vulnerability Handling Specifications
(1) Technical Remediation Standards
Tailored remediation shall be performed per risk tier:
Critical Risk: Mandatory OTA patches shall be released within 72 hours. For emergencies such as insulation resistance below 1kΩ/V, the hardware interlock shall cut off high voltage within 100ms.
- Medium Risk: Incremental silent hotfix for automatic background firmware update without device reboot.
- Low Risk: Fixed via remote configuration or local tools; no equipment restart required.
(2) End‑to‑End Process Control
- A 7×24 vulnerability submission channel is available. Vulnerability verification shall be finished within 48 hours upon receipt, and relevant reports shall be submitted to MIIT’s vulnerability platform per regulatory requirements.
- Complete risk assessment and grading to define affected scope.
- Deadline rules: Critical vulnerabilities to complete fixing, regression test and penetration test within 24h; Medium within 72h; Low risks incorporated into regular version cycles.
- After patch release, promptly notify users of risks and upgrade instructions; conduct post‑mortem root cause analysis to refine coding standards and test cases to prevent recurring faults.
(3) Emergency Response for Large‑Scale Critical Vulnerability Outbreak
- Leverage cloud platform to monitor real‑time data of overvoltage, overheating and insulation faults.
- Remotely limit output power and disable fast charging of abnormal devices for safety isolation.
- Initiate product recall per national laws and provide free firmware upgrade or hardware replacement for customers.
(4) Data Compliance Rules
Core operational data including voltage, temperature and fault logs shall be retained for minimum 90 days with full traceability and retrievability.
3. Implementation Assurance
- Organizational Responsibility: Appoint a dedicated full‑time BMS safety manager and set up a cross‑functional response team consisting of R&D, QA, O&M and legal representatives with clear individual accountability.
- Mandatory Time Limits: Critical vulnerabilities: initial response within 24h, full remediation within 72h; Medium vulnerabilities: initial response within 72h, full remediation within 7 working days.
- Dual Technical Safeguard: Independent hardware security module operates separately, unaffected by faults of master control software or MCU to realize dual safety protection.
4. Detailed Handling Rules for Common Vulnerabilities
| Vulnerability Type | Risk Level | Disposal Measures |
|---|
| Overcharge/Over‑discharge Protection Failure | Critical | Dual hardware & software protection, 100ms high‑voltage cutoff + mandatory OTA rollout |
| CAN Bus Message Injection | Medium | Add message filtering rules, activate degraded operation + background silent patch |
| SOC Calculation Deviation | Medium | Optimize algorithm & verification logic, automatic background update |
| Log Leakage & Unauthorized Parameter Access | Low | Log desensitization + disable unused debug ports |
5. Compliance Consultation & Violation Reporting
Confidential consultation and reporting channels are established. Informant privacy is fully protected; all submissions will be verified with timely feedback.
E‑mail: kgmarket@kgooer.com
Hotline: +86‑571‑85373365
Supplementary Provisions
These regulations shall take effect upon official release.
The interpretation right of this document belongs to the Company’s BMS Safety Management