What must you ensure when enabling HTTPS for remote WebFig access besides enabling the service?

• A. Disable HTTPS.
• B. Have a valid certificate and proper firewall rules.
• C. Disable firewall.
• D. Use a self-signed certificate only.

Answer: (B)

Securing remote WebFig access with HTTPS hinges on two things: a trusted TLS certificate and proper access control at the network edge. A certificate that is valid and trusted by clients ensures that the connection is encrypted without browser warnings and that you can confidently verify the server’s identity. If you rely on a self-signed certificate, users will see warnings unless that certificate is manually installed on every client, which isn’t practical for remote use.

Coupled with this, firewall rules must restrict who can reach the HTTPS service. Allowing HTTPS only from trusted networks or specific IPs (or requiring access through a VPN) reduces the exposure of the management interface to the wider internet and helps prevent unauthorized attempts.

So, enabling the service is not sufficient on its own—you need a valid certificate and properly configured firewall rules to make remote HTTPS access both usable and secure. The other options would undermine security: disabling HTTPS eliminates encryption, disabling the firewall opens the device to attacks, and using a self-signed certificate alone is not ideal for widespread remote access due to trust warnings.