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 ACF2 Security Technical Implementation Guide

V-224368

CAT II (Medium)

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

Rule ID

SV-224368r1144172_rule

STIG

zOS WebSphere MQ for ACF2 Security Technical Implementation Guide

Version

V7R2

CCIs

CCI-000213

Discussion

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.

Check Content

Refer to the following report produced by the ACF2 Data Collection:

- SENSITVE.RPT(MQADMIN).
- SENSITVE.RPT(MXADMIN).
- ACF2CMDS.RPT(RESOURCE) - Alternate report.

For all context resources (i.e., ssid.CONTEXT) defined to TYPE(MQA) or TYPE(MXA) (i.e., MQADMIN or MXADMIN resource class, if SCYCASE is set to MIXED), verify access authorization restricts access to users requiring the ability to pass or set identity and/or origin data for a message. This is difficult to determine. However, an item for concern may be a profile with * READ specified in the access list. If this guidance is true, this is not a finding.

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

Fix Text

The ISSO will ensure that use of context resources is restricted to authorized personnel.

For all context resources (i.e., ssid.CONTEXT) defined to TYPE(MQA) (i.e., MQADMIN resource class or MXADMIN if SCYCASE is set to MIXED), ensure access authorization restricts access to users requiring the ability to pass or set identity and/or origin data for a message. This is difficult to determine. However, an item for concern may be a profile with * READ specified in the access list.

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

Example:

$KEY(ssid) TYPE(MQA)
CONTEXT.- UID (CICS SUPPORT) LOG
CONTEXT.- UID(*) PREVENT