STIGhubSTIGhub
STIGsRMF ControlsCompare
STIGhub— A free STIG search and compliance tool·STIGs updated 4 days ago
Powered by Pylon·Privacy·Terms·© 2026 Beacon Cloud Solutions, Inc.
← Back to zOS WebsphereMQ for ACF2 Security Technical Implementation Guide

V-224366

CAT II (Medium)

WebSphere MQ Namelist resources must be protected in accordance with security requirements.

Rule ID

SV-224366r1050683_rule

STIG

zOS WebsphereMQ for ACF2 Security Technical Implementation Guide

Version

V7R1

CCIs

SV-7270

Discussion

WebSphere MQ resources allow for the control of administrator functions, connections, commands, queues, processes, and namelists. Some resources provide the ability to disable or bypass security checking. Failure to properly protect WebSphere MQ resources may result in unauthorized access. This exposure could compromise the availability, integrity, and confidentiality of system services, applications, and customer data.

Check Content

a) Refer to the following report produced by the ACF2 Data Collection:

- SENSITVE.RPT(MQNLIST)
- ACF2CMDS.RPT(RESOURCE) - Alternate report

b) For all namelist resources (i.e., ssid.namelist) defined to TYPE(MQN)(i.e., MQNLIST resource class or MXNLIST resource class if SCYCASE is set to MIXED), ensure access authorization restricts access to users requiring the ability to make namelist inquiries. This is difficult to determine. However, an item for concern may be a profile with * READ specified in the access list.

NOTE: ssid is the queue manager name (a.k.a., subsystem identifier).

c) If (b) is true, there is no finding.

d) If (b) is untrue, this is a finding.

Fix Text

The ISSO will ensure that all MQSeries/WebSphere MQ namelist resources are restricted to authorized users.

For all namelist resources (i.e., ssid.namelist) defined to TYPE(MQN) (i.e., MQNLIST resource class or MXNLIST resource class if SCYCASE is set to MIXED), ensure access authorization restricts access to users requiring the ability to make namelist inquiries. This is difficult to determine. However, an item for concern may be a profile with * READ specified in the access list.

NOTE: ssid is the queue manager name (a.k.a., subsystem identifier).

Example:

$KEY(QZN1) TYPE(MQN)
SYSTEM.DEFAULT.NAMELIST UID(MQAdministrators) SERVICE(READ) LOG
SYSTEM.DEFAULT.NAMELIST UID(*) PREVENT