Further information on TLS filtering in gateways can be found in the web content filters section of the Guidelines for Gateways. Secure Shell Using Secure Shell When using ICT equipment or software that implements SSH, security controls for using AACAs and AACPs in the ASDApproved Cryptographic Algorithms and ASD-Approved Cryptographic Protocols sections of these guidelines will also need to be consulted. Configuring Secure Shell SSH version 1 was found to have a number of security vulnerabilities, and was subsequently replaced by SSH version 2. As such, an organisation implementing SSH should disable the use of SSH version 1. In addition, a number of security risks exist when SSH is configured in an insecure manner. To mitigate these security risks, SSH should be configured as per the configuration settings below. The configuration settings below are based on OpenSSH. An organisation using other implementations of SSH should adapt these settings to suit their SSH implementation. Security Control: ISM-1506; Revision: 1; Updated: Mar-22; Applicability: All; Essential Eight: N/A The use of SSH version 1 is disabled for SSH connections. Security Control: ISM-0484; Revision: 6; Updated: Dec-21; Applicability: All; Essential Eight: N/A The SSH daemon is configured to:  only listen on the required interfaces (ListenAddress xxx.xxx.xxx.xxx)  have a suitable login banner (Banner x)  have a login authentication timeout of no more than 60 seconds (LoginGraceTime 60)  disable host-based authentication (HostbasedAuthentication no)  disable rhosts-based authentication (IgnoreRhosts yes)  disable the ability to login directly as root (PermitRootLogin no)  disable empty passwords (PermitEmptyPasswords no)  disable connection forwarding (AllowTCPForwarding no)  disable gateway ports (GatewayPorts no)  disable X11 forwarding (X11Forwarding no). Authentication mechanisms As public key-based authentication schemes offer stronger authentication than passphrase-based authentication schemes, due to being much less susceptible to brute-force attacks, they should be used for SSH connections. Furthermore, in order to protect SSH private keys, access to such keys should be protected via the use of passphrases or key encryption keys. Security Control: ISM-0485; Revision: 3; Updated: Sep-18; Applicability: All; Essential Eight: N/A Public key-based authentication is used for SSH connections. Security Control: ISM-1449; Revision: 1; Updated: Sep-18; Applicability: All; Essential Eight: N/A SSH private keys are protected with a passphrase or a key encryption key. 135

Select target paragraph3

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