Express + expert help

View pricing →
Skip to main content

Practical template

OTA test evidence plan

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.

  • Device/hardware: [fill in]
  • Bootloader/image hashes: [fill in]
  • Platform/version: [fill in]
  • Trust anchors/partition map/signing policy: [fill in]
  • Safe test units and recovery method: [fill in]
TestDefined expected resultInput/configuration/hashRaw logs and observed stateActual pass/failReviewer
Correct signed image[fill in][fill in][fill in][fill in][fill in]
Altered payload/wrong signer[fill in][fill in][fill in][fill in][fill in]
Power loss at defined phases[fill in][fill in][fill in][fill in][fill in]
Failed first boot/recovery[fill in][fill in][fill in][fill in][fill in]
Older authorised image[fill in][fill in][fill in][fill in][fill in]
Automatic update default, opt-out and postponement[fill in][fill in][fill in][fill in][fill in]

Host demonstration, run separately on a development computer: original Ed25519 signature accepted; changed payload, wrong key and altered signature rejected. It tests the Node.js crypto API only, not OTA firmware, flash, boot, rollback or anti-rollback. No permanent key or device configuration is changed.

Cyber Resilience Act (Regulation (EU) 2024/2847) points covered by this plan, and gaps: Annex I, Part I, point (2)(c); Annex I, Part II, points (2), (7) and (8); Annex II, point 8: [fill in]

  • Failures/corrective actions: [fill in]
  • Security approval/date: [fill in]