STIGhubSTIGhub
STIGsRMF ControlsCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • RMF Controls
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 3 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to zOS WebSphere MQ for RACF Security Technical Implementation Guide

V-224567

CAT II (Medium)

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

Rule ID

SV-224567r1145086_rule

STIG

zOS WebSphere MQ for RACF Security Technical Implementation Guide

Version

V7R3

CCIs

CCI-001762CCI-000213

Discussion

RESLEVEL security profiles control the number of userids checked for API-resource security. RESLEVEL is a powerful option that can cause the bypassing of all security checks. RESLEVEL security will not be implemented.

Check Content

Refer to the following reports produced by the Data Set and Resource Data Collection:

- SENSITVE.RPT(MQADMIN).
- SENSITVE.RPT(MXADMIN).

Automated Analysis
Refer to the following report produced by the Data Set and Resource Data Collection:

- PDI(ZWMQ0060).

Review the MQADMIN and GMQADMIN resource classes (or MXADMIN and GMXADMIN 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).

A RESLEVEL resource (i.e., ssid.RESLEVEL) is defined for each queue manager with a UACC(NONE).
Access authorization to these RESLEVEL resources restricts all access. No users or groups must be specified in the access list.

Fix Text

RESLEVEL security profiles control the number of userids checked for API-resource security. RESLEVEL security will not be implemented due to the following exposures and limitations:
RESLEVEL is a powerful option that can cause the bypassing of all security checks.
Security audit records are not created when the RESLEVEL profile is utilized.
If the WARNING option is specified on a RESLEVEL profile, no warning messages are produced.

To protect against any profile in the MQADMIN or MXADMIN class, such as ssid.**, resolving to a RESLEVEL profile, a ssid.RESLEVEL profile will be defined for each queue manager with UACC(NONE) specified and no users or groups specified in the access list.

Ensure the following items are in effect:

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

A RESLEVEL resource (i.e., ssid.RESLEVEL) is defined for each queue manager to the MQADMIN  or MXADMIN resource class with a UACC(NONE).
Access authorization to these RESLEVEL resources restricts all access. No users or groups must be specified in the access list.

A set of sample commands is provided below to implement the profile necessary for proper security. 

RDEF MQADMIN <ssid>.RESLEVEL UACC(NONE) OWNER(ADMIN) AUDIT(ALL(READ)) DATA('MQADMIN PROFILE REQUIRED BY ZWMQ0060')

SETR RACL(MQADMIN) 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(*)