STIGhubSTIGhub
STIGsRMF ControlsCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • RMF Controls
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 3 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to SPEC Innovations Innoslate 4.x Security Technical Implementation Guide

V-254086

CAT II (Medium)

Innoslate must initiate a session lock after a 15-minute period of inactivity.

Rule ID

SV-254086r845234_rule

STIG

SPEC Innovations Innoslate 4.x Security Technical Implementation Guide

Version

V1R1

CCIs

CCI-000057CCI-001133CCI-002039

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. Satisfies: SRG-APP-000003, SRG-APP-000190, SRG-APP-000390

Check Content

1. Enter the web.xml file located at C:\Innoslate4\apache-tomcat\webapps\Innoslate4\WEB-INF.
2. Search (Ctrl+f) for "session-timeout" object (typically found on line 8).
3. Verify time is set to 15 minutes, if not , this is a finding.

Fix Text

1. Enter the web.xml file located at C:\Innoslate4\apache-tomcat\webapps\Innoslate4\WEB-INF.
2. Search (Ctrl+f) for "session-timeout" object (typically found on line 8).
3. Set the time to 15 minutes.
4. Save.
5. Restart the service.