Having a PSIRT at all and having a good PSIRT are different questions, and FIRST's PSIRT Maturity Document — scoring a team across three levels, Basic through Advanced — is the tool built to answer the second one. Published by FIRST's PSIRT Special Interest Group as a companion to the PSIRT Services Framework, it walks through the same service areas the Framework defines and scores each one across three levels — Basic, Intermediate and Advanced — so a team can see exactly which part of its process is holding back the rest.
Key takeaways
- Having a PSIRT at all and having a good PSIRT are different questions, and FIRST's PSIRT Maturity Document — scoring a team across three levels, Basic through Advanced — is the tool built to answer the second one.
- Annex 7 of the Maturity Document PDF closes with a sample checklist, read on 2026-11-10.
- a vulnerability disclosure policy, usually public.
- The PSIRT Services Framework v1.1 answers "what should a PSIRT be doing" — it lists the service areas and the Strategic/Tactical/Operational foundation underneath them.
What are the three PSIRT maturity levels?
| Level | FIRST's own tagline | What it covers |
|---|---|---|
| 1 — Basic | "The Beginning is a very fine place to start" | Executive sponsorship and a named team; a route for reports to arrive; a basic triage and analysis process; initial use of a scoring system such as CVSS |
| 2 — Intermediate | "I am reactive, but I've trained for it!" | Builds on Level 1 with a trained, more consistent process; stakeholder ecosystem management; a product/component inventory (a bill of materials); and tracked metrics on report volume and response time |
| 3 — Advanced | "Proactive...we're ready for anything (mostly)" | Builds on Levels 1-2 with proactive vulnerability discovery (not just reactive intake); deeper coordination with external researchers and industry peers; and integration of security feedback into the secure development lifecycle |
Each level is explicitly cumulative — Level 2 assumes Level 1's building blocks already work, and Level 3 assumes both lower levels are solid, so a team cannot skip the reactive basics and claim a "proactive" maturity score just because it runs a bug bounty programme without a working triage process underneath it.
The service areas it scores
The Maturity Document applies its three levels across the same service areas the PSIRT Services Framework defines: stakeholder ecosystem management, vulnerability discovery, vulnerability triage and analysis, remediation, vulnerability disclosure, and training and education. A PSIRT's overall maturity is not one single number — it is realistic, and common, for a team to be Advanced in triage and analysis while still Basic in proactive vulnerability discovery, and the document is built to surface that unevenness rather than hide it behind a single composite score.
What does FIRST's own checklist list at each level?
Annex 7 of the Maturity Document PDF closes with a sample checklist, read on 2026-11-10. It is the most compact view of what FIRST expects at each level. Condensed, by service area:
| Service area | Level 1 (Basic) | Level 2 (Intermediate) | Level 3 (Advanced) |
|---|---|---|---|
| Operational foundations | Executive sponsorship; identify stakeholders; budget; policies | Charter; organisational model; management and stakeholder support; staffing, resources and tools; understand branch and version support lifecycles; baseline metrics; product registry with dependency mapping | Organisational policies built out; cost of vulnerability management known |
| Stakeholder ecosystem management | — | Key internal and downstream stakeholders identified; incident communications and coordination | Direct engagement with the finder community; community engagement (for example joining FIRST); stakeholder metrics |
| Vulnerability discovery | Intake of vulnerability reports; a PSIRT e-mail address with a PGP key | A process for discovering unreported vulnerabilities | Monitoring for product component vulnerabilities; new vulnerabilities from feeds, forums and external sites; discovery metrics |
| Vulnerability triage and analysis | Defined intake process; internal workflows for qualification, triage and analysis | Finders who repeatedly send quality reports identified; internal reproduction capability | — |
| Remediation | Remediation options analysed; fix or mitigation documented | A formal security remedy management plan | Advanced incident handling; vulnerability release metrics |
| Vulnerability disclosure | CVE and CVSS adopted; communication templates; stakeholders informed; finders acknowledged | A system to notify stakeholders; vulnerability metrics | A playbook for stakeholder and industry coordination |
| Training and education | — | Training for PSIRT members; feedback mechanisms | Training for development teams; continuing education for all stakeholders |
Two placements matter for device makers. The product registry with dependency mapping, in practice an SBOM per product version, sits at Level 2; the Level 2 narrative calls it a "Product Manifest or Bill of Materials (BOM)". Monitoring of component vulnerabilities sits at Level 3. See firmware SBOM for how to build that registry from firmware images. The Level 2 narrative also suggests the Traffic Light Protocol for sharing information with partners.
Which policies and charter items come first?
The Level 1 chapter names five policies a new PSIRT could establish, next to ISO/IEC 29147 and ISO/IEC 30111:
- a vulnerability management policy (as covered in ISO/IEC 30111);
- an information handling policy (as covered in ISO/IEC 29147);
- a vulnerability scoring and prioritisation policy;
- a remediation service level agreement;
- a vulnerability disclosure policy, usually public.
On scoring, the document is direct: "choose your yardstick and then measure all things against it." It prefers CVSS, and a team using its own scale should be able to explain to customers why it is better. Annex 3 lists the usual charter items (mission statement, stakeholders, affiliation and sponsoring organisation, scope), and Annex 4 quotes mission statements from several large vendors' PSIRTs.
Where the template falls short of the CRA. Annex 6 offers sample policy statements, such as "Security vulnerabilities must be triaged within [#] days of receiving a report" and "The company will publicly disclose security vulnerabilities only when a remediation is available and customer action is required." For products sold in the EU, the second one is narrower than CRA Annex I Part II point (4). That point asks manufacturers to disclose fixed vulnerabilities once a security update is available, with a delay allowed only in duly justified cases until users have had the chance to patch.
Why this pairs with the Services Framework rather than replacing it
The PSIRT Services Framework v1.1 answers "what should a PSIRT be doing" — it lists the service areas and the Strategic/Tactical/Operational foundation underneath them. The Maturity Document answers "how well is the team doing it right now," using that same service-area structure as its scoring axis. A team setting up a PSIRT for the first time typically reads the Framework first to scope what it is building, then uses the Maturity Document to benchmark progress and plan the next investment — training, tooling or headcount — against whichever service area scores lowest.
How this fits regulatory vulnerability-handling duties
Neither the EU Cyber Resilience Act's Annex I Part II vulnerability-handling requirements nor ISO/IEC 29147 and 30111 names a FIRST maturity level as a compliance target — a product can be CRA-compliant without ever being formally scored against this document. What the levels are useful for is gap analysis: a team already building a CVD process against ISO/IEC 29147/30111 can map its current practice onto FIRST's three levels to spot where it is reactive-only (Level 1-2) versus where it has room to add proactive discovery and SDLC integration (Level 3), independent of what any single regulation strictly requires.
How do the levels line up with CRA Annex I Part II?
Not one to one. FIRST does not map its document to the Cyber Resilience Act; the table below is our reading of the Annex 7 checklist against the CRA text (see CRA Annex I explained for the full annex). Service numbers come from the PSIRT Services Framework v1.1.
| CRA provision (condensed) | Closest FIRST service | Where Annex 7 places it |
|---|---|---|
| Part II (1): identify and document components, including an SBOM | Operational foundations; 2.3 Monitoring for Product Component Vulnerabilities | Registry: Level 2. Component monitoring: Level 3 |
| Part II (2): remediate without delay | 4.2 Remediation; 4.1 Remedy Release Management Plan | Level 1, formalised at Level 2 |
| Part II (3): regular security tests and reviews | 2.2 Identify Unreported Vulnerabilities | Level 2 |
| Part II (4): disclose fixed vulnerabilities | 5.3 Disclosure | Level 1 |
| Part II (5): coordinated vulnerability disclosure policy | Operational foundations (policies) | Level 1 |
| Part II (6): contact address, including for third-party components | 2.1 Intake of Vulnerability Reporting | Level 1 |
| Part II (7): secure update distribution | 4.2 Remediation | Not on the checklist; the Level 3 narrative describes routine delivery, including over the air |
| Part II (8): free updates with advisory messages | 5.1 Notification | Level 1, with a notification system at Level 2 |
| Article 13(6): report component flaws upstream and share the fix | Stakeholder ecosystem management | Level 3 narrative: relationships with upstream providers |
The pattern: a team that meets only FIRST's Level 1 still misses CRA baseline duties that FIRST files under Level 2 or 3, above all the SBOM and component monitoring. Regulator reporting within 24 and 72 hours under Article 14 is outside the document altogether; see CRA 24h/72h reporting.
Worked example: how would a small device maker self-assess?
A hypothetical 60-person maker of EV wall chargers, not a customer case, rates itself against Annex 7, one service area at a time:
| Service area | Evidence the team finds | Level reached | Next action |
|---|---|---|---|
| Operational foundations | Written mandate from the CTO; disclosure policy; no budget line | Level 1, partly (budget missing) | Agree a budget; write a charter (a Level 2 item) |
| Stakeholder ecosystem | Support forwards reports ad hoc; no list of installers and distributors | Below Level 2 | List the downstream stakeholders who must be told |
| Vulnerability discovery | security.txt, security@ with a PGP key; SBOM per release from the build system | Level 1, plus the Level 2 registry | Add component monitoring, which the CRA expects |
| Triage and analysis | CVSS used, but no written workflow | Level 1, partly | Write the intake and triage workflow |
| Remediation | Fixes ship in the next feature release | Level 1 | Formal remedy plan with separate security updates |
| Vulnerability disclosure | Release notes say "security fixes" with no CVE IDs | Below Level 1 | Advisories with CVE and CVSS, templates, finder credit |
| Training and education | None | — | Train PSIRT members (a Level 2 item) |
The result is a profile, not a single number. The team fixes the two Level 1 gaps first, disclosure and triage, because everything else depends on them. Its strongest area, discovery, came from SBOM work it had already done for the CRA.
What does the Maturity Document not measure?
FIRST draws the limits itself in the preface. The document does not cover capacity, meaning "the number of vulnerabilities and incidents a team can manage simultaneously," and it is not a maturity model such as SIM3, which indicates how well a team governs, documents, performs and measures its functions. It uses "maturity" to describe a profile of a team and the capabilities it provides to stakeholders.
- No scoring scale. The levels are narrative use cases, and Annex 7 is called a sample checklist. Any score is your own self-assessment.
- No certification. The document defines no audit or certificate against the levels.
- A 2019 text. The PDF cover is dated 2019 and points to the Services Framework, so later duties such as CRA reporting are not covered.
- No external benchmark. It does not tell you how your team compares with peers, or how many people you need.
What a PSIRT should do with this document
Score each service area separately, not the team as a whole — a single composite "we are Level 2" statement hides exactly the gaps the document is designed to expose. Treat Level 1 as the non-negotiable floor, not an early milestone to rush past. A named owner, a working intake route and a basic triage process are what everything else depends on. Use the lowest-scoring service area to prioritise the next investment, whether that is training, a bill-of-materials tool, or a formal stakeholder-coordination process for third-party components. Re-score periodically, especially after a regulatory deadline (such as the CRA's reporting obligations) forces process changes — maturity documents are meant to be revisited, not scored once and filed away. Pair the self-assessment with a concrete build-out planSee how to set up a PSIRT for a hardware product company for the step-by-step version of reaching a working Level 1, and the CVD process guide for how the underlying ISO processes map onto these same service areas.
SoftWSP can run a PSIRT maturity assessment against these three levels and help prioritise the gap that is actually slowing your team down: see PSIRT services.
Put this guide to work
Frequently asked questions
What is the FIRST PSIRT Maturity Document?
It is a companion document to FIRST's PSIRT Services Framework, published by FIRST's PSIRT Special Interest Group, that gives a product security incident response team a way to self-assess which of three maturity levels its current practice sits at, service area by service area, rather than treating 'do we have a PSIRT' as a single yes/no question.
What are the three PSIRT maturity levels?
Level 1, titled 'The Beginning is a very fine place to start,' covers the foundational building blocks: executive sponsorship, a named team, a basic vulnerability intake and triage process, and first use of a scoring system such as CVSS. Level 2, 'I am reactive, but I've trained for it!,' assumes Level 1 is in place and adds a trained, more formal process, a product/component inventory such as a bill of materials, and tracked metrics. Level 3, 'Proactive...we're ready for anything (mostly),' assumes Levels 1 and 2 and adds proactive vulnerability discovery, deeper external stakeholder coordination, and integration with the secure development lifecycle.
How does the Maturity Document relate to the PSIRT Services Framework?
The Services Framework (current version 1.1) defines what a PSIRT does, organised into service areas such as stakeholder ecosystem management, vulnerability discovery, triage and analysis, remediation, disclosure, and training and education. The Maturity Document applies that same set of service areas and asks how well-developed each one currently is, levelled from Basic through Advanced, so the two documents are meant to be read together rather than as alternatives.
Does CRA or ISO/IEC 29147/30111 require a specific FIRST maturity level?
No. Neither the EU Cyber Resilience Act nor ISO/IEC 29147 (disclosure) or ISO/IEC 30111 (vulnerability handling) names FIRST's maturity levels or requires a specific score. The Maturity Document is a voluntary self-assessment tool a PSIRT can use to plan its own improvement; meeting CRA's Annex I Part II vulnerability-handling points or the ISO processes does not require citing a particular FIRST maturity level, though the underlying practices overlap heavily.
Can a small hardware company realistically reach Level 1?
Yes — Level 1 is deliberately scoped to what a small team can stand up: a named owner, a way to receive reports, a basic triage and scoring process, and a route to ship a fix and an advisory. FIRST's own framing of Level 1, 'the beginning is a very fine place to start,' signals it is meant as an achievable starting point, not an aspirational end state; see our guide on setting up a PSIRT for a hardware company for the concrete steps that get a small team to that point.
Sources
- FIRST: Product Security Incident Response Team (PSIRT) Maturity Document
- FIRST: Product Security Incident Response Team (PSIRT) Maturity Document (PDF)
- FIRST: PSIRT Services Framework, Version 1.1
- FIRST: PSIRT Special Interest Group (SIG)
- ISO: ISO/IEC 29147:2018 — Vulnerability disclosure (catalogue record)
- Regulation (EU) 2024/2847 (Cyber Resilience Act), Article 13 and Annex I Part II, EUR-Lex
About this guide
SoftWSP Firmware Security Desk
Covers the PSIRT & disclosure cluster: 15 guides.

In this cluster
Questions about this page?
