Overview
Sigenergy Security Incident Response Center operates a Coordinated Vulnerability Disclosure (CVD) program — with the product-facing work run by our Product Security Incident Response Team (PSIRT) — aligned with ISO/IEC 29147 (vulnerability disclosure) and ISO/IEC 30111 (vulnerability handling processes).
We treat every report as a priority input to product security. Each vulnerability follows a defined lifecycle — from intake and triage through remediation and public disclosure — with clear ownership, documented decision points, and status communication to the reporter at every stage.
Process at a Glance
Process Stages
Objective: capture every report through a secure, structured channel and confirm receipt.
- Reports are received via csirt@sigenergy.cloud or the vulnerability reporting form.
- Each report is assigned a unique reference identifier for tracking.
- The report is logged with metadata: reporter, affected product, version, and vulnerability type.
- An initial acknowledgement is sent to the reporter per the response SLA.
Objective: confirm the issue is a genuine, reproducible vulnerability and determine its scope.
- The reported issue is reproduced in a controlled laboratory environment.
- False positives, misconfigurations, and known duplicates are identified and closed with feedback.
- Affected products, firmware/software versions, and exposure surface are determined.
- The reporter is notified of the validation outcome.
Objective: score severity consistently and prioritize remediation effort.
- The vulnerability is scored using CVSS v4.0 (Base, Threat, and Environmental metrics).
- A severity rating is assigned — Critical High Medium or Low.
- Exploitability, exposure, and business impact drive remediation priority.
- The severity assessment is shared with the reporter for validation.
Objective: identify the root cause and develop a complete, secure fix.
- A root-cause analysis is performed across code, configuration, and architecture.
- The fix is designed to address the root cause, not just the symptom.
- Remediation is tracked against the severity-based target timeline.
- Where a fix is deferred, compensating controls and mitigations are defined.
Objective: verify the fix resolves the issue without introducing new risks.
- The fix is validated against the original proof of concept.
- Regression testing confirms no new defects or security regressions are introduced.
- Security review of the patch is performed prior to release.
- Release artifacts are verified for integrity and authenticity.
Objective: deliver the fix to customers and publish coordinated disclosure.
- The fixed version is distributed through official update channels.
- A CVE identifier is requested or assigned for the vulnerability.
- A security advisory is published with CVSS vector, severity, and remediation guidance.
- Disclosure is coordinated with the reporter and any affected third parties.
Objective: monitor for exploitation and feed lessons back into the process.
- Public sources are monitored for exploitation activity related to the advisory.
- The advisory is updated if new information, affected versions, or mitigations emerge.
- Lessons learned are captured and applied to the secure development lifecycle.
- Recurring issue classes feed threat intelligence and hardening programs.
Response Timelines
Target response times are based on the assigned severity. Timelines are service objectives and may be adjusted for exceptional circumstances, in which case the reporter is kept informed.
| Severity | Initial Response | Fix Target | Status Updates |
|---|---|---|---|
| Critical | Within 24 hours | As soon as possible (target ≤ 7 days) | Daily |
| High | Within 3 business days | Target ≤ 30 days | Weekly |
| Medium | Within 5 business days | Target ≤ 90 days | Every two weeks |
| Low | Within 10 business days | Next scheduled release | Per release |
How to Report a Vulnerability
Send your report to csirt@sigenergy.cloud. A complete report enables faster triage and a shorter time to fix. Please include, where possible:
- Affected product, model, and firmware/software version — the more precise, the better.
- Vulnerability type — e.g. injection, authentication bypass, XSS, memory corruption, etc.
- Detailed reproduction steps — a clear, ordered sequence we can follow.
- Proof of concept (PoC) or exploit code — if available; it greatly accelerates validation.
- Observed impact — what an attacker could achieve and any data at risk.
- Contact details — for coordination and credit (a name and email are sufficient).
- Disclosure plans — whether you intend to publish the finding independently.
What Reporters Can Expect
- Acknowledgement within the severity-based response time.
- A unique reference ID for tracking the report through its lifecycle.
- Status updates at key milestones — validation, prioritization, fix, and disclosure.
- Transparent severity assessment, including the CVSS vector and rating.
- Credit in the published advisory unless you prefer to remain anonymous.
- Coordinated disclosure timing agreed with you before publication.
Disclosure Policy
Default 90-day coordinated disclosure
Sigenergy follows a 90-day coordinated disclosure timeline. We aim to release a fix and publish an advisory within 90 days of validating a vulnerability. If more time is genuinely required, we will agree a revised timeline with the reporter rather than leaving the process open-ended.
Good-faith research is protected
We will not pursue legal action against, or request the prosecution of, researchers who act in good faith and follow our Rules of Engagement. We view responsible disclosure as a contribution to the safety of our customers and products.
Credit and acknowledgement
Reporters are credited in the published advisory by name or alias unless they request anonymity. Crediting is at the discretion of the reporter.
Independent disclosure
If we cannot resolve a validated issue or communicate a plan within a reasonable timeframe, the reporter may disclose the finding independently. We ask only that the disclosure be accurate and non-destructive.
Rules of Engagement
To keep research safe for everyone, we ask reporters to observe the following while testing:
- Do not exploit a vulnerability beyond what is necessary to demonstrate it.
- Do not exfiltrate, modify, or delete production data beyond a minimal proof of concept.
- Do not conduct denial-of-service, destructive, or ransomware testing.
- Do not use social engineering or physical attacks against staff, customers, or facilities.
- Do not publicly disclose details before the coordinated disclosure is complete.
- Do test on systems you own or are authorized to test.
Security Testing Requirements
Security testing may cover inverter power hardware, embedded firmware, PCB circuitry, device communication links, cloud services, mobile apps, backend APIs and device-to-cloud communication protocols. Devices carry high-voltage and high-current hazards, and testing also touches business systems and user data safety. The following requirements must be strictly observed.
Electrical Safety Requirements
- Residual high voltage remains on the AC/DC sides of the inverter and on the DC-bus capacitors. Before opening the enclosure, disconnecting cables or soldering, you must power off, discharge, and verify with a measuring instrument that no voltage is present. Insulated tools and fire-fighting equipment must be present in the test area.
- Connecting a modified inverter to the public power grid is strictly prohibited without written permission from the Sigenergy security team. Testing is only permitted on an isolated, offline bench.
- If smoke, arcing or abnormal noise occurs, immediately cut the power, evacuate the area and report the incident.
Hardware Modifications & Firmware Changes Require Prior Notification
- Any circuit modification, flying lead, component replacement, firmware dump, reverse engineering, modified flashing or fault injection must be submitted through the designated channel before execution (device serial number, plan, purpose, risk). Work may proceed only after the risk assessment is approved.
- Notification is used for risk assessment and technical support only. Opening the enclosure, modifying hardware or flashing firmware will void the original manufacturer's warranty of the sample unit.
- Running modified firmware that permanently bypasses overvoltage, overcurrent or anti-islanding protection is prohibited.
Cloud, App, API & Communication Testing Boundaries
- Testing is limited to allocated test accounts, test environments and your own test devices. Scanning or penetrating production environments is strictly prohibited, as is accessing other real customers' devices or privacy data.
- API concurrency stress testing, bulk fuzzing, message tampering, MITM capture and decryption, app unpacking and hook debugging, and forging device report or control messages all require prior notification.
- Sending bulk forged device messages to flood the cloud platform is prohibited. Using authorization flaws or interface vulnerabilities to control test devices that are not yours is prohibited.
- Signing keys, credentials and protocol details obtained through app reverse engineering or traffic capture must not be made public.
Vulnerability & Information Confidentiality
- Firmware, protocols, API logic and vulnerability PoCs are the intellectual property of Sigenergy.
- Vulnerabilities must be submitted through the defined process, and the confidentiality window must be respected. Publishing vulnerability details in public accounts, forums or community groups without written permission is prohibited.
Prohibited Actions
- Over-powering or short-circuiting the main power circuit.
- Tampering with metering or grid-compliance-related hardware and logic.
- Transferring sample devices, test accounts or test environments to unauthorized personnel.
- Implanting persistent backdoors.
- Using vulnerabilities to bulk scrape data or control devices.
Traceability & Reporting
- All notifications must be recorded as a ticket or through the designated written channel.
- Retaining test logs, captured messages and reproduction materials is recommended.
Roles & Responsibilities
| Role | Responsibilities |
|---|---|
| Sigenergy CSIRT | Single point of contact; coordinates triage, prioritization, disclosure, and communication with the reporter and partners. |
| Product Security Engineering | Root-cause analysis, fix design and implementation, and security review of patches. |
| Quality Assurance | Verifies fixes and performs regression testing prior to release. |
| Reporter / Researcher | Provides accurate, actionable information; coordinates on severity and disclosure timing. |
| Customers & Users | Apply patches and advisories promptly and report suspected issues. |
| CVE & CERT Communities | Identifier assignment and broader industry coordination where applicable. |
Frequently Asked Questions
How do I report a vulnerability?
How quickly will I get a response?
Can I report anonymously?
Will I be credited for my report?
Do you offer a bug bounty?
How is severity determined?
What if I disagree with the severity assessment?
Report a Vulnerability
Found a security issue in a Sigenergy product or service? Our team is ready to work with you through every stage of coordinated disclosure.
Contact csirt@sigenergy.cloud