STIGhubSTIGhub
STIGhub— A free STIG search and compliance tool·STIGs updated just now
Powered by Pylon·Privacy·Terms·Feedback·© 2026 Beacon Cloud Solutions, Inc.
← Back to Ivanti Policy Secure NDM Security Technical Implementation Guide

V-284541

CAT II (Medium)

The Ivanti Policy Secure must limit the number of concurrent sessions to one for each administrator account/or administrator type.

Rule ID

SV-284541r1244953_rule

STIG

Ivanti Policy Secure NDM Security Technical Implementation Guide

Version

V1R1

CCIs

CCI-000054

Discussion

Device management includes the ability to control the number of administrators and management sessions that manage a device. Limiting the number of allowed administrators and sessions per administrator based on account type, role, or access type is helpful in limiting risks related to denial-of-service (DoS) attacks. This requirement addresses concurrent sessions for administrative accounts and does not address concurrent sessions by a single administrator via multiple administrative accounts. The maximum number of concurrent sessions should be defined based upon mission needs and the operational environment for each system. At a minimum, limits must be set for SSH, HTTPS, account of last resort, and root account sessions.

Check Content

1. In the Web UI, navigate to Administrators >> Admins Realms >> Admin Realms.
2. Click the configured admin realm being used for CAC/PKI token admin logins.
3. Click the "Authentication Policy" tab, then click "Limits".

If the "Maximum number of sessions per user" field shows any value other than "1", this is a finding.

Fix Text

1. In the Web UI, navigate to Administrators >> Admins Realms >> Admin Realms.
2. Click the configured admin realm being used for CAC/PKI token admin logins.
3. Click the "Authentication Policy" tab, then click "Limits".
4. In "Maximum number of sessions per user", enter "1".
5. Click "Save Changes".