← CRA Glossary
CVD & Vulnerability Management

Product Security Incident Response Team (PSIRT)

A Product Security Incident Response Team (PSIRT) is the dedicated function within a hardware or software vendor that receives vulnerability reports, investigates flaws in shipped products, coordinates fixes with engineering teams, and publishes security advisories for customers. A PSIRT protects the products an organisation sells, whereas a CSIRT protects internal corporate IT systems.

CVD & Vulnerability Management

Last updated 13 November 2026

Key takeaways

  1. A Product Security Incident Response Team (PSIRT) manages the vulnerability lifecycle for hardware and software products a vendor ships to customers.
  2. A PSIRT handles vulnerabilities in commercial or open-source products, whereas a CSIRT defends an organisation's internal corporate IT infrastructure.
  3. Established vendor teams such as Cisco PSIRT, Siemens ProductCERT, Fortinet PSIRT, Phoenix Contact PSIRT, and Adobe PSIRT publish coordinated advisories for customers.
  4. The FIRST PSIRT Services Framework defines core service areas covering vulnerability intake, triage, remediation coordination, and advisory disclosure.

What does a PSIRT do?

A Product Security Incident Response Team owns the end-to-end lifecycle of security vulnerabilities discovered in an organisation's hardware, firmware, or software products. External security researchers, customers, suppliers, and internal test teams submit vulnerability reports to the PSIRT through a published intake channel.

Once a report arrives, the PSIRT validates whether the issue is reproducible, scores severity using a standard such as CVSS, and coordinates with product engineering teams to build and test a security update. When a vulnerability affects a shared third-party component, the team coordinates embargo dates with upstream maintainers and peer vendors. At release, the PSIRT assigns or requests a CVE identifier and publishes a customer security advisory.

How does a PSIRT differ from a CSIRT?

A PSIRT secures products delivered to customers, whereas a CSIRT (Computer Security Incident Response Team) or SOC defends the organisation's own enterprise network, cloud accounts, and employee endpoints. Large technology and industrial vendors operate both teams side by side with separate playbooks.

DimensionPSIRTCSIRT
ScopeVulnerabilities in shipped hardware, firmware, and software productsSecurity incidents and intrusions in internal corporate IT systems
What it protectsCustomers, integrators, and downstream users of the vendor's productsThe organisation's own networks, data, employees, and infrastructure
Who reports to itExternal security researchers, customers, component suppliers, and CERTsInternal monitoring tools, employees, SOC analysts, and threat feeds
OutputsSecurity patches, CVE records, VEX statements, and public CSAF advisoriesIncident containment, forensic eradication, system recovery, and internal post-mortems
ExampleSiemens ProductCERT publishing a PLC firmware advisoryAn internal enterprise SOC containing a phishing intrusion

Examples of vendor PSIRTs

Hardware, enterprise software, and industrial automation manufacturers publish dedicated PSIRT portals with PGP keys, reporting policies, and searchable advisory feeds.

  • [Cisco PSIRT](https://sec.cloudapps.cisco.com/security/center/publicationListing.x) manages vulnerability reports and publishes CVRF and CSAF security advisories across Cisco networking, collaboration, and security products.
  • [Siemens ProductCERT](https://www.siemens.com/global/en/products/services/cert.html) coordinates vulnerability handling and publishes machine-readable CSAF advisories for Siemens industrial automation, energy, and building products.
  • [Fortinet PSIRT](https://www.fortiguard.com/psirt) triages vulnerability disclosures and releases FortiGuard security advisories across FortiOS and network security appliances.
  • [Phoenix Contact PSIRT](https://www.phoenixcontact.com/en-pc/company/compliance/psirt) handles coordinated vulnerability disclosure and publishes CSAF advisories for industrial controllers, switches, and power supplies.
  • [Adobe PSIRT](https://helpx.adobe.com/security.html) receives external researcher reports and publishes scheduled security bulletins across Creative Cloud, Document Cloud, and Experience Cloud software.

PSIRT maturity and the FIRST PSIRT Services Framework

The Forum of Incident Response and Security Teams publishes the FIRST PSIRT Services Framework, an open reference model used to design and benchmark product security teams. The framework groups capabilities into service areas including stakeholder ecosystem management, vulnerability information receipt, triage and root-cause analysis, remediation coordination, and incident disclosure.

New product security teams typically start with a published security.txt contact, a documented coordinated vulnerability disclosure policy, and a tracked triage queue. Mature teams add automated SBOM correlation, CVE Numbering Authority (CNA) operations, multi-party embargo coordination, and automated CSAF 2.0 advisory distribution.

PSIRT obligations under the EU Cyber Resilience Act

Regulation (EU) 2024/2847 (the EU Cyber Resilience Act) requires every manufacturer placing products with digital elements on the EU market to operate core PSIRT capabilities, even though the regulation text uses functional terms rather than the acronym PSIRT.

  • Intake and contact address. and require a coordinated vulnerability disclosure policy and a published contact address for receiving vulnerability reports.
  • Component tracking and remediation. and require manufacturers to maintain a machine-readable SBOM and remediate vulnerabilities without delay through security updates.
  • Public advisories. and require manufacturers to publish advisories describing fixed vulnerabilities, affected products, severity, and user remediation steps alongside free security updates.
  • Mandatory regulatory reporting. Since 11 September 2026, Article 14 requires manufacturers to submit an early warning within 24 hours, a notification within 72 hours, and a final report to ENISA and the coordinating national CSIRT for any actively exploited vulnerability or severe incident.
CRA reference:Article 14, Annex I Part II

Building a minimal PSIRT for small and medium manufacturers

Small and medium manufacturers can meet product security obligations without hiring a standalone department by assigning clear roles and documented procedures to existing engineering and compliance staff.

  1. Publish a single point of contact at /.well-known/security.txt and on a public vulnerability disclosure policy page.
  2. Set acknowledgement and triage targets defining who validates incoming reports and scores severity.
  3. Define an engineering escalation path linking product maintainers, release managers, and legal review for severe flaws.
  4. Prepare advisory and reporting templates so the team can publish customer advisories and meet the 24-hour Article 14 early warning clock when active exploitation occurs.
CRA reference: and , Article 14

Work through the CRA for each product in one workspace.

Classify each product, build the Annex VII technical file and prepare Article 14 notifications. The disclosure portal that receives vulnerability reports stays free.

Frequently asked

What is the difference between a PSIRT and a CSIRT?+

A PSIRT (Product Security Incident Response Team) investigates and fixes vulnerabilities in hardware and software products that an organisation builds and ships to customers. A CSIRT (Computer Security Incident Response Team) responds to cyberattacks and operational security incidents affecting the organisation's own internal IT infrastructure. National CSIRTs also act as public authorities that receive mandatory vulnerability notifications under laws such as the EU Cyber Resilience Act.

Does a small manufacturer need a dedicated full-time PSIRT?+

No. A single designated lead backed by engineering maintainers can perform the PSIRT role when the company maintains a public reporting contact, documented triage and escalation procedures, patch release workflows, and authority notification playbooks. Regulators and enterprise buyers evaluate documented capability and response speed rather than headcount.

How fast should a PSIRT acknowledge a vulnerability report?+

Industry frameworks such as ISO/IEC 29147 and the ENISA Coordinated Vulnerability Disclosure guidelines recommend acknowledging external vulnerability reports within a few business days, commonly 48 hours to 5 business days. Under CRA Article 14, a separate 24-hour statutory clock starts as soon as a manufacturer becomes aware that a vulnerability in its product is being actively exploited.

This definition is part of the EU Cyber Resilience Act guide, which explains Regulation (EU) 2024/2847 article by article.

Browse the full CRA Compliance Checklist

See how Product Security Incident Response Team (PSIRT) fits into your complete CRA compliance programme.

View checklists →