zOS WebSphere MQ for TSS STIG

zOS WebSphere MQ for TSS Security Technical Implementation Guide

The zOS WebSphere MQ for TSS Security Technical Implementation Guide (V7 R3) has 17 STIG checks. New to STIG checklists? Read What is a STIG checklist?, CKL vs CKLB, and STIG vs SCAP benchmark.

Find STIG checks

17STIG checks

Search filters this STIG's checks locally. Separate terms must all match (use quotes for an exact phrase). A search you ran on the Search page carries over here.

Severity

Version

V7 · R3

CurrentPublished Wed Jul 01 2026 What changed in V7R3

WebSphere MQ queue resource defined to the appropriate resource class must be protected in accordance with security requirements.

zOS WebSphere MQ for TSS Security Technical Implementation Guide

Assessment Title

Rule Text

WebSphere MQ queue resource defined to the appropriate resource class must be protected in accordance with security requirements.

Description

Discussion Text

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.

New to STIG checklists? Read What is a STIG checklist? and CKL vs CKLB.

Objective

V-225633

Rule

SV-225633r1146227_rule

Severity

medium

Rule Version

ZWMQ0054

Documentable

false

IA Controls

NIST SP 800-53

Rev 5

Assessment Procedure

Check Text

Refer to the following report produced by the z/OS Data Collection:

- MQSRPT(ssid).

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

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

- SENSITVE.RPT(WHOHMQUE).
- SENSITVE.RPT(WHOHXQUE).

For all queues identified by the DISPLAY QUEUE(*) ALL command in the MQSRPT(ssid), these queues will be prefixed by ssid to identify the resources to be protected. Ensure these queue resources are defined to the MQQUEUE (MXQUEUE resource class if SCYCASE is set to MIXED). If the following guidance is true, this is not a finding.

For message queues (i.e., ssid.queuename), access authorization restricts access to users requiring the ability to get messages from and put messages to message queues. This is difficult to determine. However, an item for concern may be a profile with * READ specified in the access list. Decentralized MQ Administrators, non-DECC datacenter users, can have up to ALTER access to the user message queues.

For system queues (i.e., ssid.SYSTEM.queuename), access authorization restricts WRITE and/or greater access to WebSphere MQ STCs, WebSphere MQ administrators, systems programming personnel, and CICS regions running WebSphere MQ applications.

For the following system queues, ensure that UPDATE access is restricted to auditors and users that require access to review message queues.
ssid.SYSTEM.COMMAND.INPUT
ssid.SYSTEM.COMMAND.REPLY
ssid.SYSTEM.CSQOREXX.*
ssid.SYSTEM.CSQUTIL.*

For the real dead-letter queue (to determine queue name refer to ZWMQ0053), ALTER access authorization restricts access to WebSphere MQ STCs, WebSphere MQ administrators, CICS regions running WebSphere MQ applications, and any automated application used for dead-letter queue maintenance.

For the alias dead-letter queue (to determine queue name refer to ZWMQ0053), UPDATE access authorization restricts access to users requiring the ability to put messages to the dead-letter queue. This is difficult to determine. However, an item for concern may be a profile with * READ specified in the access list.

Implementation Procedure

Fix Text

For all queue resources defined to the MQQUEUE or MXQUEUE resource class, ensure the following items are in effect:

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

For system queues (i.e., ssid.SYSTEM.queuename), access authorization restricts access to WebSphere MQ STCs, WebSphere MQ administrators, systems programming personnel, and CICS regions running WebSphere MQ applications.

For the following system queues ensure that UPDATE access is restricted to WebSphere MQ STCs, WebSphere MQ administrators, systems programming personnel, CICS regions running WebSphere MQ applications, auditors, and users that require access to review message queues.

ssid.SYSTEM.COMMAND.INPUT
ssid.SYSTEM.COMMAND.REPLY
ssid.SYSTEM.CSQOREXX.*

For the following system queues (i.e., ssid.SYSTEM.CSQUTIL.*) ensure that UPDATE access is restricted to WebSphere MQ STCs, WebSphere MQ administrators, systems programming personnel, CICS regions running WebSphere MQ applications, and auditors.

For the real dead-letter queue (to determine queue name, refer to ZWMQ0053), access authorization restricts access to WebSphere MQ STCs, WebSphere MQ administrators, CICS regions running WebSphere MQ applications, and any automated application used for dead-letter queue maintenance.

For the alias dead-letter queue (to determine queue name, refer to ZWMQ0053), access authorization restricts access to users requiring the ability to put messages to the dead-letter queue. This is difficult to determine. However, an item for concern may be a profile with * READ specified in the access list.

Note: If an alias queue is not used in place of the dead-letter queue, the RACF rules for the dead-letter queue will be coded to restrict unauthorized users and systems from reading the messages on the file.

The following is a sample of the commands required to allow a user (USER1) to get messages from or put messages to queues beginning with (PAY.) on subsystem (QM1):

TSS PER(USER1) MQQUEUE(QM1.PAY.) ACC(UPDATE)

STIG check 11 of 17 in the zOS WebSphere MQ for TSS STIG checklist

← Previous · V-225632WebSphere MQ dead letter and alias dead letter queues are not properly defined.Next · V-225634 →WebSphere MQ Process resources must be protected in accordance with security requirements.