PSIRT Policies

Last updated: November 2026

Purpose and Scope

Sigen attaches great importance to product security and strives to quickly assess and resolve product security issues. It is committed to building a sustainable and trustworthy vulnerability management system, and working openly with external stakeholders to jointly address the challenges of vulnerabilities.

This policy applies to products, software, mobile applications, and cloud services provided by Sigenergy that remain within their security update support periods. See the Update Period page for the applicable support periods.

Vulnerability Management Process

The following graphic illustrates the Sigen PSIRT process at a high level.

Upon receiving any vulnerability notification, we will collaborate with the relevant product teams to analyze and verify the vulnerability, assess its severity based on the actual impact on the product, determine the remediation priority, and develop a remediation plan (including workarounds, patches/version updates, and other risk mitigation measures that customers can implement).

The Sigenergy PSIRT process covers intake, validation, assessment, remediation, disclosure, and continuous improvement. If remediation validation is unsuccessful, or if residual risk, broader impact, or recurrence is identified after release, the issue returns to the appropriate stage for further handling.

Five-stage closed-loop PSIRT vulnerability management process

The PSIRT vulnerability management process consists of five connected stages. During Vulnerability Awareness, we receive security notifications and identify the relevant development team. During Validation and Assessment, we confirm whether a suspected vulnerability is valid and determine its scope of impact. During Vulnerability Remediation, we develop and implement a fix or risk mitigation measures. During Vulnerability Disclosure, we provide customers with vulnerability information and security updates in accordance with the communication plan. During Closed-Loop Improvement, we incorporate feedback from customers and internal teams to improve our products and processes before returning to the Vulnerability Awareness stage.

Communication and Expedited Handling

Sigenergy PSIRT normally acknowledges a vulnerability report by email within 24 hours of receipt and provides the reporter with necessary status updates based on the severity of the issue and remediation progress.

In addition to acknowledging receipt, Sigenergy PSIRT will provide an estimated initial response time and a schedule for subsequent status updates in the acknowledgment email or later communications, taking into account the vulnerability's severity, complexity, and remediation progress. We will notify the reporter when a significant development occurs or the previously communicated schedule changes.

Sigenergy will initiate expedited handling if a vulnerability has been publicly exploited, shows signs of active exploitation, is likely to attract widespread attention, or may pose a significant security risk to customers. When the expedited handling criteria are met, Sigenergy will provide an initial notification to affected customers within 72 hours after confirming the relevant conditions and will continue to provide updates as remediation progresses.

Severity Assessment

Sigen currently uses the Common Vulnerability Scoring System version 3.1 (CVSS v3.1) to evaluate the severity level of identified vulnerabilities. CVSS enables a common scoring method and a common language to communicate the characteristics and impacts of vulnerabilities. CVSS attempts to establish a measurement of how much concern a vulnerability warrants.

The CVSS model uses three distinct measurements or scores that include Base, Temporal, and Environmental calculations, each consisting of a set of metrics. We use the Qualitative Severity Rating Scale from CVSS to define severity rating:

Security Impact Rating CVSS Score
Critical 9.0–10.0
High 7.0–8.9
Medium 4.0–6.9
Low 0.0–3.9

Vulnerability Remediation

Sigen will push updates to the mySigen App, where customers can confirm and complete product security updates.

Customers should promptly review security advisories and apply recommended updates or mitigations during an appropriate maintenance window. Customers who choose not to apply, or to delay applying, an available update assume the resulting risks, including security risks, data loss, system interruption, or other consequences.

Coordinated Vulnerability Disclosure

Sigenergy asks reporters to keep undisclosed vulnerability information confidential until a fix or appropriate mitigation is available. Sigenergy will coordinate an appropriate disclosure date with the reporter and affected suppliers, taking into account vulnerability risk, remediation readiness, the need to protect customers, and stakeholder input.

Uncoordinated early disclosure may increase customer risk. If active exploitation, regulatory requirements, or another emergency requires earlier disclosure, Sigenergy will prioritize providing customers with the necessary risk information and mitigation guidance.

Sigenergy supports good-faith, non-destructive security research. Researchers should test only products, devices, accounts, and data they are authorized to test. They must not conduct denial-of-service attacks, disrupt product operation, bypass physical security controls, violate privacy, access or retain data unrelated to vulnerability validation, or exploit a vulnerability for improper gain. When researchers comply with applicable law, this policy, and the coordinated disclosure requirements, Sigenergy will not pursue action solely because they submitted a vulnerability report in good faith. This provision does not authorize any activity that violates applicable law, contractual obligations, or third-party rights.

Before public disclosure, Sigenergy shares necessary information only with internal personnel who need it to handle the vulnerability, affected suppliers, coordination bodies, or competent authorities legally entitled to receive it. Sigenergy PSIRT determines the scope of sharing, disclosure decisions, and any embargo period together with the relevant product, security, legal, and compliance representatives, based on vulnerability risk, remediation readiness, third-party coordination arrangements, and customer protection needs. If the embargo period needs to change, Sigenergy will make reasonable efforts to coordinate a new disclosure date with the reporter and affected parties.

Protecting Vulnerability Information

Sigenergy uses and shares vulnerability information only to the extent necessary to handle the vulnerability and restricts access to undisclosed vulnerability information.

Do not send passwords, private keys, recovery codes, customer data, or other sensitive information unrelated to vulnerability validation. If sensitive vulnerability information must be submitted, you may encrypt it with Sigenergy's published PGP public key before sending it to the PSIRT email address. See Sensitive Information and Attachments on the Reporting Vulnerabilities page for the public key, full fingerprint, and usage instructions. PGP encryption is not required to submit a vulnerability report, and reports sent without PGP encryption will still be accepted. If an attachment exceeds the email size limit, contact us through the PSIRT email address first, and we will provide an appropriate secure transfer method.

Sigenergy will not reject a suspected vulnerability solely because it was submitted through a different channel or the initial report is incomplete.

Third-Party and Open-Source Component Vulnerabilities

If a vulnerability is identified in a product or service supplied by a third party during product development, delivery, or deployment, Sigenergy will proactively contact the supplier to seek remediation and will reference the supplier's CVSS score when publishing a security advisory. For open-source software vulnerabilities, Sigenergy will follow the vulnerability management practices of the relevant open-source community, submit suspected vulnerabilities to that community, encourage timely remediation, and reference the CVSS score provided by the open-source community when publishing a security advisory.

Security Bulletins

Sigenergy publishes security advisories for vulnerabilities rated Critical or High. Before publishing an advisory, Sigenergy completes its vulnerability response process and confirms that a software update or other measure sufficient to address the vulnerability is available. A security advisory provides stakeholders with enough information to protect themselves while avoiding excessive technical detail that could facilitate malicious exploitation.

Security advisories typically include:

  1. Affected products and versions;
  2. The vulnerability identifier;
  3. A brief description of the vulnerability and its potential impact if exploited;
  4. The CVSS severity rating;
  5. Security updates, mitigations, or other required actions;
  6. The publication date and last updated date; and
  7. Actions users need to take.

Medium- and Low-severity vulnerabilities may be disclosed through a consolidated security advisory, release notes, or another appropriate method, depending on the actual risk.

Sigenergy publishes security advisories and consolidated advisories on the Security Bulletins page of this website. Release notes are provided with the corresponding product release or security update. For vulnerabilities affecting third-party components, the relevant advisory will reference the third-party vulnerability advisory or updated version, or provide enough information for users to determine whether the vulnerability affects a Sigenergy product.

Sigenergy publishes information about remediated vulnerabilities. Sigenergy may decide not to publish a separate advisory only when a vulnerability applies solely to a remote data processing solution, has been fully remediated, deployment of the remediation is controlled by Sigenergy, and no residual risk remains that requires users to be informed or take action. If Sigenergy determines that the risk of full disclosure outweighs the security benefit, it may delay disclosure in accordance with the coordinated disclosure principles and inform affected users by email of the planned disclosure date and necessary risk information.

Security Updates

Sigenergy may provide security updates through the mySigen App, product maintenance tools, cloud platforms, or other authorized channels. Customers should review security advisories and apply recommended updates or mitigations during an appropriate maintenance window.

Security updates are provided free of charge during the published security update support period, unless otherwise agreed between the manufacturer and an enterprise customer for a customized product. Once an update is available, Sigenergy distributes it in a timely manner based on the vulnerability's priority, urgency, and target remediation time. If an update cannot be installed automatically, Sigenergy will provide applicable instructions for installation, deployment, and verification of the installation result.

Disclaimer

This document is provided for informational purposes only and on an “as is” basis, without any express, implied, or statutory warranties, including but not limited to warranties of merchantability, fitness for a particular purpose, or non-infringement. Nothing in this document creates any contractual obligation, service commitment, or guarantee regarding vulnerability response, remediation timelines, or security performance. Sigenergy may update, modify, or withdraw the information in this document at any time without prior notice. Nothing in this policy authorizes any activity that violates applicable laws, regulations, or contractual obligations.

Contact Us