WebSphere MQ command resources defined to MQCMDS resource class are not protected in accordance with security requirements.

Severity	Group ID	Group Title	Version	Rule ID	Date	STIG Version
medium	V-224369	SRG-OS-000080	ZWMQ0059	SV-224369r1144194_rule	2025-09-27	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 report produced by the dataset and Resource Data Collection: - SENSITVE.RPT(MQCMDS). - ACF2CMDS.RPT(RESOURCE) - Alternate report. For all command resources (i.e., ssid.command) defined to TYPE(MQC) (i.e., MQCMDS resource class), if the following guidance is true, this is not a finding. Note: ssid is the queue manager name (a.k.a., subsystem identifier). Access authorization restricts access to the appropriate personnel as designated in the WebSphere MQ COMMAND SECURITY CONTROLS Table in the z/OS STIG Addendum. All command access is logged as designated in the WebSphere MQ COMMAND SECURITY CONTROLS Table in the z/OS STIG Addendum.

ℹ️ Check

Refer to the following report produced by the dataset and Resource Data Collection: - SENSITVE.RPT(MQCMDS). - ACF2CMDS.RPT(RESOURCE) - Alternate report. For all command resources (i.e., ssid.command) defined to TYPE(MQC) (i.e., MQCMDS resource class), if the following guidance is true, this is not a finding. Note: ssid is the queue manager name (a.k.a., subsystem identifier). Access authorization restricts access to the appropriate personnel as designated in the WebSphere MQ COMMAND SECURITY CONTROLS Table in the z/OS STIG Addendum. All command access is logged as designated in the WebSphere MQ COMMAND SECURITY CONTROLS Table in the z/OS STIG Addendum.

✔️ Fix
The ISSO will ensure that all WebSphere MQ commands are restricted to authorized personnel. For all command resources (i.e., ssid.command) defined to TYPE(MQC) (i.e., MQCMDS resource class, ensure the following items are in effect: Note: ssid is the queue manager name (a.k.a., subsystem identifier). Access authorization restricts access to the appropriate personnel as designated in the table titled WebSphere MQ COMMAND SECURITY CONTROLS in the zOS STIG Addendum. All command access is logged as designated in the table titled WebSphere MQ COMMAND SECURITY CONTROLS, in the zOS STIG Addendum. Example: $KEY(ssid) TYPE(MQC) ALTER.- UID(syspaudt) SERVICE(READ,ADD,UPDATE) LOG ALTER.- UID(*) PREVENT SET R(MQC) COMPILE 'ACF2.MVA.MQC(ssid)' STORE F ACF2,REBUILD(MQC)

✔️ Fix

The ISSO will ensure that all WebSphere MQ commands are restricted to authorized personnel. For all command resources (i.e., ssid.command) defined to TYPE(MQC) (i.e., MQCMDS resource class, ensure the following items are in effect: Note: ssid is the queue manager name (a.k.a., subsystem identifier). Access authorization restricts access to the appropriate personnel as designated in the table titled WebSphere MQ COMMAND SECURITY CONTROLS in the zOS STIG Addendum. All command access is logged as designated in the table titled WebSphere MQ COMMAND SECURITY CONTROLS, in the zOS STIG Addendum. Example: $KEY(ssid) TYPE(MQC) ALTER.- UID(syspaudt) SERVICE(READ,ADD,UPDATE) LOG ALTER.- UID(*) PREVENT SET R(MQC) COMPILE 'ACF2.MVA.MQC(ssid)' STORE F ACF2,REBUILD(MQC)