This statement is TRUE . When an administrator logs in to a device through the web UI over HTTPS , the device acts as the HTTPS server and presents a local certificate to the web browser during the TLS handshake. If this certificate is issued by a CA trusted by the browser , the browser can verify the certificate chain, confirm the identity of the device, and establish an encrypted session without certificate warning messages.
This process improves security in two important ways. First, it provides server identity authentication , which helps the administrator confirm that the browser is connected to the legitimate device rather than an impersonated or spoofed host. Second, once the certificate is trusted and the TLS session is established, the communication is encrypted and protected for integrity , which reduces the risk of eavesdropping, tampering, and man-in-the-middle attacks during administrator login.
If a trusted CA certificate is not used, administrators may see browser warnings and may not be able to reliably confirm the server identity. Therefore, configuring a CA-issued certificate for HTTPS management helps prevent malicious attacks and ensures more secure administrator access.