2.10 – Test Anti-Rollback Firmware Protection:

2.10 – Test Anti-Rollback Firmware Protection

Requirement Description

Verify that the device cannot be downgraded to old versions (anti-rollback) of valid firmware.

---

DUT Confirmation Details

(To be filled by OEM/vendor team) Example:

• Device Name: [Insert Name]

• Model Number: [Insert Model No.]

• Manufacturer: [Insert Manufacturer Name]

---

DUT Software Details

• Firmware Version Tested: [Insert Version]

• Build Date: [Insert Date]

• Secure Boot Enabled: Yes/No

• Anti-Rollback Mechanism Implemented: Yes/No

---

Hash Checksum Verification for DUT’s Software Image

• Checksum Algorithm: SHA-256

• Verified Hash: [Insert Hash]

---

DUT Configuration

Include relevant configuration parameters related to firmware security, e.g.:

• Secure Boot: Enabled

• Digital Signature Verification: Enabled

• Firmware Version Lock: Configured

---

Pre-Conditions

The vendor shall provide the following:

• Documentation explaining the secure firmware upgrade process, including:

  • Keys used and their lifecycle management

  • Signature validation workflow

  • Any anti-rollback logic or implementation details

---

Test Plan

• Total Number of Test Cases: 1

---

Test-bed Diagram with Interfaces and IPs:

(Attach or embed relevant test-bed network diagram showing connection between test system and DUT. Include IP addresses or interface details used for upgrade attempts.)