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

Severity	Group ID	Group Title	Version	Rule ID	Date	STIG Version
medium	V-225635	SRG-OS-000080	ZWMQ0056	SV-225635r1146233_rule	2025-09-28	7

Description
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.

Description

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
Refer to the following reports produced by the TSS Data Collection: - SENSITVE.RPT(WHOHMNLI). - SENSITVE.RPT(WHOHXNLI). For all namelist resources (i.e., ssid.namelist) defined to 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. If this guidance is true, this is not a finding. Note: ssid is the queue manager name (a.k.a., subsystem identifier).

ℹ️ Check

Refer to the following reports produced by the TSS Data Collection: - SENSITVE.RPT(WHOHMNLI). - SENSITVE.RPT(WHOHXNLI). For all namelist resources (i.e., ssid.namelist) defined to 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. If this guidance is true, this is not a finding. Note: ssid is the queue manager name (a.k.a., subsystem identifier).

✔️ Fix
For all namelist resources (i.e., ssid.namelist) defined to MQNLIST or MXNLIST resource class, 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). The following is a sample of the commands required to allow a user (USER1) to inquire on namelist TST1 on queue manager (QM1): TSS ADD(USER1) FAC(QM1MSTR) TSS PER(USER1) MQNLIST(QM1.TST1.) ACC(READ) ACTION(AUDIT)

✔️ Fix

For all namelist resources (i.e., ssid.namelist) defined to MQNLIST or MXNLIST resource class, 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). The following is a sample of the commands required to allow a user (USER1) to inquire on namelist TST1 on queue manager (QM1): TSS ADD(USER1) FAC(QM1MSTR) TSS PER(USER1) MQNLIST(QM1.TST1.) ACC(READ) ACTION(AUDIT)