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 channel security is not implemented in accordance with security requirements.

zOS WebSphere MQ for TSS Security Technical Implementation Guide

Assessment Title

Rule Text

WebSphere MQ channel security is not implemented in accordance with security requirements.

Description

Discussion Text

WebSphere MQ channel security can be configured to provide authentication, message privacy, and message integrity between queue managers. WebSphere MQ channels use SSL encryption techniques, digital signatures and digital certificates to provide message privacy, message integrity and mutual authentication between clients and servers.

Failure to properly secure a WebSphere MQ channel may lead to unauthorized access. This exposure could compromise the availability, integrity, and confidentiality of some system services, applications, and customer data.

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

Objective

V-225624

Rule

SV-225624r1146202_rule

Severity

medium

Rule Version

ZWMQ0012

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).

To determine which Release of WebSphere MQ, review ssid reports for message CSQU000I. Collect the following Information for each WebSphere MQ queue manager.

- If a WebSphere MQ queue manager communicates with another WebSphere MQ queue manager, provide the WebSphere MQ queue manager and channel names used to connect these queue managers.
- If any WebSphere MQ channels are used to communicate within the enclave, provide a list of channels and provide documentation regarding the sensitivity of the information on the channel.

Review the ssid report(s) and perform the following steps. If the following guidance for each queue manager ssid is true, this is not a finding.

Find the DISPLAY QMGR DEADQ, SSLKEYR, SCYCASE command to locate the start of the Queue Manager definitions.

Verify that each WebSphere MQ 5.3 queue manager is using a digital certificate by reviewing the SSLKEYR parameter to ensure that a keyring is identified. i.e., SSLKEYR(sslkeyring-id).

Issue the following TSS commands, where ssidCHIN is the Acid for the WebSphere MQ Channel Initiator's userid and sslkeyring-id is obtained from the above action:

TSS LIST(ssidCHIN) KEYRING(sslkeyring-id)

Note: The sslkeyring-id is case sensitive.

In the output find the DIGICERT field for ACID(ssidCHIN). Use this DIGICERT in the following command:

TSS LIST(ssidCHIN) DIGICERT(digicert)

Note: The digicert is case sensitive.

Review the ISSUER DISTINGUISHED NAME field in the resulting output for information of any of the following:

OU=PKI.OU=DoD.O=U.S. Government.C=US
OU=ECA.O=U.S. Government.C=US

Repeat these steps for each queue manager ssid identified.

Implementation Procedure

Fix 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). 

Find the DISPLAY QMGR SSLKEYR command to locate the start of the queue manager definitions.
Verify that each WebSphere MQ queue manager is using a digital certificate by reviewing the SSLKEYR parameter to ensure that a keyring is identified - i.e., SSLKEYR(sslkeyring-id)
Issue the following TSS commands, where ssidCHIN is the lid for the WebSphere MQ Channel Initiator's userid and sslkeyring-id is obtained from the above action:

TSS LIST(ssidCHIN) KEYRING(sslkeyring-id)

Note: The sslkeyring-id is case sensitive.

In the output find the DIGICERT field for ACID(ssidCHIN). Use this DIGICERT in the following command:

TSS LIST(ssidCHIN) DIGICERT(digicert)

Note: The Certificate Label Name is case sensitive.

Review the Issuer's Name field in the resulting output for information of any of the following:

OU=PKI.OU=DoD.O=U.S. Government.C=US
OU=ECA.O=U.S. Government.C=US

Repeat these steps for each queue manager ssid identified.

To implement the requirements stated above, the following two items are provided which attempt to assist with (1) Technical "how to" information and (2) A DISA Point of contact for obtaining SSL certificates for CSD WebSphere MQ channels:

Review the information available on setting up SSL, Keyrings, and Digital Certificates in the CA TSS Cookbook regarding usage of the TSS commands to administer PKI Certificates as well as the WebSphere MQ Security manual. Also review the information contained in the documentation provided as part of the install package from the DISA SSO Resource Management Factory (formerly Software Factory).

For information on obtaining an SSL certificate in the DISA CSD environment, send email inquiry to disaraoperations@disa.mil for more information.

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

← Previous · V-225623WebSphere MQ channel security must be implemented in accordance with security requirements.Next · V-225625 →Production WebSphere MQ Remotes must utilize Certified Name Filters (CNF).