SK0-004 · Question #796
A server technician has produced a vulnerability report and notices a port is flagged as being susceptible to remote attacks. Given this scenario, the technician must mitigate the vulnerability and…
The correct answer is C. Disable RSH service on the server, enable SSH, and block port 514 at the network or server level. RSH (Remote Shell) is an insecure, unencrypted protocol on port 514 that should be disabled, while SSH provides the encrypted secure channel required for safe remote administration.
Question
A server technician has produced a vulnerability report and notices a port is flagged as being susceptible to remote attacks. Given this scenario, the technician must mitigate the vulnerability and use a "secure channel" for remote administration. Which of the following actions BEST represents what the technician should do to harden the server?
Options
- ADisable SSH service on the server, enable RSH, and block port 443 at the network or server level
- BDisable SSH service on the server, enable rlogin, and block port 513 at the network or server
- CDisable RSH service on the server, enable SSH, and block port 514 at the network or server level
- DDisable RDP service on the server, enable Telnet, and block port 3389 at the network or server
How the community answered
(23 responses)- A13% (3)
- B4% (1)
- C74% (17)
- D9% (2)
Why each option
RSH (Remote Shell) is an insecure, unencrypted protocol on port 514 that should be disabled, while SSH provides the encrypted secure channel required for safe remote administration.
Disabling SSH removes the secure channel rather than enabling it, and RSH is the insecure protocol that should be replaced, not port 443 (HTTPS).
rlogin (port 513) is also an insecure, plaintext legacy protocol and does not constitute a secure channel for remote administration.
RSH transmits data in plaintext and is flagged as a vulnerability; disabling it and blocking its port (514) removes the attack surface. SSH replaces RSH with an encrypted, authenticated tunnel, satisfying the requirement for a secure remote administration channel.
Telnet transmits credentials and data in plaintext and is one of the least secure remote access methods available, making it unsuitable as a secure channel.
Concept tested: Replacing insecure remote shell protocols with SSH
Source: https://www.cisecurity.org/insights/white-papers/ssh-usage-in-enterprise-security
Topics
Community Discussion
No community discussion yet for this question.