Product Security

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

DimensionCSIRTPSIRT
ScopeIncidents in Sigenergy's own networks, systems and dataVulnerabilities in the products and services we ship
ConstituencyEmployees and internal infrastructureCustomers, installers and asset owners
Typical inputsAlerts, logs, user reports, threat intelligenceResearcher reports, third-party component advisories, internal testing, coordinators
Typical outputsContained incidents, recovered systems, post-incident reviewsFixed releases, security advisories, CVE records, customer notifications
Clock startsWhen an incident is detectedWhen a vulnerability is reported or published
Typical ownerCISO or IT securityProduct security and engineering
FrameworkFIRST CSIRT Services FrameworkFIRST PSIRT Services Framework
StandardsISO/IEC 27035 (incident management)ISO/IEC 29147 (disclosure) and ISO/IEC 30111 (handling)
The two teams do not work in isolation. National CSIRTs and coordinators are often how a manufacturer first learns about a vulnerability, and an incident that reaches a build system can turn an internal event into a product one.

How our PSIRT works

  1. 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.
  2. Triage and validation. We reproduce the issue in a controlled environment, confirm the affected products and versions, and check for duplicates.
  3. Severity and priority. We score with CVSS v4.0 and assign a severity, which sets the remediation timeline and the communications cadence.
  4. 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.
  5. 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.
  6. 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.
  7. 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

SeverityInitial responseFix targetStatus updates
CriticalWithin 24 hoursAs soon as possible, target 7 daysDaily
HighWithin 3 business daysTarget 30 daysWeekly
MediumWithin 5 business daysTarget 90 daysEvery two weeks
LowWithin 10 business daysNext scheduled releasePer release
These targets match our published vulnerability handling process and service level agreement. They are service objectives; exceptional cases are communicated to the reporter.

What we publish

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