Check: ISEC-06-000030
ISEC7 Sphere STIG:
ISEC-06-000030
(in version v3 r1)
Title
The ISEC7 SPHERE must initiate a session lock after a 15-minute period of inactivity. (Cat II impact)
Discussion
A session time-out lock is a temporary action taken when a user 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 Content
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 the user is prompted to login 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 Text
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.
Additional Identifiers
Rule ID: SV-224761r1013800_rule
Vulnerability ID: V-224761
Group Title: SRG-APP-000003
Expert Comments
CCIs
Number | Definition |
---|---|
CCI-000057 |
Prevent further access to the system by initiating a device lock after organization-defined time period of inactivity; and/or requiring the user to initiate a device lock before leaving the system unattended. |
Controls
Number | Title |
---|---|
AC-11 |
Session Lock |