Legal · Coordinated Disclosure

Responsible Disclosure Policy

Sigenergy welcomes security research conducted in good faith. This policy defines how to report vulnerabilities and the protections we offer researchers.

Last updated: October 2026 · Version 1.0

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:

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.

Safe Harbor applies when you: make a good-faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our services; do not access or retain data beyond what is necessary to demonstrate the vulnerability; and report the issue to us before public disclosure.

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

Out of scope

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:

Please do not include excessive amounts of sensitive personal data, customer data, or credentials in your report. Where evidence contains such data, redact or mask it.

Researcher Expectations

To benefit from Safe Harbor and to protect our customers, we ask researchers to:

  1. Stop testing and report the issue as soon as a vulnerability is confirmed.
  2. Avoid accessing, modifying, or deleting data that does not belong to you.
  3. Avoid actions that could disrupt service for other users (no DoS, no mass exploitation).
  4. Provide us a reasonable time to remediate before public disclosure (see timeline below).
  5. Comply with applicable laws and this policy.

Disclosure Timeline

StageCommitment
Acknowledge receiptPer severity, as published in our vulnerability handling process: within 24 hours for critical issues and 3 business days for high severity
Initial triage & validationWithin 10 business days
RemediationBased on severity; Critical/High issues prioritized, generally within 90 days
Public disclosureCoordinated 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.

For any questions about this policy, contact the Sigenergy CSIRT at csirt@sigenergy.cloud.