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

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.

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

- SENSITVE.RPT(MQPROC). - SENSITVE.RPT(MXPROC). - ACF2CMDS.RPT(RESOURCE) - Alternate report.

For all process resources (i.e., ssid.processname) defined to TYPE(MQP) or TYPE(MXP) (i.e., MQPROC or MXPROC resource class, if SCYCASE is set to MIXED), verify 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).

The ISSO will ensure that process security is active, all profiles are defined to the MQPROC class, and process inquiries are restricted to READ access.

For all process resources (i.e., ssid.processname) defined to TYPE(MQP) (i.e., 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.

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

Example:

$KEY(ssid) TYPE(MQP) CHL_TRIG_PROCESS UID(MQAdministrators) SERVICE(READ) LOG CHL_TRIG_PROCESS UID(*) PREVENT SYSTEM.DEFAULT.PROCESS UID(MQAdministrators) SERVICE(READ) LOG SYSTEM.DEFAULT.PROCESS UID(*) PREVENT