Practical template
Embedded firmware VEX decision record
Use this template with your own product details and evidence. Copy the text into your document to complete the fields and add rows as needed.
- Product/version/hash: [fill in]
- Component/provenance: [fill in]
- Issue/source: [fill in]
- Analyst/date: [fill in]
- Evidence known at decision time: [fill in]
| Question | Evidence reference | Finding/uncertainty |
|---|---|---|
| Correct component/version match? | [fill in] | [fill in] |
| Affected feature/code present? | [fill in] | [fill in] |
| Reachable in relevant configurations? | [fill in] | [fill in] |
| Mitigation/corrected release verified? | [fill in] | [fill in] |
- State and format-specific vocabulary: [fill in]
- Reason/justification: [fill in]
- Affected component references verified: [fill in]
- Product distribution scope: [fill in]
- Reassessment triggers: [fill in]
- Reviewer/date: [fill in]
- Reporting assessment handled separately: [fill in]
DEMO-VULN-001 in the supplied JSON is fictional and remains in_triage. DEMO-VULN-002, shown only in the article, is fictional as well and refers to evidence that does not exist. No exploitability result is established.
Read the accompanying guide
CycloneDX VEX for Embedded Firmware: a Worked Synthetic Example