Product Security Incident Response Team
How we find, triage, fix and disclose vulnerabilities in the products we ship — and how the PSIRT differs from the CSIRT.
What a PSIRT is
A Product Security Incident Response Team (PSIRT) is the team inside a manufacturer that handles vulnerabilities in the products and services it sells. It receives vulnerability reports, works out which products and versions are affected, drives a fix through engineering, and tells customers through security advisories.
The distinction that matters is whose systems are at risk. A CSIRT responds to incidents inside the organization — its own networks, systems and data. A PSIRT responds to vulnerabilities in the products that customers run in their own environments, where the manufacturer cannot patch on the customer's behalf: it ships a fixed release and the customer installs it. FIRST calls the focus on products the key differentiator between the two.
CSIRT · Internal
Incidents in Sigenergy's own estate. Detection, containment, eradication, recovery, forensics and regulatory notification for company incidents.
PSIRT · Product
Vulnerabilities in Sigenergy hardware, firmware, cloud services and apps. Triage, CVE ID assignment, fixed releases and coordinated disclosure.
PSIRT and CSIRT compared
| Dimension | CSIRT | PSIRT |
|---|---|---|
| Scope | Incidents in Sigenergy's own networks, systems and data | Vulnerabilities in the products and services we ship |
| Constituency | Employees and internal infrastructure | Customers, installers and asset owners |
| Typical inputs | Alerts, logs, user reports, threat intelligence | Researcher reports, third-party component advisories, internal testing, coordinators |
| Typical outputs | Contained incidents, recovered systems, post-incident reviews | Fixed releases, security advisories, CVE records, customer notifications |
| Clock starts | When an incident is detected | When a vulnerability is reported or published |
| Typical owner | CISO or IT security | Product security and engineering |
| Framework | FIRST CSIRT Services Framework | FIRST PSIRT Services Framework |
| Standards | ISO/IEC 27035 (incident management) | ISO/IEC 29147 (disclosure) and ISO/IEC 30111 (handling) |
How our PSIRT works
- Intake. Reports arrive through our report form, by email to csirt@sigenergy.cloud, or from coordinators and upstream suppliers. Each report gets a tracking identifier.
- Triage and validation. We reproduce the issue in a controlled environment, confirm the affected products and versions, and check for duplicates.
- Severity and priority. We score with CVSS v4.0 and assign a severity, which sets the remediation timeline and the communications cadence.
- Remediation. Product engineering fixes the root cause; we track the work against the severity-based target and define compensating controls where a fix is deferred.
- Verification and release. The fix is re-tested against the original proof of concept, regressions are checked, and the release is signed and distributed through official channels.
- Disclosure. We assign a CVE ID where the issue meets the CVE Program definition of a vulnerability, publish an advisory with the CVSS vector and remediation guidance, and publish the CVE Record within 24 hours of disclosure and never later than 72 hours.
- Post-disclosure. We monitor for exploitation, update advisories when new information appears, and feed lessons back into the secure development lifecycle.
Response and remediation targets
| 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 |
What we publish
- Security advisories — one per confirmed vulnerability, with CVSS v4.0 score and vector, affected components and remediation. Published at Security Advisory and indexed at CVE Index.
- CVE IDs and CVE Records — assigned and published under our CVE ID Assignment policy once our CNA authorization is in effect.
- Reporter credit — researchers who wish to be named are listed on Acknowledgements; our Responsible Disclosure Policy states the safe harbor we extend.
- Machine-readable feeds — advisories are also available as RSS.
Working with others
Our products include third-party components and are deployed next to equipment we do not make. Where an upstream supplier is itself a CNA, we notify it and defer first-refusal assignment under CNA Rule 4.2.16.6. We coordinate disclosure dates with reporters, with affected suppliers and, where required, with national CSIRTs and regulators.
Regulatory obligations that touch the PSIRT include the EU Cyber Resilience Act, NIS2 reporting duties, and China's MLPS regime; our regulatory contacts page lists the authorities we coordinate with.
Contact the PSIRT
- Product vulnerability reports: csirt@sigenergy.cloud or the report form — available 24×7. Encrypt sensitive details with our PGP key.
- Product security enquiries: psirt@sigenergy.com.
- Related pages: Product Security · Vulnerability Handling · CVE ID Assignment · CVE Index.
