Template library
TRUST ATLAS WORKSHEET

Vulnerability handling procedure

EU Cyber Resilience Act · Step 2 · Build security into design and support
Who prepares it
Product security + engineering
When to prepare it
Before release and throughout the support period

Worked example

This example uses fictional details. Use the same fields with evidence from your work.

Intake
Product security mailbox and monitored vulnerability disclosure form
Triage
Identify affected releases and preserve reproduction details in the restricted case.
Escalation
Page product security for signs of active exploitation. Regulatory affairs checks reporting triggers.
Release and validation
Engineer builds a fix, QA runs exploit regression and service tests.
Disclosure and closure
Publish an approved advisory, record receipts and update the affected-version register.

Gather first

  • Product inventory and support dates
  • Disclosure contact and criteria
  • Incident, patch and regulator workflows

How to prepare it

  1. Define intake, the acknowledgement owner and how to reproduce the report safely. Record product version, technical impact and evidence of exploitation.
  2. Set severity, escalation and reporting decision rules. Assign ownership of mitigation, customer updates and any separate legal clocks.
  3. Run a mock report through disclosure and patch release. Verify deadlines, authority contact and customer instructions before adopting the procedure.

Review

The workflow routes a report to a named decision maker even while facts are incomplete.

Handoff

Provide the procedure to support, engineering, security and regulatory owners before the product enters service.

Keyboard shortcuts

⌘K or /
Search everything
?
This list
g h
Home
g l
Guide library
g f
Find my path
g t
Templates
g p
Playbooks
g w
My workspace
g d
Deadline calendar
g c
Regulatory changes