Rule ID
SV-225638r1146242_rule
Version
V7R2
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 Data Set and Resource Data Collection: - SENSITVE.RPT(WHOHMCMD). For all command resources (i.e., ssid.command) defined to MQCMDS resource class, if the following guidance is true, this is not a finding. Note: ssid is the queue manager name (a.k.a., subsystem identifier). Access authorization restricts access to the appropriate personnel as designated in the WebSphere MQ COMMAND SECURITY CONTROLS Table in the z/OS STIG Addendum. All command access is logged as designated in the WebSphere MQ COMMAND SECURITY CONTROLS Table in the z/OS STIG Addendum.
Command security validates userids authorized to issue 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). Access authorization restricts access to the appropriate personnel as designated in the table titled "WebSphere MQ Command Security Controls " in the zOS STIG Addendum. All command access is logged as designated in the table titled "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)