WebSphere MQ started tasks are not defined in accordance with the proper security requirements.

Started tasks are used to execute WebSphere MQ queue manager services. Improperly defined WebSphere MQ started tasks may result in inappropriate access to application resources and the loss of accountability. This exposure could compromise the availability of some system services and application data.

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

- ACF2CMDS.RPT(LOGONIDS). - ACF2CMDS.RPT(ATTSTC).

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

Provide a list of all WebSphere MQ Subsystem IDs (Queue managers) and Release levels.

ssidMSTR is the name of a queue manager STC. ssidCHIN is the name of a distributed queuing (a.k.a., channel initiator) STC.

Review WebSphere MQ started tasks and verify the following items are in effect. If they are, this is not a finding.

Each ssidMSTR and ssidCHIN started task is associated with a unique logonid. Each ssidMSTR and ssidCHIN STC logonid has the following attributes defined.

STC MUSASS NOSMC

Repeat these steps for each queue manager ssid.

The ISSO will ensure that all WebSphere MQ started tasks are properly defined.

Review WebSphere MQ started tasks and ensure the following items are in effect:

Note: ssid is the queue manager name (a.k.a., subsystem identifier). ssidMSTR is the name of a queue manager STC. ssidCHIN is the name of a distributed queuing (a.k.a., channel initiator) STC.

Each WebSphere MQ started task is associated with a unique logonid.

Each WebSphere MQ STC logonid has the attributes of STC, MUSASS, and NOSMC.

Example:

SET LID INSERT ssid.MSTR NAME(MQseries, STC) STC MUSASS NO-SMC

INSERT ssid.CHIN NAME(MQseries, STC) STC MUSASS NO-SMC