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

CAT II (Medium)

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

Rule ID

SV-224566r1145299_rule

STIG

zOS WebSphere MQ for RACF Security Technical Implementation Guide

Version

V7R3

CCIs

CCI-000213CCI-002234

Discussion

WebSphere MQ resources allow for the control of commands. Failure to properly protect WebSphere MQ Command resources may result in unauthorized access. This exposure could compromise the availability, integrity, and confidentiality of system services, applications, and customer data.

Check Content

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

- SENSITVE.RPT(MQCMDS).

For all command resources (i.e., ssid.command) defined to the MQCMDS and GMQCMDS resource classes. 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 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 WebScphere MQ COMMAND SECURITY CONTROLS Table in the z/OS STIG Addendum.

Fix Text

Command security validates userids authorized to issue MQSeries/WebSphere MQ commands. Command security will be active

For all command resources (i.e., ssid.command) defined to the MQCMDS resource class, ensure the following items are in effect:

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

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

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 MQCMDS ** UACC(NONE) OWNER(ADMIN) AUDIT(ALL(READ)) DATA('MQCMDS DENY-BY-DEFAULT PROFILE')

RDEF MQCMDSN <ssid>.<CmdName>.** UACC(NONE) OWNER(ADMIN) AUDIT(ALL(READ)) DATA('MQCMDS Required See ZWMQ0059')

PE <ssid>.<CmdNAme>.** CL(MQCMDS) ID(<authorizeduser>) ACC(C)

SETR RACL(MQCMDS) REF

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

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