SLES-15-010280 - The SUSE operating system SSH daemon must be configured with a timeout interval.

Warning! Audit Deprecated

This audit has been deprecated and will be removed in a future update.

View Next Audit Version

Information

Terminating an idle session within a short time period reduces the window of opportunity for unauthorized personnel to take control of a management session enabled on the console or console port that has been left unattended. In addition, quickly terminating an idle session will also free up resources committed by the managed network element.

Terminating network connections associated with communications sessions includes, for example, deallocating associated TCP/IP address/port pairs at the SUSE operating system-level, and deallocating networking assignments at the application level if multiple application sessions are using a single SUSE operating system-level network connection. This does not mean that the SUSE operating system terminates all sessions or network access; it only ends the inactive session and releases the resources associated with that session.

Satisfies: SRG-OS-000126-GPOS-00066, SRG-OS-000163-GPOS-00072, SRG-OS-000279-GPOS-00109

Solution

Configure the SUSE operating system SSH daemon to timeout idle sessions.

Add or modify (to match exactly) the following line in the '/etc/ssh/sshd_config' file:

ClientAliveInterval 600

The SSH daemon must be restarted for any changes to take effect.

See Also

https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_SLES_15_V1R10_STIG.zip

Item Details

References: CAT|II, CCI|CCI-000879, CCI|CCI-001133, CCI|CCI-002361, Rule-ID|SV-234827r854189_rule, STIG-ID|SLES-15-010280, Vuln-ID|V-234827

Plugin: Unix

Control ID: 83a2e52a446c5a2e9d7eb6e678196d37ee99e598b05962d8797c686d4dcf6cc4