The ISEC7 SPHERE must configure the timeout for the console to be 15 minutes or less.
Severity | Group ID | Group Title | Version | Rule ID | Date | STIG Version |
---|---|---|---|---|---|---|
medium | V-224774 | SRG-APP-000516 | ISEC-06-002520 | SV-224774r1013835_rule | 2024-08-20 | 3 |
Description |
---|
A session time-out lock is a temporary action taken when a user (MDM system administrator) stops work and moves away from the immediate physical vicinity of the information system but does not log out because of the temporary nature of the absence. Rather than relying on the user to manually lock their application session prior to vacating the vicinity, applications need to be able to identify when a user's application session has idled and take action to initiate the session lock. The session lock is implemented at the point where session activity can be determined and/or controlled. This is typically at the operating system level and results in a system lock but may be at the application level where the application interface window is secured instead. |
ℹ️ Check |
---|
Log in to the ISEC7 SPHERE Console. Navigate to Administration >> Configuration >> Apache Tomcat Settings. Validate the session timeout has been set to the correct value. Alternatively, allow the console to sit for 15 minutes and confirm that the user is prompted to log in once again when attempting to navigate to a new screen. If the SPHERE Console timeout has not been set for 15 minutes or less, this is a finding. |
✔️ Fix |
---|
Log in to the ISEC7 SPHERE Console. Navigate to Administration >> Configuration >> Apache Tomcat Settings. Set the session timeout to the correct value of 15 minutes or less. |