3.5 Confirm Use of Non-Proprietary Network Protocols

3.5 – Confirm Use of Non-Proprietary Network Protocols

Requirement Description

Verify that no proprietary network protocols are used in the device. If proprietary protocols are present, complete implementation details and the source code shall be provided for assessment.

---

DUT Confirmation Details

(To be provided by the vendor/OEM)

• Device Name: [Insert Device Name]

• Model Number: [Insert Model Number]

• Manufacturer: [Insert Manufacturer Name]

---

DUT Software Details

• Firmware Version: [Insert Version]

• Operating System/Platform: [e.g., Linux Kernel vX, Embedded RTOS]

• Build ID/Release Date: [Insert Details]

---

Hash Checksum Verification for DUT’s Software Image

• Hashing Algorithm Used: SHA-256

• Verified Checksum: [Insert Checksum]

• Integrity Status: Verified / Not Verified

---

DUT Configuration

• Network Interfaces: [e.g., Ethernet, Wi-Fi, Cellular]

• Protocol Stack Used: [e.g., TCP/IP, MQTT, HTTP/HTTPS, etc.]

• Security Protocols: [e.g., TLS 1.2, SSH, etc.]

---

Pre-Conditions

The vendor shall provide the following:

• A detailed document listing all network protocols used in the firmware/device

• For any proprietary protocol, complete documentation including:

  • Functional overview

  • Security controls

  • Source code or binaries for assessment

---

Test Plan

• Total Number of Test Cases: 1

• Validation Method:

  • Documentation review

  • Optional: Traffic analysis using tools such as Wireshark to detect non-standard protocol usage

---

Test-bed Diagram with Interfaces and IP Addresses

(Attach or refer to a network diagram showing the DUT, test interfaces, IP assignments, and capturing system if applicable. This is used for protocol behavior validation during active testing.)