Responsible Disclosure Policy
Sigenergy welcomes security research conducted in good faith. This policy defines how to report vulnerabilities and the protections we offer researchers.
Our Commitment
The Sigenergy Security Incident Response Center (CSIRT) is committed to working with the security research community to protect our customers and products. We follow internationally recognized coordinated vulnerability disclosure (CVD) practices aligned with ISO/IEC 29147 and ISO/IEC 30111.
If you report a vulnerability to us in accordance with this policy, we will:
- Acknowledge your report in a timely manner.
- Treat your report with confidentiality during the investigation.
- Investigate the issue and keep you informed of progress.
- Credit you in our Hall of Thanks if the issue is confirmed and you wish to be named.
Safe Harbor
When conducting vulnerability research and reporting under this policy, we consider such research to be authorized and we will not pursue civil action or file a complaint with law enforcement for accidental, good-faith violations of this policy.
If a third party (such as a cloud provider or another organization) files a legal claim against you as a result of your research conducted in compliance with this policy, we will make clear that your actions were authorized by this policy.
Scope
In scope
- Sigenergy web services and APIs, including *.sigenergy.com and *.sigencloud.com.
- Sigenergy mobile applications (Android and iOS).
- Sigenergy hardware products and their firmware and embedded software.
- The Sigenergy cloud platform and connected infrastructure.
Out of scope
- Social engineering, phishing, or physical attacks against employees, customers or facilities.
- Denial-of-service (DoS) attacks or any testing that degrades production services.
- Vulnerabilities in third-party systems not owned or operated by Sigenergy.
- Issues without a demonstrable security impact (e.g. missing HTTP security headers reported without exploit context).
How to Report
Send your report to the Sigenergy CSIRT at csirt@sigenergy.cloud, or use the vulnerability report form.
A high-quality report should include:
- The affected product, endpoint, or component and its version.
- A clear description of the vulnerability and its impact.
- Steps to reproduce, including proof-of-concept code or request/response evidence where possible.
- Your assessment of severity (CVSS if available).
- Your preferred contact method and whether you wish to be credited.
Researcher Expectations
To benefit from Safe Harbor and to protect our customers, we ask researchers to:
- Stop testing and report the issue as soon as a vulnerability is confirmed.
- Avoid accessing, modifying, or deleting data that does not belong to you.
- Avoid actions that could disrupt service for other users (no DoS, no mass exploitation).
- Provide us a reasonable time to remediate before public disclosure (see timeline below).
- Comply with applicable laws and this policy.
Disclosure Timeline
| Stage | Commitment |
|---|---|
| Acknowledge receipt | Per severity, as published in our vulnerability handling process: within 24 hours for critical issues and 3 business days for high severity |
| Initial triage & validation | Within 10 business days |
| Remediation | Based on severity; Critical/High issues prioritized, generally within 90 days |
| Public disclosure | Coordinated after a fix is released, or by mutual agreement |
We publish a security advisory (SVID) for confirmed issues and credit the reporter in the Acknowledgements page unless anonymity is requested.
CVE IDs
Vulnerabilities we confirm are published with a CNA-managed CVE ID where the issue meets the CVE Program definition of a vulnerability. Our scope, request process, response times and end-of-life policy are published in CVE ID Assignment; published advisories and their CVE assignment status are listed on the CVE Index.
To request a CVE ID, email csirt@sigenergy.cloud with CVE in the subject line.
Recognition
We value the time and effort of security researchers. Confirmed vulnerabilities are credited in our Hall of Thanks. We do not currently operate a monetary bug bounty program; recognition is provided through public credit.