← Back to zOS WebSphere MQ for TSS Security Technical Implementation Guide

V-225634

CAT II (Medium)

WebSphere MQ Process resources must be protected in accordance with security requirements.

Rule ID

SV-225634r1146230_rule

STIG

zOS WebSphere MQ for TSS 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 TSS Data Collection:

- SENSITVE.RPT(WHOHMPRO).
- SENSITVE.RPT(WHOHXPRO).

For all process resources (i.e., ssid.processname) defined to MQPROC resource class (or MXPROC resource class , if SCYCASE is set to MIXED), ensure access authorization restricts access to users requiring the ability to make process inquiries. 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

For all process resources (i.e., ssid.processname) defined to MQPROC or MXPROC resource class, ensure access authorization restricts access to users requiring the ability to make process inquiries. 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).

The following is a sample of the commands required to allow a user (USER1) to inquire on processes beginning with the letter V on queue manager (QM1):

TSS ADD(USER1) FAC(QM1MSTR)
TSS PER(USER1) MQPROC(QM1.V) ACC(READ) 
      ACTION(AUDIT)