STIGQter: STIG Summary: zOS WebSphere MQ for RACF Security Technical Implementation Guide Version: 7 Release: 3 Benchmark Date: 01 Jul 2026:

WebSphere MQ Process resource profiles defined in the appropriate Class must be protected in accordance with security requirements.

DISA Rule

SV-224562r1145297_rule

Vulnerability Number

V-224562

Group Title

SRG-OS-000080

Rule Version

ZWMQ0055

Severity

CAT II

CCI(s)

• CCI-000213 - Enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies.

Weight

10

Fix Recommendation

Process security validates userids authorized to issue WebSphere MQ inquiries on process definitions. A process definition object defines an application that is started in response to a trigger event on a queue manager. Process security will be active, and all profiles ssid.processname will be defined to the appropriate class. Restrict READ access to those userids requiring access to make process inquiries.

For all process resources (i.e., ssid.processname) defined to the MQPROC, GMQPROC, MXPROC, and GMXPROC resource classes, ensure the following items are in effect:

Note: ssid is the queue manager name (a.k.a., subsystem identifier).

Resource profiles are defined with a UACC(NONE).
Access authorization restricts access to users requiring the ability to make process inquires. This is difficult to determine. However, an item for concern may be a profile with * READ specified in the access list.

A set of sample commands are provided below to implement the minimum profiles necessary for proper security.

/* THE FOLLOWING PROFILE FORCES GRANULAR PROFILES DEFINITIONS */
RDEF MQPROC ** UACC(NONE) OWNER(ADMIN) AUDIT(ALL(READ)) DATA('MQPROC DENY-BY-DEFAULT PROFILE')

RDEF MQPROC <ssid>.** UACC(NONE) OWNER(ADMIN) AUDIT(ALL(READ)) DATA('REQUIRED FOR ZWMQ0055')
PE <ssid>.** CL(MQPROC) ID(<ApplicableUsers>)

SETR RACL(MQPROC) REF

Note that an additional WebSphere MQ Refresh may be required for active queue managers. This is done from the CONSOLE:

The example is for a queue manager named QMD1:
>QMD1 REFRESH SECURITY(*)

The following is a sample of the commands required to allow a group (GRP1) to inquire on processes beginning with the letter V on queue manager (QM1):

RDEFINE MQPROC QM1.V* UACC(NONE) AUDIT(ALL(READ))
PERMIT QM1.V* CLASS(MQPROC) ID(GRP1) ACCESS(READ)

Check Contents

Refer to the following reports produced by the RACF Data Collection:

- SENSITVE.RPT(MQPROC).
- SENSITVE.RPT(MXPROC).

For all process resources (i.e., ssid.processname) defined to the MQPROC and GMQPROC resource classes (or MXPROC and GMXPROC resource classes, if SCYCASE is set to MIXED). If the following guidance is true, this is not a finding.

Note: ssid is the queue manager name (a.k.a., subsystem identifier).

Resource profiles are defined with a UACC(NONE).
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.

Vulnerability Number

V-224562

Documentable

False

Rule Version

ZWMQ0055

Severity Override Guidance

Refer to the following reports produced by the RACF Data Collection:

- SENSITVE.RPT(MQPROC).
- SENSITVE.RPT(MXPROC).

For all process resources (i.e., ssid.processname) defined to the MQPROC and GMQPROC resource classes (or MXPROC and GMXPROC resource classes, if SCYCASE is set to MIXED). If the following guidance is true, this is not a finding.

Note: ssid is the queue manager name (a.k.a., subsystem identifier).

Resource profiles are defined with a UACC(NONE).
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.

Check Content Reference

M

Target Key

4167