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 2 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to IBM WebSphere Traditional V9.x Security Technical Implementation Guide

V-255837

CAT II (Medium)

The WebSphere Application Server users in a LDAP user registry group must be authorized for that group.

Rule ID

SV-255837r961353_rule

STIG

IBM WebSphere Traditional V9.x Security Technical Implementation Guide

Version

V2R1

CCIs

CCI-002235

Discussion

Preventing non-privileged users from executing privileged functions mitigates the risk that unauthorized individuals or processes may gain unnecessary access to information or privileges. Restricting non-privileged users also prevents an attacker, who has gained access to a non-privileged account, from elevating privileges, creating accounts, and performing system checks and maintenance.

Check Content

If a file based or local federated repository is in use, this requirement is NA.

Review System Security Plan documentation.

Interview the system administrator.

In the administrative console select Security >> Global Security.

Under "User Account Repository", verify the "Available realm Definition" is set to "Standalone LDAP registry".

Select "Configure".

The properties of the LDAP repository are displayed for purposes of identifying the LDAP server.

Work with the admin of LDAP repository.

Identify users and groups.

Validate members of groups are authorized.

If the group members have not been authorized by the ISSO/ISSM, this is a finding.

Fix Text

In the LDAP server admin console, assign WebSphere users to the appropriate WebSphere group.