Disclosure Policy
Wecon IoT Product Vulnerability Disclosure Policy
Version: 1.1
Effective Date: June 1, 2026
Scope of Application: All digital‑element‑embedded products sold by the Company in the EU market
1. Overview
The Company attaches high importance to the cybersecurity of IoT products and is committed to providing transparent and efficient vulnerability reporting channels for security researchers, customers, partners and the general public. This document specifies:
- How to report security vulnerabilities in the Company’s IoT products
- Processing workflows and emergency response mechanisms upon receipt of vulnerability reports
- Rights and obligations of all parties throughout vulnerability disclosure
- How the Company fulfils compliance obligations under the EU Cyber Resilience Act
This procedure is implemented and maintained by the Company’s Product Security Incident Response Team (PSIRT).
2. Legal and Standard References
This vulnerability reporting mechanism is designed and implemented in accordance with the following legal instruments and harmonised standards:
- EU Cyber Resilience Act
- EN 40000‑1‑2
- EN 40000‑1‑3
3. Vulnerability Reporting Channels
3.1 Standard Contact Points
The Company has established standard contact addresses for receiving vulnerability reports:
- Dedicated security vulnerability reporting email addresses: support01@we‑con.com.cn; cybersecurity@wecon.com.cn
- Security vulnerability reporting web form: https://www.we‑con.com.cn/en/contact.html or https://docs.we-con.com.cn/bin/view/Cybersecurity/Report%20Vulnerability/
- European regional agents, sales personnel and technical staff
- Wecon Headquarters sales and technical personnel, Tel: (+86) 400 799 8189
3.2 Recommended Report Content
To facilitate rapid identification and remediation of vulnerabilities, reporters are encouraged to include the following information in submissions where possible:
- Name, model and firmware/software version(s) of affected products
- Detailed vulnerability description and reproduction steps
- Potential security impacts of the vulnerability
- Environmental information for vulnerability discovery (e.g. network configuration, test platform)
- Relevant proof‑of‑concept code or screenshots (if available)
- Proposed remediation measures (if available)
3.3 Safe‑Harbour Provision
The Company undertakes not to take legal action against bona‑fide security researchers who adhere to the following principles:
- Do not exploit vulnerabilities for malicious attacks or improper gain
- Report vulnerabilities to the Company in the first instance, rather than disclosing them publicly without coordination
- Refrain from extortion, threats or other improper conduct
4. Vulnerability Handling Workflow
The Company processes received vulnerability reports in accordance with the workflow below.
4.1 Phase 1: Receipt and Acknowledgement
4.1.1 Report Receipt
All vulnerability reports submitted via the above‑mentioned channels are centrally received and managed by the PSIRT. Upon receipt, the PSIRT shall send an acknowledgement email within 48‑72 hours to confirm report receipt and outline initial processing arrangements.
4.1.2 Assignment of Tracking ID
Each valid vulnerability report shall be assigned a unique tracking identifier for subsequent communication and status inquiry. Reporters may use this ID to track remediation progress.
4.2 Phase 2: Verification and Assessment
4.2.1 Vulnerability Verification
The PSIRT conducts technical review of submissions to confirm authenticity, reproducibility and relevance to the Company’s products. Verification activities include:
- Reproducing vulnerability trigger conditions
- Confirming scope of affected products and versions
- Assessing technical details of the vulnerability
4.2.2 Risk Assessment and Severity Classification
Confirmed vulnerabilities are risk‑assessed against the risk‑management framework defined in EN 40000‑1‑2. Vulnerabilities are classified by severity as follows:
| Severity Level | Description |
|---|---|
| Critical | Remotely exploitable without authentication; may lead to full device compromise |
| High | May result in sensitive‑information disclosure, privilege escalation or service disruption |
| Medium | Exploitation subject to restrictive preconditions; limited impact scope |
| Low | Minor impact; impractical for real‑world exploitation |
4.3 Phase 3: Regulatory Notification
4.3.1 Actively‑Exploited Vulnerabilities
Where the Company obtains reliable evidence that malicious actors are unauthorisedly exploiting product flaws, the following notification procedures apply:
| Timeframe | Notification Requirements |
|---|---|
| Within 24 hours | Submit an early warning via ENISA’s Single Reporting Platform, describing vulnerability nature and affected Member‑State scope |
| Within 72 hours | Submit detailed notification including severity description, preliminary assessment and implemented mitigating measures |
| Within 14 days after patch release | Submit final report containing full vulnerability analysis, impact assessment and implemented remediation measures |
4.3.2 Severe Security Incidents
If a vulnerability triggers a severe security incident materially impairing product availability, authenticity, integrity or confidentiality, the Company shall submit a preliminary incident notification within 72 hours and a final incident report within one month.
4.3.3 Notification Recipients
Notifications follow a dual‑synchronisation mechanism and are submitted via ENISA‑operated Single Reporting Platform to: the CSIRT of the Member State where the Company’s principal EU establishment is located, and ENISA.
4.4 Phase 4: Emergency‑Response Mechanism
Where confirmed vulnerabilities are under active exploitation, or where security incidents have broad‑reaching or severe consequences, the Company shall activate its emergency‑response mechanism immediately to maximise user‑risk mitigation. Core components are:
- Immediate cross‑functional emergency team formation: Co‑ordinated by PSIRT, dedicated response team assembling R&D, security, legal, customer‑support and management personnel for unified command and accelerated decision‑making.
- Rapid development and publication of interim mitigations: Prior to patch completion, deliver actionable interim countermeasures (e.g. configuration changes, network isolation, service deactivation) to block exploitation vectors.
- Urgent customer advisories: Notify affected customers via email, in‑product alerts, official security advisories and, where necessary, direct telephone outreach, detailing vulnerabilities, associated risks and applicable interim steps.
- Proactive threat monitoring and coordination: Strengthen security monitoring for affected products; maintain close liaison with industry partners, local EU‑based CSIRTs and ENISA for threat‑intelligence sharing and collaborative response.
- Post‑incident review and improvement: Upon emergency‑response conclusion, conduct thorough root‑cause analysis, evaluate response efficacy, formulate improvement plans and integrate outcomes into secure product development and operation workflows.
4.5 Phase 5: Remediation and Development