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

Severity	Group ID	Group Title	Version	Rule ID	Date	STIG Version
medium	V-225634	SRG-OS-000080	ZWMQ0055	SV-225634r1055912_rule	2025-02-24	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
a) Refer to the following report produced by the TSS Data Collection: - SENSITVE.RPT(WHOHMPRO) b) For all process resources (i.e., ssid.processname) defined to MQPROC or MXPROC resource class, ensure access authorization restricts access to users requiring the ability to make process 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.

ℹ️ Check

a) Refer to the following report produced by the TSS Data Collection: - SENSITVE.RPT(WHOHMPRO) b) For all process resources (i.e., ssid.processname) defined to MQPROC or MXPROC resource class, ensure access authorization restricts access to users requiring the ability to make process 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
For all process resources (i.e., ssid.processname) defined to MQPROC or MXPROC resource class, ensure access authorization restricts access to users requiring the ability to make process 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 processes beginning with the letter V on queue manager (QM1): TSS ADD(USER1) FAC(QM1MSTR) TSS PER(USER1) MQPROC(QM1.V) ACC(READ) ACTION(AUDIT)

✔️ Fix

For all process resources (i.e., ssid.processname) defined to MQPROC or MXPROC resource class, ensure access authorization restricts access to users requiring the ability to make process 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 processes beginning with the letter V on queue manager (QM1): TSS ADD(USER1) FAC(QM1MSTR) TSS PER(USER1) MQPROC(QM1.V) ACC(READ) ACTION(AUDIT)