20.3.
Secure Shell
Objective
Recommended Control 01:
Recommended Control 02:
Recommended Control 03:
Recommended Control 04:
Recommended Control 05:
Secure Shell (SSH) is implemented correctly as an Approved
Cryptographic Protocol
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
ListenAddressxxx.xxx.xxx.xxx
interfaces, configure the SSH
daemon to listen only on the
required interfaces
Disable connection forwarding
AllowTCPForwarding no
Disable gateway ports
Gatewayports no
Disable the ability to login directly PermitRootLogin no
as root
Disable host‐based authentication HostbasedAuthentication
no
Disable rhosts‐based
RhostsAuthentication no
authentication
IgnoreRhosts yes
Do not allow empty passwords
PermitEmptyPasswords no
Configure a suitable login banner Banner/directory/filename
Configure a login authentication
LoginGraceTime xx
timeout of no more than 60
seconds
Disable X forwarding
X11Forwarding no
Agencies should use public key‐based authentication before using
password‐based authentication
Agencies that allow password authentication should use
techniques to block brute force18 attacks against the password
Agencies should use parameter checking when using the ‘forced
command’ option
Agencies that use logins without a password for automated
purposes should disable:
access from IP addresses that do not need access
port forwarding
agent credential forwarding
X11 display remoting
console access
18
A brute‐force attack, or exhaustive key search, is a cryptanalytic attack that can, in theory, be used against any
encrypted data (except for data encrypted in an information‐theoretically secure manner)
92
Select target paragraph3
Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents