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-224365

CAT II (Medium)

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

Rule ID

SV-224365r1050680_rule

STIG

zOS WebsphereMQ for ACF2 Security Technical Implementation Guide

Version

V7R1

CCIs

V-6966

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(MQPROC)
- ACF2CMDS.RPT(RESOURCE) - Alternate report

b) For all process resources (i.e., ssid.processname) defined to TYPE(MQP) (i.e., MQPROC resource class or MXPROC resource class if SCYCASE is set to MIXED), 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 Text

The ISSO will ensure that process security is active, all profiles are defined to the MQPROC class, and process inquiries are restricted to read access.

For all process resources (i.e., ssid.processname) defined to TYPE(MQP) (i.e., MQPROC resource class or MXPROC resource class if SCYCASE is set to MIXED), 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).

Example:

$KEY(ssid) TYPE(MQP)
CHL_TRIG_PROCESS UID(MQAdministrators) SERVICE(READ) LOG 
CHL_TRIG_PROCESS UID(*) PREVENT
SYSTEM.DEFAULT.PROCESS UID(MQAdministrators) SERVICE(READ) LOG
SYSTEM.DEFAULT.PROCESS UID(*)  PREVENT