WebSphere MQ context resources defined to the appropriate resource class 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(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).

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