STIGhubSTIGhub
STIGhub— A free STIG search and compliance tool·STIGs updated 5 hours ago
Powered by Pylon·Privacy·Terms·Feedback·© 2026 Beacon Cloud Solutions, Inc.
← Back to Rancher Government Solutions (RGS) Harvester Government GPOS Security Technical Implementation Guide

V-285663

CAT II (Medium)

Harvester Government must automatically terminate inactive shell sessions after 15 minutes of inactivity.

Rule ID

SV-285663r1273641_rule

STIG

Rancher Government Solutions (RGS) Harvester Government GPOS Security Technical Implementation Guide

Version

V1R1

CCIs

CCI-000057

Discussion

Terminating idle user sessions reduces the risk of unauthorized access to information and system resources when a user leaves a session unattended. Automatic session termination helps prevent unauthorized individuals from assuming the identity of a previously authenticated user and gaining access to privileged functions or sensitive information. Harvester Government nodes provide administrative access through shell sessions. Configuring an inactivity timeout ensures unattended shell sessions are automatically terminated after a defined period of inactivity, reducing the opportunity for unauthorized access to the operating system and platform management functions.

Check Content

Verify Harvester Government automatically terminates inactive shell sessions.

1. Access Harvester Government using a privileged account and verify the auto-logout configuration file exists and is protected:

stat -c "%n %a %U %G" /etc/profile.d/autologout.sh

2. Verify the output returns:

/etc/profile.d/autologout.sh 755 root root

If the file does not exist, is not owned by root, or permissions differ from 755, this is a finding.

3. Verify the inactivity timeout configuration:

grep -E "^(TMOUT=900|readonly TMOUT)" /etc/profile.d/autologout.sh

4. Verify the output contains:

TMOUT=900
readonly TMOUT

If TMOUT is not configured to 900 seconds, TMOUT is not configured as read only, or the configuration is missing, this is a finding.

Fix Text

Ensure Harvester Government platform is running in its default configuration. 

1. Attempt to reboot the node to restore the original, immutable settings. Run the script again and check for failures.

2. If any checks return a "FAIL" status, upgrade or reinstall Harvester Government platform in its default configuration.