WebSphere MQ context resources defined to the appropriate ADMIN resource class must be protected in accordance with security requirements.

Severity	Group ID	Group Title	Version	Rule ID	Date	STIG Version
medium	V-225637	SRG-OS-000080	ZWMQ0058	SV-225637r1146239_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(WHOHMADM). - SENSITVE.RPT(WHOHXADM). For all context resources (i.e., ssid.CONTEXT) defined to the MQADMIN resource class (or MXADMIN resource class, if SCYCASE is set to MIXED), ensure access authorization restricts access to users requiring the ability to pass or set identity and/or origin data for a message. 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(WHOHMADM). - SENSITVE.RPT(WHOHXADM). For all context resources (i.e., ssid.CONTEXT) defined to the MQADMIN resource class (or MXADMIN resource class, if SCYCASE is set to MIXED), ensure access authorization restricts access to users requiring the ability to pass or set identity and/or origin data for a message. 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 context resources (i.e., ssid.CONTEXT) defined to the MQADMIN or MXADMIN resource class, ensure access authorization restricts access to users requiring the ability to pass or set identity and/or origin data for a message. 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 systems programming group (SYS1) to offload and reload messages for queue manager (QM1): TSS ADD(SYS1) FAC(QM1MSTR) TSS PER(SYS1) MQADMIN(QM1.CONTEXT) ACC(UPDATE) ACTION(AUDIT)

✔️ Fix

For all context resources (i.e., ssid.CONTEXT) defined to the MQADMIN or MXADMIN resource class, ensure access authorization restricts access to users requiring the ability to pass or set identity and/or origin data for a message. 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 systems programming group (SYS1) to offload and reload messages for queue manager (QM1): TSS ADD(SYS1) FAC(QM1MSTR) TSS PER(SYS1) MQADMIN(QM1.CONTEXT) ACC(UPDATE) ACTION(AUDIT)