WebSphere MQ command resources defined to MQCMDS resource class are not protected in accordance with security requirements.

From z/OS TSS STIG

Part of ZWMQ0059

Associated with: CCI-000213 CCI-002234

SV-7555r2_rule WebSphere MQ command resources defined to MQCMDS resource class are not protected in accordance with security requirements.

Vulnerability 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

a) Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(WHOHMCMD) b) For all command resources (i.e., ssid.command) defined to MQCMDS resource class, ensure the following items are in effect: NOTE: ssid is the queue manager name (a.k.a., subsystem identifier). 1) Access authorization restricts access to the appropriate personnel as designated in the Websphere MQ COMMAND SECURITY CONTROLS Table in the z/OS STIG Addendum. 2) All command access is logged as designated in the Websphere MQ COMMAND SECURITY CONTROLS Table in the z/OS STIG Addendum. c) If both of the items in (b) are true, there is NO FINDING. d) If either item in (b) is untrue, this is a FINDING.

Fix text

Command security validates userids authorized to issue MQSeries/WebSphere MQ commands. Command security will be active, and all profiles will be defined to the MQCMDS class. For all command resources (i.e., ssid.command) defined to MQCMDS resource class, ensure the following items are in effect: NOTE: ssid is the queue manager name (a.k.a., subsystem identifier). 1) Access authorization restricts access to the appropriate personnel as designated in the table entitled "Websphere MQ Command Security Controls " in the zOS STIG Addendum. 2) All command access is logged as designated in the table entitled "Websphere MQ Command Security Controls " in the zOS STIG Addendum. The following is a sample of the commands required to allow a systems programming group (SYS1) to issue the command CLEAR QLOCAL in subsystem QM1: TSS ADD(SYS1) FAC(QM1MSTR) TSS PER(SYS1) MQCMDS(QM1.CLEAR.LOCAL) ACC(ALTER) ACTION(AUDIT)

Pro Tips

Lavender hyperlinks in small type off to the right (of CSS class id, if you view the page source) point to globally unique URIs for each document and item. Copy the link location and paste anywhere you need to talk unambiguously about these things.

You can obtain data about documents and items in other formats. Simply provide an HTTP header Accept: text/turtle or Accept: application/rdf+xml.

Powered by sagemincer