V-253927

Discussion

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.

Check Content

Review the network device configuration to determine if the network device or its associated authentication server prohibits the use of cached authenticators after an organization-defined time period.

Verify idle-timeouts, SSH keepalive messages, and SSH rekey are configured to meet the requirements of the target network.
[edit system]
login {
    idle-timeout 10;
}
system {
    services {
        ssh {
            protocol-version v2;
            client-alive-count-max (0..255);
            client-alive-interval (0..65535 seconds);
            rekey {
                data-limit (51200..4294967295 bytes);
                time-limit (1..1440 minutes);
            }
        }
    }
}

For externally authenticated accounts, verify the external authentication server enforces appropriate authenticator timeouts.

If cached authenticators are used after an organization-defined time period, this is a finding.