CEH Wireless, IoT and Cloud Security Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Require strong passwords on the camera web interface.

  Why it's wrong here

  Requiring strong passwords on the camera's web interface primarily secures administrative access to the device's configuration settings. However, this measure does not encrypt the actual video, audio, or telemetry data streams transmitted from the camera to a server or monitoring station. Consequently, even with robust interface authentication, the sensitive communication payload remains vulnerable to passive eavesdropping or active tampering if the underlying network channel is unencrypted.

• ✗

  Use a site-to-site VPN between the cameras and the server.

  Why it's wrong here

  Implementing a site-to-site VPN typically involves establishing a secure tunnel between two networks, often requiring dedicated hardware or significant software configuration on network gateways. Many resource-constrained IoT cameras lack the processing power, memory, or firmware capabilities to act as VPN endpoints, making direct site-to-site VPN integration impractical or impossible. Furthermore, managing individual VPN tunnels for a large fleet of devices introduces considerable operational complexity and overhead.

• ✗

  Use certificate pinning to prevent man-in-the-middle attacks.

  Why it's wrong here

  Certificate pinning is an advanced security technique that enhances the trust model of TLS/SSL by hardcoding or pre-configuring specific server certificates or public keys within the client application. While effective at preventing sophisticated Man-in-the-Middle attacks by ensuring communication only occurs with known, legitimate servers, certificate pinning itself does not provide the fundamental encryption layer. It relies entirely on an existing TLS/SSL connection to establish the secure, encrypted channel; without TLS/SSL, pinning has no cryptographic context to operate within.

• ✓

  Implement TLS/SSL encryption for all camera communications.

  Why this is correct

  Implementing TLS/SSL (Transport Layer Security/Secure Sockets Layer) encryption for all camera communications establishes a robust, end-to-end secure channel. This protocol encrypts the entire data stream, including sensitive video feeds, audio, control commands, and metadata, protecting them from unauthorized interception, eavesdropping, and tampering as they traverse public or untrusted networks. TLS/SSL also provides server authentication, ensuring the camera communicates with the legitimate server, and data integrity verification, confirming the data has not been altered in transit.

Go deeper

Related to this question