SBOM and Vulnerability Handling: Parts List, Intake, Fix-and-Notify, Ready for EU CRA Reports

Project & Development

SBOM and Vulnerability Handling: Parts List, Intake, Fix-and-Notify, Ready for EU CRA Reports

Advanced | 4 whiteboard pages · Task board: 4 columns (4 parent tasks, 12 subtasks)

Advanced: Assumes you know the technical terms and methods, and the steps are only outlined. Work through it on your own, guided by decision criteria and points to check.

From September 2026 the EU Cyber Resilience Act (CRA) requires an early warning within 24 hours and a notification within 72 hours of learning of an exploited vulnerability. Severe incidents follow suit; both end with a final report. This template helps software and device makers set per-product SBOMs (software bills of materials), an intake for outside vulnerability reports, a promise to fix and tell users, and who files reports. It also records per-product SBOM update triggers and owners. Recording when you became aware and naming who sends each early warning is the key to the short deadlines. Check the final report deadline in Article 14 of Regulation (EU) 2024/2847 and the latest guidance. Pitfalls, each with what happens, how to check and a fix: an SBOM never updated after shipping, a personal email as the only contact, fixes users never hear about, and no one deciding EU scope. The whiteboard has 4 pages; the task board has 4 columns, 4 parent tasks and 12 subtasks.

0 Likes 0 Copies Author: WeProcess
SBOM vulnerability handling Cyber Resilience Act product security software bill of materials
Sign up free and use this template

Once you have a free account, you can copy this template from the marketplace

Whiteboard preview

Read the whiteboard text as plain text

SBOM and Vulnerability Handling Board

How to use (4 pages): ① On page 1, set the goal and list parts and SBOM per product (boards①–⑤) → ② On page 2, set the intake flow and contact policy, check pitfalls (boards⑥–⑩) → ③ On page 3, rank products, decide EU scope and reporting owner (boards⑪⑫) → ④ On page 4, set CRA reporting, SBOM updates and the notice template (boards⑬–⑮)

1/4 List products and parts

① Goal and scope (start writing here)

  • Why we are deciding this e.g. Be able to fix and notify from the moment we learn of a vulnerability, even when owners change
  • Scope e.g. 3 products on sale (a business app, a gateway device, a mobile app). Products past support go in a separate table
  • Timeline and who takes part e.g. Decide in 4 weeks. One person each from development, quality, support and legal

② Parts and SBOM per product (list the products in scope of ①)

Parts (own, external) SBOM status and date SBOM owner Recipients
Product A e.g. Business app. 12 own, 85 external e.g. Yes, but not updated for the last three releases e.g. Dev lead (deputy is quality) e.g. Corporate customers in Japan and the EU
Product B e.g. Gateway device. 5 own, 40 external (including the OS) e.g. None e.g. TBD e.g. Companies via EU resellers
Product C e.g. Mobile app. 8 own, 60 external e.g. Yes. Rebuilt at every release e.g. App team e.g. Consumers through each country's store
Product D e.g. Shared internal component. Not counted e.g. None e.g. No owner e.g. Built into products A to C

③ Own parts (what we wrote ourselves)

  • e.g. Login, pricing calculation, device control
  • Write how versions are numbered and where the source lives
  • e.g. A version per release. Source in the internal repository

④ External parts (open source, bought-in)

  • e.g. A logging library, a crypto component, the device OS
  • For each part, write the supplier and whether maintenance continues
  • e.g. 2 parts whose supplier has not updated them in over a year

⑤ Recipients (who receives the product)

  • e.g. 120 corporate customers in Japan, 2 EU resellers
  • Write who is told about fixes and how
  • e.g. A notice page on the product site, an email to resellers

2/4 Set intake and fix flow

⑥ From a vulnerability report on a product in ② to the record

  1. Intake Receive the report and acknowledge it e.g. Log the date and time at the shared inbox and acknowledge within 2 business days. Reports of exploitation go to Confirm the same day
  2. Confirm Decide the affected products and versions e.g. Search the SBOM in ② for the part version. If an EU product from ⑫ is being exploited, go to the reports in ⑬
  3. Fix Build the fix and set a release date e.g. Release fixes starting with the biggest impact and tell the reporter the date
  4. Notify Tell users and the reporter e.g. Send the affected versions, fixed version and user actions using the notice in ⑮
  5. Record Keep the history and fix the SBOM e.g. Keep the date received, the decision and the version released, and update the date in the table in ②

⑦ Intake contact policy (rules for Intake and Notify in ⑥)

Current state Chosen policy Owner and review
Contact address e.g. One person's email e.g. Publish a shared inbox on the product site e.g. Support lead, every 6 months
Acknowledgement e.g. Not decided e.g. Acknowledge within 2 business days e.g. Inbox duty (2 people, weekly rotation)
Disclosure timing e.g. Decided case by case e.g. Publish after the fix is released. Align the date with the reporter e.g. Quality lead
Agreement with reporter e.g. None e.g. Report progress every 2 weeks. Ask the person before naming them e.g. Inbox duty

⑧ Pitfall: the SBOM is never updated

  • What happens, e.g. A new vulnerability appears and you cannot say which product and version contain it
  • How to check, e.g. Compare the update date in ② with the last release date
  • How to prevent, e.g. Add "Rebuild the SBOM" to the release steps

⑨ Pitfall: the contact is a personal email

  • What happens, e.g. A transfer or leave means reports go unseen and replies stall for weeks
  • How to check, e.g. Find out whose inbox the contact on the product site reaches
  • How to prevent, e.g. Switch to a shared inbox and put at least 2 people on duty in ⑦

⑩ Pitfall: no notice after the fix

  • What happens, e.g. Users keep running old versions and never hear about the fix
  • How to check, e.g. Match the past year of fixes against the notices you sent
  • How to prevent, e.g. Do not close the record until Notify in ⑥ is done

3/4 Decide scope and deadlines

⑪ Plot the products in ② (impact by number of users)

Vertical axis: Impact (higher = larger) / Horizontal axis: Number of users (further right = more)

  • High impact, few users e.g. A factory device. Set up the SBOM and contact first, and decide a notice route per customer
  • Top priority e.g. The business app. Update the SBOM every release and name the reporting owner and deputy first
  • Later e.g. A shared internal component. Link it in the table in ② to the products it is built into
  • Firm up the notice route e.g. The mobile app. Set up the fix release steps and the notice template first

⑫ EU scope and reporting owner for the products in ⑪ (pitfall: nobody decides)

For the EU (decided by) Evidence checked Reporting owner, deputy
Product A e.g. For the EU (legal decided. EU customers exist) e.g. Territories in the contract. Check scope conditions in the latest guidance e.g. Quality lead (deputy is dev lead)
Product B e.g. For the EU (distributed through resellers) e.g. Reseller contract and shipment records e.g. TBD. Decide by day 3
Product C e.g. TBD (checking the store's distribution regions) e.g. The store's distribution settings screen e.g. App team
Pitfall check What happens, e.g. Exploitation is found in the EU and nobody files the report How to check, e.g. See whether every product row has the name of who decided How to prevent, e.g. Add an EU-or-not field at the planning stage of new products

4/4 Run reporting and updates

⑬ The 3 CRA reporting stages (when the owner in ⑫ learns of an exploited vulnerability or severe incident)

  1. Early warning e.g. Within 24 hours of becoming aware, send the first notice through ENISA's reporting channel (reaches the national coordinating CSIRT and ENISA at the same time). Record the time you became aware
  2. Notification e.g. Within 72 hours of becoming aware, send more detail than the early warning. Check the required items in the latest guidance
  3. Final report e.g. For an exploited vulnerability, within 14 days of a fix or mitigation being available. For a severe incident, within 1 month of the notification. Check Article 14 of Regulation (EU) 2024/2847

⑭ SBOM update schedule (keep the table in ② from going stale)

Update trigger Next rebuild How to check
Product A e.g. Every release e.g. Next release (Friday of week 2) e.g. Release records and SBOM update dates line up
Product B e.g. Every device firmware update e.g. Next firmware update (early next month) e.g. Every shipped version has an SBOM
Product C e.g. Every store release e.g. The next store release e.g. Match the store version number to the SBOM version
All products e.g. Once a month, compare external parts with published vulnerability information e.g. First Monday of each month e.g. Record the date and result of the comparison

⑮ Notice template for users (used in Notify in ⑥)

  • What happened e.g. A vulnerability was found in an external part used in versions of product A earlier than 3.2
  • What users should do e.g. Update to 3.2.1. The update steps are on the notice page of the product site
  • Contact and next update e.g. Contact the shared inbox. A follow-up will appear on the same page within 2 weeks

Task board contents

Not started 16 items

Map products, parts

On page 1, set the goal and the products in scope, then tabulate parts count, SBOM status, owner and recipients per product. This product list is the input for all the work on later pages. Press Ctrl+F (⌘F on Mac) and type 3/4 to jump to page 3.

3 products + owners

Open the register of products on sale (shipments or contracts) and write product names and owners in the 3 rows of the table on board ②. Write TBD for a product with no owner and you are done; no need to count parts yet.

Check parts, SBOMs

In the remaining cells of board ②, write the number of own and external parts, SBOM status and update date, and recipients. Where you do not know, write who to ask and you are done.

Fill the 3 frames

On boards ③–⑤, write own parts, external parts and recipients. You are done once board ⑤ names who is told about fixes and how.

Set intake flow

On page 2, set the five stages from receiving a vulnerability report to recording it and the contact policy, then check the 3 pitfalls. Reporting deadlines are short, so without a defined intake you will miss the reports on page 4.

Write the 5 stages

On board ⑥, write who does what at each of the 5 stages. You are done once you have written the branch point that sends exploited cases to the reports on board ⑬.

Set contact policy

In the table on board ⑦, write the current state and chosen policy for contact address, acknowledgement, disclosure timing and agreement with reporters. You are done once the contact address is a shared inbox.

Check 3 pitfalls

On boards ⑧–⑩, rewrite what happens, how to check and one way to prevent it for your situation. You are done once the prevention notes name an owner.

Scope and deadlines

On page 3, rank the products from board ② by impact and number of users, then decide per product whether it is for the EU and who reports. Start from the highest-priority products to prepare the reports and SBOM updates on page 4.

Plot on 4 quadrants

Place the products from board ② on board ⑪, and make those in the high-impact, many-users quadrant the top priority. You are done once every product sits in a quadrant.

Judge EU scope

In the table on board ⑫, write per product whether it is for the EU, who judged it and the evidence. Check the detailed scope conditions in the latest guidance.

Name report owners

In the reporting owner and deputy column of board ⑫, write an owner and a deputy for each EU product. You are done once you have also filled in the pitfall in the last row.

Run reports, SBOM

On page 4, set owners and deadlines for the 3 CRA reporting stages, the SBOM update schedule and the notice template for users. Once decided, move the task to In operation and review every six months.

Check the 3 stages

Check the deadlines of the 3 stages on board ⑬ against Article 14 of Regulation (EU) 2024/2847 and the latest guidance, and decide who records the time of awareness. Reports are filed by the owner and deputy set on board ⑫.

Plan SBOM updates

In the table on board ⑭, write per product the update trigger, next rebuild date and how to check (the owner is the SBOM owner set on board ②). You are done once you rebuild the SBOM once at the next release.

Draft the notice

Using the 3 items on board ⑮, build the notice template for users. You are done once you have drafted it with one past fix as the example.

Deciding 0 items

Internal review 0 items

In operation 0 items

← Back to templates

Preview mode SBOM and Vulnerability Handling: Parts List, Intake, Fix-and-Notify, Ready for EU CRA Reports

Whiteboard preview

① Goal and scope (start writing here) ② Parts and SBOM per product (list th... ③ Own parts (what we wrote ourselves) ④ External parts (open source, bought... ⑤ Recipients (who receives the product) ⑥ From a vulnerability report on a pr... ⑦ Intake contact policy (rules for In... ⑧ Pitfall: the SBOM is never updated ⑨ Pitfall: the contact is a personal ... ⑩ Pitfall: no notice after the fix ⑪ Plot the products in ② (impact by n... High impact, few users Top priority Later Firm up the notice route ⑫ EU scope and reporting owner for th... ⑭ SBOM update schedule (keep the tabl... ⑮ Notice template for users (used in ... SBOM and Vulnerab... How to use (4 pag... Goal and promise ... Decisions and policy Pitfalls and gaps How to check and ... 1/4 List products and... Ctrl+F / ⌘F : 2/4... → 2/4 2/4 Set intake and fi... ↙ 3/4 Why we are deciding thise.g. Be able to fix and notify from the moment we learn of a vulnerability, even when owners change Scopee.g. 3 products on sale (a business app, a gateway device, a mobile app). Products past support go in a separate table Timeline and who takes parte.g. Decide in 4 weeks. One person each from development, quality, support and legal Parts (own, exter... SBOM status and date SBOM owner Recipients Product A e.g. Business app. 12 own, 85 external e.g. Yes, but not updated for the last three releases e.g. Dev lead (deputy is quality) e.g. Corporate customers in Japan and the EU Product B e.g. Gateway device. 5 own, 40 external (including the OS) e.g. None e.g. TBD e.g. Companies via EU resellers Product C e.g. Mobile app. 8 own, 60 external e.g. Yes. Rebuilt at every release e.g. App team e.g. Consumers through each country's store Product D e.g. Shared internal component. Not counted e.g. None e.g. No owner e.g. Built into products A to C e.g. Login, pricing calculation, device control Write how versions are numbered and where the source lives e.g. A version per release. Source in the internal repository e.g. A logging library, a crypto component, the device OS For each part, write the supplier and whether maintenance continues e.g. 2 parts whose supplier has not updated them in over a year e.g. 120 corporate customers in Japan, 2 EU resellers Write who is told about fixes and how e.g. A notice page on the product site, an email to resellers IntakeReceive the report and acknowledge ite.g. Log the date and time at the shared inbox and acknowledge within 2 business days. Reports of exploitation go to Confirm the same day ConfirmDecide the affected products and versionse.g. Search the SBOM in ② for the part version. If an EU product from ⑫ is being exploited, go to the reports in ⑬ FixBuild the fix and set a release datee.g. Release fixes starting with the biggest impact and tell the reporter the date NotifyTell users and the reportere.g. Send the affected versions, fixed version and user actions using the notice in ⑮ RecordKeep the history and fix the SBOMe.g. Keep the date received, the decision and the version released, and update the date in the table in ② Current state Chosen policy Owner and review Contact address e.g. One person's email e.g. Publish a shared inbox on the product site e.g. Support lead, every 6 months Acknowledgement e.g. Not decided e.g. Acknowledge within 2 business days e.g. Inbox duty (2 people, weekly rotation) Disclosure timing e.g. Decided case by case e.g. Publish after the fix is released. Align the date with the reporter e.g. Quality lead Agreement with re... e.g. None e.g. Report progress every 2 weeks. Ask the person before naming them e.g. Inbox duty What happens, e.g. A new vulnerability appears and you cannot say which product and version contain it How to check, e.g. Compare the update date in ② with the last release date How to prevent, e.g. Add "Rebuild the SBOM" to the release steps What happens, e.g. A transfer or leave means reports go unseen and replies stall for weeks How to check, e.g. Find out whose inbox the contact on the product site reaches How to prevent, e.g. Switch to a shared inbox and put at least 2 people on duty in ⑦ What happens, e.g. Users keep running old versions and never hear about the fix How to check, e.g. Match the past year of fixes against the notices you sent How to prevent, e.g. Do not close the record until Notify in ⑥ is done 3/4 Decide scope and ... → 4/4 4/4 Run reporting and... Vertical axis: Im... e.g. A factory device. Set up the SBOM and contact first, and decide a notice route per customer e.g. The business app. Update the SBOM every release and name the reporting owner and deputy first e.g. A shared internal component. Link it in the table in ② to the products it is built into e.g. The mobile app. Set up the fix release steps and the notice template first For the EU (decid... Evidence checked Reporting owner, ... Product A e.g. For the EU (legal decided. EU customers exist) e.g. Territories in the contract. Check scope conditions in the latest guidance e.g. Quality lead (deputy is dev lead) Product B e.g. For the EU (distributed through resellers) e.g. Reseller contract and shipment records e.g. TBD. Decide by day 3 Product C e.g. TBD (checking the store's distribution regions) e.g. The store's distribution settings screen e.g. App team Pitfall check What happens, e.g. Exploitation is found in the EU and nobody files the report How to check, e.g. See whether every product row has the name of who decided How to prevent, e.g. Add an EU-or-not field at the planning stage of new products ⑬ The 3 CRA repor... Early warning e.g. Within 24 hours of becoming aware, send the first notice through ENISA's reporting channel (reaches the national coordinating CSIRT and ENISA at the same time). Record the time you became aware Notification e.g. Within 72 hours of becoming aware, send more detail than the early warning. Check the required items in the latest guidance Final report e.g. For an exploited vulnerability, within 14 days of a fix or mitigation being available. For a severe incident, within 1 month of the notification. Check Article 14 of Regulation (EU) 2024/2847 Update trigger Next rebuild How to check Product A e.g. Every release e.g. Next release (Friday of week 2) e.g. Release records and SBOM update dates line up Product B e.g. Every device firmware update e.g. Next firmware update (early next month) e.g. Every shipped version has an SBOM Product C e.g. Every store release e.g. The next store release e.g. Match the store version number to the SBOM version All products e.g. Once a month, compare external parts with published vulnerability information e.g. First Monday of each month e.g. Record the date and result of the comparison What happenede.g. A vulnerability was found in an external part used in versions of product A earlier than 3.2 What users should doe.g. Update to 3.2.1. The update steps are on the notice page of the product site Contact and next updatee.g. Contact the shared inbox. A follow-up will appear on the same page within 2 weeks → 2/4 Set intake and fi... ↙ 3/4 Decide scope and ... → 4/4 Run reporting and...
100%

Drag to move, scroll to zoom