Information
Some authentication implementations can be configured to use cached authenticators.
If cached authentication information is out-of-date, the validity of the authentication information may be questionable.
The organization-defined time period should be established for each device depending on the nature of the device; for example, a device with just a few administrators in a facility with spotty network connectivity may merit a longer caching time period than a device with many administrators.
Solution
Configure the network device or its associated authentication server to prohibit the use of cached authenticators after an organization-defined time period.
set system login idle-timeout 10
set system services ssh protocol-version v2
set system services ssh client-alive-count-max (0..255)
set system services ssh client-alive-interval (0..65535 seconds)
set system services ssh rekey data-limit (51200..4294967295 bytes)
set system services ssh rekey time-limit (1..1440 minutes)