Test 1-3

Here's a polished and structured version of TEST 1 under section 3.2 – Encryption of Wireless Communication Channels:

TEST 1

Test Case ID: BIS-3.2.1 Test Name: TC_TEST_ENCRYPTION_OF_WIRELESS_COMMUNICATION_CHANNELS_TEST

Objective:

To verify, in the presence of the OEM team, that all wireless communications initiated by the DUT are securely encrypted and adhere to the mutual authentication mechanisms documented by the vendor.

Tools Used:

  • Wireshark (for packet capture and analysis)

  • Wireless client or test terminal

  • OEM documentation/manuals

  • Aircrack-ng (optional, for passive traffic inspection)

Test Execution Steps:

  1. Set up a wireless test environment with the DUT and a test client, ensuring that the DUT is configured according to the vendor’s specifications.

  2. Review and follow the documented mutual authentication process (e.g., WPA2-Enterprise, EAP-TLS, certificate-based authentication).

  3. Attempt to initiate wireless communication:

    • With valid credentials – to ensure successful and secure connection.

    • With invalid/missing credentials – to validate enforcement of mutual authentication.

  4. Use Wireshark to monitor traffic and verify that:

    • All communication is encrypted (no readable payload).

    • Proper TLS/SSL or WPA2/3 handshakes occur.

  5. Attempt to capture and inspect the wireless packets to determine if any unencrypted or sensitive data is visible.

Expected Results for Pass:

  • Wireless communication is successfully established only with valid authentication credentials.

  • All traffic is encrypted; inspection tools fail to extract any plaintext or sensitive information.

  • Attempted communication without authentication fails.

  • Wireshark logs confirm encrypted payloads and secure handshakes.

Test Observations:

(To be filled after execution)

  • Type of authentication used: ___________

  • Encryption standard observed: ___________

  • Handshake protocol: ___________

  • Result of packet inspection: ___________

Evidence Provided:

  • Wireshark packet capture logs (PCAP)

  • Screenshots of successful/failed connection attempts

  • Authentication and encryption configuration snapshots

Test Case Result:

(Pass/Fail – to be determined after testing)

Here's a polished and structured version of TEST 2 under section 3.2 – Encryption of Wireless Communication Channels:

TEST 2

Test Case ID: BIS-3.2.2 Test Name: TC_TEST_ENCRYPTION_OF_WIRELESS_COMMUNICATION_CHANNELS_CODE**

Objective:

To identify and verify all security mechanisms implemented in the firmware for wireless communication through static code analysis, ensuring encryption protocols follow industry best practices.

Tools Used:

  • Static Analysis Tools (e.g., Fortify SCA, SonarQube, or Coverity)

  • Code Editor/IDE (e.g., VS Code, Eclipse)

  • OEM Documentation

  • Manual code walkthrough with OEM support

Test Execution Steps:

  1. Obtain the firmware source code from the OEM and set up the analysis environment.

  2. Review the modules related to wireless communication to identify any encryption-related functionality.

  3. Check for usage of secure encryption libraries (e.g., OpenSSL, mbedTLS, wolfSSL) and the implementation of cryptographic functions.

  4. Confirm the use of secure protocols such as:

    • WPA2/WPA3 for Wi-Fi security

    • TLS 1.2 or higher for encrypted sessions

    • AES for payload encryption

  5. Verify proper key management practices (e.g., ephemeral keys, no hardcoded keys).

  6. Document all findings and highlight any deprecated or insecure implementations.

Expected Results for Pass:

  • Code analysis confirms use of modern encryption standards (e.g., WPA2/WPA3, TLS 1.2/1.3).

  • No deprecated or weak algorithms (e.g., WEP, MD5) are found.

  • Secure encryption functions and libraries are consistently used.

  • Key management and certificate handling practices are secure and follow best practices.

Test Observations:

(To be filled after execution)

  • Encryption libraries identified: ___________

  • Protocols used: ___________

  • Any insecure functions found: Yes / No

  • Code sections reviewed: ___________

Evidence Provided:

  • Static analysis report

  • Code snippets/screenshots showing use of secure encryption

  • OEM attestation or review documentation

Test Case Result:

(Pass / Fail – to be filled post-review)

Here is the polished and structured version of TEST 3 under section 3.2 – Encryption of Wireless Communication Channels:

TEST 3

Test Case ID: BIS-3.2.3 Test Name: TC_TEST_ENCRYPTION_OF_WIRELESS_COMMUNICATION_CHANNELS_PROCESS**

Objective:

To verify that secure key management processes are implemented and followed throughout the encryption lifecycle of wireless communication, through a detailed audit of documentation and practices.

Tools Used:

  • OEM Key Lifecycle Documentation

  • Security Audit Checklist

  • Interviews with OEM security personnel (if applicable)

Test Execution Steps:

  1. Review vendor-provided documentation covering key management processes, including:

    • Key generation mechanisms

    • Secure key distribution techniques

    • Key storage methods (e.g., use of HSM, secure elements)

    • Key rotation frequency and mechanisms

    • Key revocation and expiry handling

  2. Conduct an audit of the actual key management processes implemented on the device:

    • Inspect configuration files, key storage methods, and update mechanisms

    • Validate implementation through logs or relevant system responses

  3. Cross-check the audit results with the documentation to ensure there are no deviations in practice.

  4. Assess whether secure key lifecycle management is consistently enforced across wireless communication modules.

Expected Results for Pass:

  • The documented key management process is implemented accurately without deviations.

  • Encryption keys are generated using secure algorithms and stored in protected areas.

  • Keys are rotated and revoked as per policy.

  • No exposure of keys through insecure channels, hardcoded values, or improper permissions.

Test Observations:

(To be filled post-execution)

  • Documented process version: ___________

  • Key generation method: ___________

  • Secure storage used: Yes / No

  • Rotation & revocation observed: Yes / No

  • Any deviation from SOP: Yes / No

Evidence Provided:

  • Vendor SOP documents

  • System logs showing key rotation/revocation

  • Screenshots or config file extracts demonstrating compliance

Test Case Result:

(Pass / Fail – to be filled after validation)

Overall Test Result:

(Pass / Fail – based on cumulative outcome of all 3.2 test cases)

Previous3.2 – Test Encryption of Wireless Communication ChannelsNext3.3 Assess Trusted Supply Chain for Critical Components

Last updated

Was this helpful?