vulnerability. 17.5.6.R.03. Rationale SSH has the ability to forward connections and access privileges in a variety of ways. This means that an attacker who can exploit any of these features can gain unauthorised access to a potentially large amount of classified information. 17.5.6.R.04. Rationale Host-based authentication requires no credentials (password, public key etc.) to authenticate although in some cases a host key can be used. This renders SSH vulnerable to an IP spoofing attack. 17.5.6.R.05. Rationale An attacker who gains access to a system with system administrator privileges will have the ability to not only access classified information but to control that system completely. Given the clearly more serious consequences of this, system administrator login or administrator privilege escalation SHOULD NOT be permitted. 17.5.6.C.01. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:2647] The table below outlines the settings that SHOULD be implemented when using SSH. Configuration description Configuration directive Disallow the use of SSH version 1 Protocol 2 On machines with multiple interfaces, configure the SSH daemon to ListenAddress listen only on the required interfaces xxx.xxx.xxx.xxx Disable connection forwarding AllowTCPForwarding no Disable gateway ports Gatewayports no Disable the ability to login directly as root PermitRootLogin no Disable host-based authentication HostbasedAuthentication no Disable rhosts-based authentication RhostsAuthentication no IgnoreRhosts yes 17.5.7. Do not allow empty passwords PermitEmptyPasswords no Configure a suitable login banner Banner/directory/filename Configure a login authentication timeout of no more than 60 seconds LoginGraceTime xx Disable X forwarding X11Forwarding no Authentication mechanisms 17.5.7.R.01. Rationale Public key-based systems have greater potential for strong authentication, put simply, people are not able to remember particularly strong passwords. Password-based authentication schemes are also more susceptible to interception than public key-based authentication schemes. 17.5.7.R.02. Rationale Passwords are more susceptible to guessing attacks, so if passwords are used in a system then countermeasures should be put into place to reduce the chance of a successful brute force attack. 17.5.7.C.01. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:2672] Agencies SHOULD use public key-based authentication before using password-based authentication. 17.5.7.C.02. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:2673] Agencies that allow password authentication SHOULD use techniques to block brute force attacks against the password. 17.5.8. Automated remote access 17.5.8.R.01. Rationale If password-less authentication is enabled, allowing access from unknown IP addresses would allow untrusted parties to automatically authenticate to systems without needing to know the password. 17.5.8.R.02. Rationale If port forwarding is not disabled or it is not configured securely, an attacker may be able to gain access to forwarded ports and thereby create a communication channel between the attacker and the host. 17.5.8.R.03. Rationale If agent credential forwarding is enabled, an intruder could connect to the stored authentication credentials and then use them to connect to other trusted hosts or even intranet hosts, if port forwarding has been allowed as well. 17.5.8.R.04. 245 Rationale Version_3.5__January-2022

Select target paragraph3

Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents