Which remote access method is considered secure according to policy?

Which remote access method is considered secure according to policy?

• A. Telnet
• B. FTP
• C. HTTP
• D. SSH or VPN

Answer: (D)

Remote access should be conducted over encrypted, authenticated channels to protect credentials and data. The insecure options transmit data in plaintext, making interception easy. Telnet sends commands and usernames in clear text; FTP does not encrypt file transfers or authentication by default; HTTP is not encrypted and not appropriate for remote administration. SSH encrypts the session and authenticates both ends for secure command-line access, and a VPN creates an encrypted tunnel that secures all traffic between the remote user and the internal network. Because of these protections, using SSH or a VPN is considered secure for remote access according to policy.

Remote access should be conducted over encrypted, authenticated channels to protect credentials and data. The insecure options transmit data in plaintext, making interception easy. Telnet sends commands and usernames in clear text; FTP does not encrypt file transfers or authentication by default; HTTP is not encrypted and not appropriate for remote administration. SSH encrypts the session and authenticates both ends for secure command-line access, and a VPN creates an encrypted tunnel that secures all traffic between the remote user and the internal network. Because of these protections, using SSH or a VPN is considered secure for remote access according to policy.