The Jamf Pro EMM server or platform must be configured to initiate a session lock after a 15-minute period of inactivity.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-241791 | JAMF-10-000460 | SV-241791r960741_rule | CCI-000057 | medium |
| 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. SFR ID: FMT_SMF.1.1(2) i | ||||
| STIG | Date | |||
| Jamf Pro v10.x EMM Security Technical Implementation Guide | 2024-08-27 | |||
Related Frameworks
1 mapping across 4 frameworks
Related Frameworks
SCF0 mappings
No source states a mapping between these directly.
Also reachable in 3 hops (1) derived by us, not asserted by any source
Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.
- DISA STIG Benchmark (XCCDF)V3R1intersects(normalised)
- DISA CCI List2025-01-23equal to(normalised)
- SCF Secure Traceability Relationship Mapping (STRM)2026.2intersects
NIST 800-530 mappings
No source states a mapping between these directly.
Also reachable in 2 hops (18) derived by us, not asserted by any source
Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.
- DISA STIG Benchmark (XCCDF)V3R1intersects(normalised)
- DISA CCI List2025-01-23equal to(normalised)
- DISA STIG Benchmark (XCCDF)V3R1intersects(normalised)
- DISA STIG Benchmark (XCCDF)2our copyintersects(normalised)
- DISA STIG Benchmark (XCCDF)2intersects(normalised)
- DISA CCI List2025-01-23equal to(normalised)
- DISA STIG Benchmark (XCCDF)V3R1intersects(normalised)
- DISA STIG Benchmark (XCCDF)V1R4our copyintersects(normalised)
- DISA STIG Benchmark (XCCDF)V1R4intersects(normalised)
- DISA CCI List2025-01-23equal to(normalised)
- DISA STIG Benchmark (XCCDF)V3R1intersects(normalised)
- DISA STIG Benchmark (XCCDF)1our copyintersects(normalised)DISA STIG Benchmark (XCCDF)V1R7our copyintersects(normalised)
- DISA STIG Benchmark (XCCDF)1intersects(normalised)DISA STIG Benchmark (XCCDF)V1R7intersects(normalised)
- DISA CCI List2025-01-23equal to(normalised)
- DISA STIG Benchmark (XCCDF)V3R1intersects(normalised)
- DISA STIG Benchmark (XCCDF)V2R2our copyintersects(normalised)
- DISA STIG Benchmark (XCCDF)V2R2intersects(normalised)
- DISA CCI List2025-01-23equal to(normalised)
- DISA STIG Benchmark (XCCDF)V3R1intersects(normalised)
- DISA STIG Benchmark (XCCDF)7our copyintersects(normalised)
- DISA STIG Benchmark (XCCDF)7intersects(normalised)
- DISA CCI List2025-01-23equal to(normalised)
- DISA STIG Benchmark (XCCDF)V3R1intersects(normalised)
- DISA STIG Benchmark (XCCDF)V1R1our copyintersects(normalised)
- DISA STIG Benchmark (XCCDF)V1R1intersects(normalised)
- DISA CCI List2025-01-23equal to(normalised)
- DISA STIG Benchmark (XCCDF)V3R1intersects(normalised)
- DISA STIG Benchmark (XCCDF)V2R2our copyintersects(normalised)
- DISA STIG Benchmark (XCCDF)V2R2intersects(normalised)
- DISA CCI List2025-01-23equal to(normalised)
- DISA STIG Benchmark (XCCDF)V3R1intersects(normalised)
- DISA STIG Benchmark (XCCDF)V2R2our copyintersects(normalised)
- DISA STIG Benchmark (XCCDF)V2R2intersects(normalised)
- DISA CCI List2025-01-23equal to(normalised)
- DISA STIG Benchmark (XCCDF)V3R1intersects(normalised)
- DISA STIG Benchmark (XCCDF)V2R2our copyintersects(normalised)
- DISA STIG Benchmark (XCCDF)V2R2intersects(normalised)
- DISA CCI List2025-01-23equal to(normalised)
+8 more (top 10 by confidence shown)
NIST 800-1710 mappings
No source states a mapping between these directly.
Also reachable in 3 hops (1) derived by us, not asserted by any source
Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.
3.1.10
1.00
- DISA STIG Benchmark (XCCDF)V3R1intersects(normalised)
- DISA CCI List2025-01-23equal to(normalised)
- NIST SP 800-171 Rev 2, Appendix DRev 2 (Feb 2020, errata Jan 2021)equal to(normalised)
CCI1 mapping
CCI-000057
1.00
- DISA STIG Benchmark (XCCDF)V3R1intersects(normalised)
Details
Check Text (C-241791r960741_chk)
Verify the Jamf Pro EMM server or platform is configured to initiate a session lock after a 15-minute period of inactivity.
Review the variable in the Jamf Pro web.xml file.
On the Jamf Pro host server, open the web.xml file:
If using macOS, the web.xml file is located at the following filepath:
/Library/JSS/Tomcat/webapps/ROOT/WEB-INF/
If using Windows, the web.xml file is located at the following filepath:
C:\Program Files\JSS\Tomcat\webapps\ROOT\WEB-INF\
If using Linux, the web.xml file is located at the following filepath:
/usr/local/jss/tomcat/webapps/ROOT/WEB-INF/
Locate the following setting:
<session-config>
<session-timeout>15</session-timeout>
</session-config>
Ensure that the code is not commented out. If the code is commented out, remove the comment tags <!-- --> that encase the code.
Note: Session timeout is in minutes.
If the code is commented out or session-timeout is not configured to "15" minutes or less, this is a finding.
Fix Text (F-45026r685126_fix)
Perform the following procedure to configure the Jamf session lock to lock after a 15-minute period of inactivity.
Configuring the Variable in the JAMF web.xml File
On the Jamf Pro EMM host server, open the web.xml file:
If using macOS, the web.xml file is located at the following filepath:
/Library/JSS/Tomcat/webapps/ROOT/WEB-INF/
If using Windows, the web.xml file is located at the following filepath:
C:\Program Files\JSS\Tomcat\webapps\ROOT\WEB-INF\
If using Linux, the web.xml file is located at the following filepath:
/usr/local/jss/tomcat/webapps/ROOT/WEB-INF/
Locate the following setting:
<session-config>
<session-timeout>1</session-timeout>
</session-config>
Ensure that the code is not commented out. If the code is commented out, remove the comment tags <!-- --> that encase the code.
Modify the session-timeout to a value from 1 to 15.
Note: Session timeout is in minutes.
Restart Tomcat after modifying anything within the web.xml file.
See Starting and Stopping Tomcat for instructions in the Jamf admin guide.