Automated remote access
If using logins without a passphrase for automated purposes, a number of security risks may arise, specifically:
if access from unknown Internet Protocol (IP) addresses is not restricted, an adversary could automatically
authenticate to systems without needing to know any passphrases
if port forwarding is not disabled, or it is not configured securely, access may be gained to forwarded ports,
thereby, creating a communication channel between an adversary and a host
if agent credential forwarding is enabled, an adversary could connect to the stored authentication credentials and
use them to connect to other trusted hosts, or even intranet hosts if port forwarding has been allowed as well
if X11 display remoting is not disabled, an adversary could gain control of displays as well as keyboard and mouse
control functions
if console access is allowed, every user who logs into the console could run programs that are normally restricted
to authenticated users.
To assist in mitigating these security risks, it is essential that the ‘forced command’ option is used to specify what
command is executed and parameter checking is enabled.
Security Control: ISM-0487; Revision: 4; Updated: Mar-22; Applicability: All; Essential Eight: N/A
When using logins without a passphrase for SSH connections, the following are disabled:
access from IP addresses that do not require access
port forwarding
agent credential forwarding
X11 display remoting
console access.
Security Control: ISM-0488; Revision: 4; Updated: Mar-22; Applicability: All; Essential Eight: N/A
If using remote access without the use of a passphrase for SSH connections, the ‘forced command’ option is used to
specify what command is executed and parameter checking is enabled.
SSH-agent
SSH-agent and similar key caching programs manage private keys stored on workstations and servers. Specifically, when
an SSH-agent launches, it requests a user’s passphrase to unlock the user’s private key. Subsequent access to remote
systems is then performed by the SSH-agent and does not require the user to re-enter their passphrase. Screen locks
and expiring key caches can be used to ensure that a user’s private key is not left unlocked for a long period of time.
Security Control: ISM-0489; Revision: 5; Updated: Mar-22; Applicability: All; Essential Eight: N/A
When SSH-agent or similar key caching programs are used, it is limited to workstations and servers with screen locks
and key caches that are set to expire within four hours of inactivity.
Further information
Further information on configuring OpenSSH is available from the OpenSSH project.
136
Select target paragraph3
Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents