None Computing title zOS WebSphere MQ for ACF2 Security Technical Implementation Guide version 7 releaseinfo Release: 2 Vuln_Num V-224354 Rule_ID SV-224354r1144153_rule Severity high Rule_Title WebSphere MQ channel security must be implemented in accordance with security requirements. Vuln_Discuss WebSphere MQ Channel security can be configured to provide authentication, message privacy, and message integrity between queue managers. Secure Sockets Layer (SSL) uses encryption techniques, digital signatures and digital certificates to provide message privacy, message integrity and mutual authentication between clients and servers. Failure to properly secure a WebSphere MQ channel may lead to unauthorized access. This exposure could compromise the availability, integrity, and confidentiality of some system services, applications, and customer data. Satisfies: SRG-OS-000505, SRG-OS-000555 Check_Content Refer to the following report produced by the z/OS Data Collection: - MQSRPT(ssid). Note: ssid is the queue manager name (a.k.a., subsystem identifier). Collect the following Information for WebSphere MQ queue manager. - If a WebSphere MQ queue manager communicates with another WebSphere MQ queue manager, provide the WebSphere MQ queue manager and channel names used to connect these queue managers. Automated Analysis requires Additional Analysis. Automated Analysis Refer to the following report produced by the z/OS Data Collection: - PDI(ZWMQ0011) If the following guidelines are true for each channel definition displayed from the DISPLAY CHANNEL command, this is not a finding. Verify that each WebSphere MQ channel is using SSL by checking for the SSLCIPH parameter, which must specify a FIPS 140-2 compliant value of the following: (Note: Both ends of the channel must specify the same cipher specification.) ECDHE_ECDSA_AES_128_CBC_SHA256 ECDHE_ECDSA_AES_256_CBC_SHA384 ECDHE_RSA_AES_128_CBC_SHA256 ECDHE_RSA_AES_256_CBC_SHA384 TLS_RSA_WITH_3DES_EDE_CBC_SHA TLS_RSA_WITH_AES_128_CBC_SHA TLS_RSA_WITH_AES_128_CBC_SHA256 TLS_RSA_WITH_AES_256_CBC_SHA TLS_RSA_WITH_AES_256_CBC_SHA256 Repeat the above step for each queue manager ssid identified. Fix_Text Review the WebSphere MQ Screen interface invoked by the REXX CSQOREXX. Review the channel's SSLCIPH setting. Display the channel properties and look for the "SSL Cipher Specification" value. Ensure that a FIPS 140-2 compliant value is shown. ECDHE_ECDSA_AES_128_CBC_SHA256 ECDHE_ECDSA_AES_256_CBC_SHA384 ECDHE_RSA_AES_128_CBC_SHA256 ECDHE_RSA_AES_256_CBC_SHA384 TLS_RSA_WITH_3DES_EDE_CBC_SHA TLS_RSA_WITH_AES_128_CBC_SHA TLS_RSA_WITH_AES_128_CBC_SHA256 TLS_RSA_WITH_AES_256_CBC_SHA TLS_RSA_WITH_AES_256_CBC_SHA256 Note that both ends of the channel must specify the same cipher specification. Repeat these steps for each queue manager ssid identified. Not_Reviewed Vuln_Num V-224355 Rule_ID SV-224355r1144155_rule Severity medium Rule_Title WebSphere MQ channel security is not implemented in accordance with security requirements. Vuln_Discuss WebSphere MQ channel security can be configured to provide authentication, message privacy, and message integrity between queue managers. WebSphere MQ channels use SSL encryption techniques, digital signatures and digital certificates to provide message privacy, message integrity and mutual authentication between clients and servers. Failure to properly secure a WebSphere MQ channel may lead to unauthorized access. This exposure could compromise the availability, integrity, and confidentiality of some system services, applications, and customer data. Check_Content Refer to the following report produced by the z/OS Data Collection: - MQSRPT(ssid). Note: ssid is the queue manager name (a.k.a., subsystem identifier). To determine which Release of WebSphere MQ, review ssid reports for message CSQU000I. Collect the following Information for each WebSphere MQ queue manager. - If a WebSphere MQ queue manager communicates with another WebSphere MQ queue manager, provide the WebSphere MQ queue manager and channel names used to connect these queue managers. - If any WebSphere MQ channels are used to communicate within the enclave, provide a list of channels and provide documentation regarding the sensitivity of the information on the channel. Review the ssid report(s) and perform the following steps. If the following guidance for each queue manager ssid is true, this is not a finding. Find the DISPLAY QMGR DEADQ, SSLKEYR, SCYCASE command to locate the start of the Queue Manager definitions. Verify that each WebSphere MQ 5.3 queue manager is using a digital certificate by reviewing the SSLKEYR parameter to verify that a keyring is identified, i.e., SSLKEYR(sslkeyring-id). SSLKEYR(sslkeyring-id). Issue the following ACF2 command, where ssidCHIN is the lid for the WebSphere MQ Channel Initiator's userid and sslkeyring-id is obtained from the above action: LIST ssidCHIN PROFILE(KEYRING) In the output of the above LIST command, obtain the keyring-default from the DEFAULT entry for KEYRING entry with RINGNAME of sslkeyring-id. Use this keyring-default in the following command: SET PROFILE(USER) DIV(CERTDATA) LIST keyring-default Review the ISSUERDN field for the CERTDATA record for the following. OU=PKI.OU=DoD.O=U.S. Government.C=US OU=ECA.O=U.S. Government.C=US Repeat these steps for each queue manager ssid identified. Fix_Text Refer to the following report produced by the z/OS Data Collection: - MQSRPT(ssid) Note: ssid is the queue manager name (a.k.a., subsystem identifier). Find the DISPLAY QMGR SSLKEYR command to locate the start of the Queue Manager definitions. Verify that each WebSphere MQ queue manager is using a digital certificate by reviewing the SSLKEYR parameter to ensure that a keyring is identified. i.e. SSLKEYR(sslkeyring-id) Issue the following ACF2 command, where ssidCHIN is the lid for the WebSphere MQ Channel Initiator's userid and sslkeyring-id is obtained from the above action: LIST ssidCHIN PROFILE(CERTDATA, KEYRING) The output will contain information on the CERTDATA and KEYRING records for the user. Find the CERTDATA entry that has a Key ring name field with sslkeyring-id. Review the ISSUERDN field for this CERTDATA record for the following: OU=PKI.OU=DoD.O=U.S. Government.C=US OU=ECA.O=U.S. Government.C=US Note: The Certificate Label Name is case sensitive. Review the Issuer's Name field in the resulting output for information of any of the following: OU=PKI.OU=DoD.O=U.S. Government.C=US OU=ECA.O=U.S. Government.C=US Repeat these steps for each queue manager ssid identified. To implement the requirements stated above, the following two items are provided which attempt to assist with (1) Technical "how to" information and (2) A DISA Point of contact for obtaining SSL certificates for CSD WebSphere MQ channels: Review the information available on setting up SSL, Keyrings, and Digital Certificates in the CA-ACF2 Security for z/OS Administrators Guide as well as the WebSphere MQ Security manual. Also review the information contained in the documentation provided as part of the install package from the DISA SSO Resource Management Factory (formerly Software Factory). For information on obtaining an SSL certificate in the DISA CSD environment, send email inquiry to disaraoperations@disa.mil. Not_Reviewed Vuln_Num V-224356 Rule_ID SV-224356r1144158_rule Severity medium Rule_Title Production WebSphere MQ Remotes must utilize Certified Name Filters (CNF). Vuln_Discuss IBM WebSphere MQ can use a user ID associated with an ACP certificate as a channel user ID. When an entity at one end of an SSL channel receives a certificate from a remote connection, the entity asks The ACP if there is a user ID associated with that certificate. The entity uses that user ID as the channel user ID. If there is no user ID associated with the certificate, the entity uses the user ID under which the channel initiator is running. Without a validly defined Certificate Name Filter for the entity IBM WebSphere MQ will set the channel user ID to the default. Check_Content Validate that the list of all Production WebSphere MQ Remotes exists and contains approved Certified Name Filters and associated USERIDS. If the filter(s) is (are) defined, accurate and has been approved by Vulnerability ICER0030 and the associated USERID(s) is only granted need to know permissions and authority to resources and commands, this is not a finding. If there is no Certificate Name Filter for WebSphere MQ Remotes this is a finding. Note: Improper use of CNF filters for MQ Series will result in the following Message ID. CSQX632I found in the following example: CSQX632I csect-name SSL certificate has no associated user ID, remote channel channel-name - channel initiator user ID used Fix_Text The responsible MQ systems programmer(s) shall create and maintain a spreadsheet that contains a list of all Production WebSphere MQ Remotes, associated individual USERIDs with corresponding valid Certified Name Filters (CNF). This documentation will be reviewed and validated annually by responsible MQ systems programmer(s) and forwarded for approval by the ISSM. The ISSO will define the associated USERIDs, the CNF, and grant the minimal need-to-know access by granting only the required resources and Commands for each USERID in the ACP. Refer to IBM WebSphere MQ Security manual for details on defining CNF for WebSphere MQ. Generic access shall not be granted such as resource permission at the SSID. MQ resource level. Not_Reviewed Vuln_Num V-224357 Rule_ID SV-224357r1144159_rule Severity medium Rule_Title User timeout parameter values for WebSphere MQ queue managers are not specified in accordance with security requirements. Vuln_Discuss Users signed on to a WebSphere MQ queue manager could leave their terminals unattended for long periods of time. This may allow unauthorized individuals to gain access to WebSphere MQ resources and application data. This exposure could compromise the availability, integrity, and confidentiality of some system services and application data. Check_Content Refer to the following report produced by the z/OS Data Collection: - MQSRPT(ssid). Note: ssid is the queue manager name (a.k.a., subsystem identifier). Automated Analysis Refer to the following report produced by the z/OS Data Collection: - PDI(ZWMQ0020) Review the ssid report(s) and perform the following steps: Find the DISPLAY SECURITY command to locate the start of the security parameter settings. Review the CSQH015I and CSQH016I messages to determine the Timeout and Interval parameter settings respectively. Repeat these steps for each queue manager ssid. The standard values are: TIMEOUT(15) INTERVAL(5) If the Timeout and Interval values conform to the standard values, this is not a finding. Fix_Text Review the WebSphere MQ System Setup Guide and the information on the ALTER SECURITY command in the WebSphere MQ Script (MQSC) Command Reference. Ensure the values for the TIMEOUT and INTERVAL parameters are specified in accordance with security requirements. Not_Reviewed Vuln_Num V-224358 Rule_ID SV-224358r1144160_rule Severity medium Rule_Title WebSphere MQ started tasks are not defined in accordance with the proper security requirements. Vuln_Discuss 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. Check_Content 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. Fix_Text 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 Not_Reviewed Vuln_Num V-224359 Rule_ID SV-224359r1144162_rule Severity medium Rule_Title WebSphere MQ all update and alter access to MQSeries/WebSphere MQ product and system datasets are not properly restricted. Vuln_Discuss MVS datasets provide the configuration, operational, and executable properties of WebSphere MQ. Some datasets are responsible for the security implementation of WebSphere MQ. Failure to properly protect these datasets may lead to unauthorized access. This exposure could compromise the availability, integrity, and confidentiality of system services, applications, and customer data. Check_Content Refer to the following report produced by the ACP Data Collection: - SENSITVE.RPT(MQSRPT). Verify ACP datasets rules for WebSphere MQ system datasets (e.g., SYS2.MQM.) restrict access as follows. If the following guidance is true, this is not a finding. Note: ssid is the queue manager name (a.k.a., subsystem identifier). If the following guidance is true, this is not a finding. The ACP dataset rules for the datasets restrict READ access to datasets referenced by the following DDnames, restricted to WebSphere MQ STCs, WebSphere MQ administrators, and systems programming personnel. All access to these datasets is logged. DDname Procedure Description CSQINP1 ssidMSTR Input parameters CSQINP2 ssidMSTR Input parameters CSQXLIB ssidCHIN User exit library The ACP dataset rules for the datasets restrict WRITE and/or greater access to the above datasets to WebSphere MQ administrators and systems programming personnel. The ACP dataset rules for the datasets restrict WRITE and/or greater access to datasets referenced by the following DDnames, restricted to WebSphere MQ STCs, WebSphere MQ administrators, and systems programming personnel. All WRITE and/or greater access to these datasets is logged. DDname Procedure Description CSQPxxxx ssidMSTR Page datasets BSDSx ssidMSTR Bootstrap datasets CSQOUTx ssidMSTR SYSOUT datasets CSQSNAP ssidMSTR DUMP dataset (See note) ssidMSTR Log datasets Note: To determine the log dataset names, review the JESMSGLG file of the ssidMSTR active task(s). Find CSQJ001I messages to obtain dataset names. The ACP dataset rules for the datasets restrict ALTER access to archive datasets, restricted to WebSphere MQ STCs, WebSphere MQ administrator, and systems programming personnel. All ALTER access to these datasets is logged. Note: To determine the archive datasets names, review the JESMSGLG file of the ssidMSTR active task(s). Find the CSQY122I message to obtain the ARCPRFX1 and ARCPRFX2 dataset high-level qualifiers. Except for the specific dataset requirements just mentioned, WRITE and/or greater access to all other WebSphere MQ system datasets is restricted to the WebSphere MQ administrator and systems programming personnel. Fix_Text The systems programmer will have the ISSO ensure that all WRITE and/or greater access to WebSphere MQ product and system datasets are restricted to WebSphere MQ administrators, systems programmers, and WebSphere MQ started tasks. The installation requires that the following datasets be APF authorized. hlqual.SCSQAUTH hlqual.SCSQLINK hlqual.SCSQANLx hlqual.SCSQSNL hlqual.SCSQMVR1 hlqual.SCSQMVR2 READ access to datasets referenced by the CSQINP1, CSQINP2, and CSQXLIB DDs in the queue manager's procedure will be restricted to the queue manager userid, WebSphere MQ administrator, and systems programming personnel. Log all access to these datasets. WRITE and/or greater access to dataset profiles protecting all page sets, logs, bootstrap datasets (BSDS), and datasets referenced by the CSQOUTX and CSQSNAP DDs in the queue manager's procedure will be restricted to the queue manager userid, WebSphere MQ administrator, and systems programming personnel. Log all WRITE and/or greater access to these datasets. ALTER access to all archive datasets in the queue manager's procedure will be restricted to the queue manager userid, WebSphere MQ administrator, and systems programming personnel. Log all ALTER access to these datasets. Not_Reviewed Vuln_Num V-224360 Rule_ID SV-224360r1144163_rule Severity medium Rule_Title WebSphere MQ resource classes must be properly activated. Vuln_Discuss 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 Refer to the following report produced by the ACF2 Data Collection: - ACF2CMDS.RPT(ACFGSO). Verify the System Authorization Facility Definition (SAFDEF) includes an entry for WebSphere MQ as follows, this is not a finding. INSERT SAFDEF.MQS ID(MQS) FUNCRET(8) RETCODE(4) MODE(IGNORE) - RACROUTE(REQUEST=EXTRACT,CLASS=MQADMIN) REP If the Internal CLASMAP Definitions do not include the following entries, this is a finding. INSERT CLASMAP.MQADMIN RESOURCE(MQADMIN) RSRCTYPE(MQA) ENTITYLN(62) INSERT CLASMAP.MQCMDS RESOURCE(MQCMDS) RSRCTYPE(MQC) ENTITYLN(22) INSERT CLASMAP.MQCONN RESOURCE(MQCONN) RSRCTYPE(MQK) ENTITYLN(10) INSERT CLASMAP.MQNLIST RESOURCE(MQNLIST) RSRCTYPE(MQN) ENTITYLN(53) INSERT CLASMAP.MQPROC RESOURCE(MQPROC) RSRCTYPE(MQP) ENTITYLN(53) INSERT CLASMAP.MQQUEUE RESOURCE(MQQUEUE) RSRCTYPE(MQQ) ENTITYLN(53) When SCYCASE is set to MIXED, CLASMAP Definitions must include the following entries: INSERT CLASMAP.MXADMIN RESOURCE(MXADMIN) RSRCTYPE(MXA) ENTITYLN(62) INSERT CLASMAP.MXNLIST RESOURCE(MXNLIST) RSRCTYPE(MXN) ENTITYLN(53) INSERT CLASMAP.MXPROC RESOURCE(MXPROC) RSRCTYPE(MXP) ENTITYLN(53) INSERT CLASMAP.MXQUEUE RESOURCE(MXQUEUE) RSRCTYPE(MXQ) ENTITYLN(53) INSERT CLASMAP.MXTOPIC RESOURCE(MXTOPIC) RSRCTYPE(MXT) ENTITYLN(246) Fix_Text The ISSO will ensure that all WebSphere MQ resources are active and properly defined. Ensure the System Authorization Facility Definition (SAFDEF) includes an entry for WebSphere MQ as follows: INSERT SAFDEF.MQS ID(MQS) FUNCRET(8) RETCODE(4) MODE(IGNORE) RACROUTE(REQUEST=EXTRACT,CLASS=MQADMIN) REP Ensure the Internal CLASMAP Definitions include the following entries: INSERT CLASMAP.MQADMIN RESOURCE(MQADMIN) RSRCTYPE(MQA) ENTITYLN(62) INSERT CLASMAP.MQQUEUE RESOURCE(MQQUEUE) RSRCTYPE(MQQ) ENTITYLN(53) INSERT CLASMAP.MQNLIST RESOURCE(MQNLIST) RSRCTYPE(MQN) ENTITYLN(53) INSERT CLASMAP.MQCMDS RESOURCE(MQCMDS) RSRCTYPE(MQC) ENTITYLN(22) INSERT CLASMAP.MQCONN RESOURCE(MQCONN) RSRCTYPE(MQK) ENTITYLN(10) INSERT CLASMAP.MQPROC RESOURCE(MQPROC) RSRCTYPE(MQP) ENTITYLN(53) When SCYCASE is set to mixed CLASMAP Definitions must include the following entries: INSERT CLASMAP.MXADMIN RESOURCE(MXADMIN) RSRCTYPE(MXA) ENTITYLN(62) INSERT CLASMAP.MXNLIST RESOURCE(MXNLIST) RSRCTYPE(MXN) ENTITYLN(53) INSERT CLASMAP.MXPROC RESOURCE(MXPROC) RSRCTYPE(MXP) ENTITYLN(53) INSERT CLASMAP.MXQUEUE RESOURCE(MXQUEUE) RSRCTYPE(MXQ) ENTITYLN(53) INSERT CLASMAP.MXTOPIC RESOURCE(MXTOPIC) RSRCTYPE(MXT) ENTITYLN(246) Not_Reviewed Vuln_Num V-224361 Rule_ID SV-224361r1144164_rule Severity high Rule_Title WebSphere MQ switch profiles must be properly defined to the appropriate class. Vuln_Discuss 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 Refer to the following report produced by the z/OS Data Collection: - MQSRPT(ssid). Automated Analysis requires Additional Analysis. Refer to the following report produced by the z/OS Data Collection: - PDI(ZWMQ0051) Note: ssid is the queue manager name (a.k.a., subsystem identifier). Review the Security switches identified in response to the DISPLAY SECURITY command in each ssid report(s). If all of the following switches specify ON, this is not a finding. SUBSYSTEM CONNECTION COMMAND CONTEXT ALTERNATE USER PROCESS NAMELIST QUEUE TOPIC COMMAND RESOURCES If SUBSYSTEM specifies OFF, this is a finding with a severity of Category I. If any of the other above switches specify OFF (other than the exception mentioned below), this is a finding and downgrade the severity to a Category II. If COMMAND RESOURCE Security switch specifies OFF, this is not a finding. Note: At the discretion of the ISSO, COMMAND RESOURCE Security switch may specify OFF by defining ssid.NO.CMD.RESC.CHECKS in the TYPE(MQA) (i.e., MQADMIN or MXADMIN if SCYCASE is set to MIXED). Fix_Text Ensure that all Switch Profiles do not have the resource ssid.NO defined to the MQADMIN (or MXADMIN if SCYCASE is set to MIXED) resource class with the exception of ssid.NO.CMD.RESC.CHECKS. ssid is the queue manager name (a.k.a., subsystem identifier). Ensure that all of the following switches specify ON. SUBSYSTEM CONNECTION COMMAND CONTEXT ALTERNATE USER PROCESS NAMELIST QUEUE COMMAND RESOURCES Example: $KEY(ssid) TYPE(MQA) ALTERNATE.USER.- UID(*) PREVENT CONTEXT.- UID(*) PREVENT RESLEVEL UID(*) PREVENT - UID(*) PREVENT Note: At the discretion of the ISSO, COMMAND RESOURCE Security switch may specify OFF by defining ssid.NO.CMD.RESC.CHECKS in the TYPE(MQA). Example: $KEY(ssid) TYPE(MQA) NO.CMD.RESC.CHECKS UID(*) PREVENT Not_Reviewed Vuln_Num V-224362 Rule_ID SV-224362r1144165_rule Severity medium Rule_Title WebSphere MQ connection class resources must be protected in accordance with security. Vuln_Discuss 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 Refer to the following report produced by the ACF2 Data Collection: - SENSITVE.RPT(MQCONN). - ACF2CMDS.RPT(RESOURCE) - Alternate report. Review the following connection resources defined to TYPE(MQK) (i.e., MQCONN resource class): Resource Authorized Users ssid.BATCH TSO and batch job userids ssid.CICS CICS region userids ssid.IMS IMS region userids ssid.CHIN Channel initiator userids Note: ssid is the queue manager name (a.k.a., subsystem identifier). For all connection resources defined to TYPE(MQK) (i.e., MQCONN resource class). If the following guidance is true, this is not a finding. Access authorization to these connections restricts access to the appropriate users as indicated above. All access FAILUREs are logged. Fix_Text Ensure all connections to WebSphere MQ resources are restricted using connection security. Ensure the following connection resources defined to TYPE(MQK) (i.e., MQCONN resource class): Resource Authorized Users ssid.BATCH TSO and batch job userids ssid.CICS CICS region userids ssid.IMS IMS region userids ssid.CHIN Channel initiator userids Note: ssid is the queue manager name (a.k.a., subsystem identifier). For all connection resources defined to TYPE(MQK), ensure the following items are in effect: Access authorization to these connections restricts access to the appropriate users as indicated above. All access FAILURE is logged. Example: $KEY(ssid) TYPE(MQK) BATCH UID(STCssid) SERVICE(READ) BATCH UID(syspaudt) SERVICE(READ) BATCH UID(*) PREVENT CHIN UID(STCssidCHIN) SERVICE(READ) CHIN UID(*) PREVENT CICS UID(*) PREVENT IMS UID(*) PREVENT Not_Reviewed Vuln_Num V-224363 Rule_ID SV-224363r1144166_rule Severity medium Rule_Title WebSphere MQ dead letter and alias dead letter queues are not properly defined. Vuln_Discuss 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 Refer to the following report produced by the z/OS Data Collection: - MQSRPT(ssid). Note: ssid is the queue manager name (a.k.a., subsystem identifier). Review the ssid report(s) and perform the following steps: Find the DISPLAY QMGR DEADQ command to locate the start of the dead-letter queue information. Review the DEADQ parameter to obtain the name of the real dead-letter queue. From the top of the report, find the QUEUE(dead-letter.queue.name) entry to locate the start of the real dead-letter queue definition. Review the GET and PUT parameters to determine their values, and verify they conform to the specified security requirements. If the following values are set for the dead-letter.queue.name, this is not a finding. The standard values are: GET(ENABLED) PUT(ENABLED) Note: dead-letter.queue.name is the value of the DEADQ parameter determined above. From the top of the report, find the QUEUE(dead-letter.queue.name.PUT) entry to locate the start of the alias dead-letter queue definition. Review the GET and PUT parameters to determine their values, and verify they conform to those specified in the security requirements. If the following values are set for the dead-letter.queue.name.PUT, this is not a finding. The standard values are: GET(DISABLED) PUT(ENABLED) Note: Dead-letter.queue.name is the value of the DEADQ parameter determined above. Note: The TARGQ parameter value for the alias queue will be the real dead letter queue name. Note: If an alias queue is not used in place of the dead-letter queue, then the ACP rules for the dead-letter queue must be coded to restrict unauthorized users and systems from reading the messages on the file. Fix_Text The systems programmer responsible for supporting WebSphere MQ will ensure that the dead-letter queue and its alias are properly defined. The following scenario describes how to securely define a dead-letter queue: Define the real dead-letter queue with attributes PUT(ENABLED) and GET(ENABLED). Give update authority for the dead-letter queue to CKTI (the WebSphere MQ-supplied CICS task initiator), channel initiators, and any automated application used for dead-letter queue maintenance. Define an alias queue that resolves to the real dead-letter queue, but give the alias queue the attributes PUT(ENABLED) and GET(DISABLED). To put a message on the dead-letter queue, an application uses the alias queue. The application does the following: Retrieve the name of the real dead-letter queue. To do this, it opens the queue manager object using MQOPEN, and then issues an MQINQ to get the dead-letter queue name. Build the name of the alias queue by appending the characters ".PUT" to this name, in this case, ssid.DEAD.QUEUE.PUT. Open the alias queue, ssid.DEAD.QUEUE.PUT. Put the message on the real dead-letter queue by issuing an MQPUT against the alias queue. Give the userid associated with the application update authority to the alias, but no access to the real dead-letter queue. Note: If an alias queue is not used in place of the dead-letter queue, then the ACP rules for the dead-letter queue will be coded to restrict unauthorized users and systems from reading the messages on the file. Undeliverable messages can be routed to a dead-letter queue. Two levels of access should be established for these queues. The first level allows applications, as well as some WebSphere MQ objects, to put messages to this queue. The second level restricts the ability to get messages from this queue and protects sensitive data. This will be accomplished by defining an alias queue that resolves to the real dead-letter queue, but defines the alias queue with the attributes PUT(ENABLED) and GET(DISABLED). The ability to get messages from the dead-letter queue will be restricted to message channel agents (MCAs), CKTI (WebSphere MQ-supplied CICS task initiator), channel initiators utility, and any automated application used for dead-letter queue maintenance. Not_Reviewed Vuln_Num V-224364 Rule_ID SV-224364r1144167_rule Severity medium Rule_Title WebSphere MQ queue resource defined to the MQQUEUE or MXQUEUE resource class must be protected in accordance with security requirements. Vuln_Discuss 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 Refer to the following report produced by the z/OS Data Collection: - MQSRPT(ssid). Note: ssid is the queue manager name (a.k.a., subsystem identifier). Refer to the following report produced by the dataset and Resource Data Collection: - SENSITVE.RPT(MQQUEUE). - SENSITVE.RPT(MXQUEUE). - ACF2CMDS.RPT(RESOURCE) - Alternate report. For all queue identified by the DISPLAY QUEUE(*) ALL command in the MQSRPT(ssid), these queues will be prefixed by ssid to identify the resources to be protected. Verify these queue resources are defined to TYPE(MQQ) or TYPE(MXQ) (i.e., MQQUEUE or MXQUEUE resource class, if SCYCASE is set to MIXED). If the following guidance is true, this is not a finding. For message queues (i.e., ssid.queuename), access authorization restricts access to users requiring the ability to get messages from and put messages to message queues. This is difficult to determine. However, an item for concern may be a profile with * READ specified in the access list. Decentralized MQ Administrators, non-DECC datacenter users, can have up to ALTER access to the user Message Queues. For system queues (i.e., ssid.SYSTEM.queuename), access authorization restricts UPDATE and/or ALTER access to WebSphere MQ STCs, WebSphere MQ administrators, systems programming personnel, and CICS regions running WebSphere MQ applications. For the following system queues, verify that UPDATE access is restricted to Auditors and Users that require access to review message queues. ssid.SYSTEM.COMMAND.INPUT ssid.SYSTEM.COMMAND.REPLY ssid.SYSTEM.CSQOREXX.* ssid.SYSTEM.CSQUTIL.* For the real dead-letter queue (to determine queue name refer to ZWMQ0053), ALTER access authorization restricts access to WebSphere MQ STCs, WebSphere MQ administrators, CICS regions running WebSphere MQ applications, and any automated application used for dead-letter queue maintenance. For the alias dead-letter queue (to determine queue name refer to ZWMQ0053), UPDATE access authorization restricts access to users requiring the ability to put messages to the dead-letter queue. This is difficult to determine. However, an item for concern may be a profile with * READ specified in the access list. Fix_Text The ISSO will ensure that all WebSphere MQ queues are restricted using queue level security. Ensure all queue resources defined to TYPE(MQQ) (i.e., MQQUEUE OR m resource class), are in effect: For all queues identified by the DISPLAY QUEUE(*) ALL command in the MQSRPT(ssid), these queues will be prefixed by ssid to identify the resources to be protected. Ensure these queue resources are defined to TYPE(MQQ) (i.e., MQQUEUE OR MXQUEUE resource class. If the following guidance is true, this is not a finding. For message queues (i.e., ssid.queuename), access authorization restricts access to users requiring the ability to get messages from and put messages to message queues. This is difficult to determine. However, an item for concern may be a profile with * READ specified in the access list. Decentralized MQ Administrators, non-DECC datacenter users, can have up to ALTER access to the user Message Queues. For system queues (i.e., ssid.SYSTEM.queuename), access authorization restricts UPDATE and/or ALTER access to WebSphere MQ STCs, WebSphere MQ administrators, systems programming personnel, and CICS regions running WebSphere MQ applications. For the following system queues, ensure that UPDATE access is restricted to Auditors and Users that require access to review message queues. ssid.SYSTEM.COMMAND.INPUT ssid.SYSTEM.COMMAND.REPLY ssid.SYSTEM.CSQOREXX.* ssid.SYSTEM.CSQUTIL.* For the real dead-letter queue (to determine queue name refer to ZWMQ0053), ALTER access authorization restricts access to WebSphere MQ STCs, WebSphere MQ administrators, CICS regions running WebSphere MQ applications, and any automated application used for dead-letter queue maintenance. For the alias dead-letter queue (to determine queue name refer to ZWMQ0053), UPDATE access authorization restricts access to users requiring the ability to put messages to the dead-letter queue. This is difficult to determine. However, an item for concern may be a profile with * READ specified in the access list. Example: $KEY(ssid) TYPE(MQQ) DEAD.QUEUE UID(STCssidCHIN) SERVICE(READ,UPDATE) LOG DEAD.QUEUE UID(MQAdministrators) SERVICE(READ,UPDATE) LOG DEAD.QUEUE UID(*) PREVENT - UID(*) PREVENT Not_Reviewed Vuln_Num V-224365 Rule_ID SV-224365r1144168_rule Severity medium Rule_Title WebSphere MQ Process resources must be protected in accordance with security requirements. Vuln_Discuss 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 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). Fix_Text 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 Not_Reviewed Vuln_Num V-224366 Rule_ID SV-224366r1144169_rule Severity medium Rule_Title WebSphere MQ Namelist resources must be protected in accordance with security requirements. Vuln_Discuss 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 Refer to the following report produced by the ACF2 Data Collection: - SENSITVE.RPT(MQNLIST). - SENSITVE.RPT(MXNLIST). - ACF2CMDS.RPT(RESOURCE) - Alternate report. For all namelist resources (i.e., ssid.namelist) defined to TYPE(MQN) or TYPE(MXN) (i.e., MQNLIST or MXNLIST resource class, if SCYCASE is set to MIXED), verify access authorization restricts access to users requiring the ability to make namelist 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). Fix_Text The ISSO will ensure that all WebSphere MQ namelist resources are restricted to authorized users. For all namelist resources (i.e., ssid.namelist) defined to TYPE(MQN) (i.e., MQNLIST resource class or MXNLIST resource class if SCYCASE is set to MIXED), ensure access authorization restricts access to users requiring the ability to make namelist 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(QZN1) TYPE(MQN) SYSTEM.DEFAULT.NAMELIST UID(MQAdministrators) SERVICE(READ) LOG SYSTEM.DEFAULT.NAMELIST UID(*) PREVENT Not_Reviewed Vuln_Num V-224367 Rule_ID SV-224367r1144170_rule Severity medium Rule_Title WebSphere MQ alternate user resources defined to the appropriate resource class must be protected in accordance with security requirements. Vuln_Discuss 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 Refer to the following report produced by the ACF2 Data Collection: - SENSITVE.RPT(MQADMIN). - SENSITVE.RPT(MXADMIN). - ACF2CMDS.RPT(RESOURCE) - Alternate report. For all alternate user resources (i.e., ssid.ALTERNATE.USER.alternatelogonid) 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 use the alternate userid. 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). Fix_Text The ISSO will ensure that use of alternate userids is restricted to authorized personnel. For all alternate user resources (i.e., ssid.ALTERNATE.USER.alternatelogonid) defined to TYPE(MQA) (MQADMIN resource class or MXADMIN if SCYCASE is set to MIXED), ensure access authorization restricts access to users requiring the ability to use the alternate userid. 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) ALTERNATE.USER.- UID(CICS support) SERVICE(READ,UPDATE) LOG ALTERNATE.USER.- UID(*) PREVENT Not_Reviewed Vuln_Num V-224368 Rule_ID SV-224368r1144172_rule Severity medium Rule_Title WebSphere MQ context resources defined to the appropriate resource class must be protected in accordance with security requirements. Vuln_Discuss 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 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). Fix_Text 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 Not_Reviewed Vuln_Num V-224369 Rule_ID SV-224369r1144194_rule Severity medium Rule_Title WebSphere MQ command resources defined to MQCMDS resource class are not protected in accordance with security requirements. Vuln_Discuss 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 Refer to the following report produced by the dataset and Resource Data Collection: - SENSITVE.RPT(MQCMDS). - ACF2CMDS.RPT(RESOURCE) - Alternate report. For all command resources (i.e., ssid.command) defined to TYPE(MQC) (i.e., 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. Fix_Text The ISSO will ensure that all WebSphere MQ commands are restricted to authorized personnel. For all command resources (i.e., ssid.command) defined to TYPE(MQC) (i.e., 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. Example: $KEY(ssid) TYPE(MQC) ALTER.- UID(syspaudt) SERVICE(READ,ADD,UPDATE) LOG ALTER.- UID(*) PREVENT SET R(MQC) COMPILE 'ACF2.MVA.MQC(ssid)' STORE F ACF2,REBUILD(MQC) Not_Reviewed Vuln_Num V-224370 Rule_ID SV-224370r1144174_rule Severity medium Rule_Title WebSphere MQ RESLEVEL resources in the appropriate ADMIN resource class must be protected in accordance with security requirements. Vuln_Discuss 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 Refer to the following report produced by the dataset and Resource Data Collection: - SENSITVE.RPT(MQADMIN). - SENSITVE.RPT(MXADMIN). - ACF2CMDS.RPT(RESOURCE) - Alternate report. Automated Analysis Refer to the following report produced by the dataset and Resource Data Collection: - PDI(ZWMQ0060). If the following guidance is true, this is not a finding. Note: ssid is the queue manager name (a.k.a., subsystem identifier). A RESLEVEL resource (i.e., ssid.RESLEVEL) is defined for each queue manager to TYPE(MQA) or TYPE(MXA) (i.e., MQADMIN or MXADMIN resource class, if SCYCASE is set to MIXED) with a default access of PREVENT. Access authorization to these RESLEVEL resources restricts all access. No users are permitted access to ssid.RESLEVEL resources. Fix_Text Ensure that a ssid.RESLEVEL profile is only defined for each queue manager. Ensure the following items are in effect: Note: ssid is the queue manager name (a.k.a., subsystem identifier). A RESLEVEL resource (i.e., ssid.RESLEVEL) is defined for each queue manager to TYPE(MQA) (i.e., MQADMIN or MZADMIN resource class) with a default access of PREVENT. Access authorization to these RESLEVEL resources restricts all access. No users are permitted access to ssid.RESLEVEL resources. Example: $KEY(ssid) TYPE(MQA) RESLEVEL UID(*) PREVENT Not_Reviewed