A security team wants to manage a Linux environment over a remote command-line session using SSH. They need a solution that encrypts session data and protects credentials from exposure. Which choice is the BEST approach?
Use a standard web server that defaults to port 80 for terminal access
Configure an administrative interface over unsecured port 23
Rely on password authentication behind a simple network filter
Implement key-based verification over an encrypted channel
Key-based verification through an encrypted channel is recommended for SSH (Secure Shell). It minimizes credential exposure by eliminating password exchanges and ensures strong cryptographic protection. Using password-based or unencrypted approaches can lead to intercepted credentials. Other solutions, including services that lack encryption or rely on plain-text protocols, do not satisfy security requirements.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is SSH and why is it considered secure?
Open an interactive chat with Bash
What is key-based verification in SSH, and how does it work?
Open an interactive chat with Bash
Why is port 23 (Telnet) considered insecure compared to SSH over an encrypted channel?
Open an interactive chat with Bash
CompTIA Cloud+ CV0-004
Security
Your Score:
Report Issue
Bash, the Crucial Exams Chat Bot
AI Bot
Loading...
Loading...
Loading...
IT & Cybersecurity Package Join Premium for Full Access