Cyber Trackr - Free Compliance Library
Cyber Trackr
The Free Compliance Library

zOS WebSphere MQ for TSS Security Technical Implementation Guide - V7R2

  • Version/Release: V7R2
  • Published: 2025-09-28
  • Released: 2025-10-01
  • Expand All:
  • Severity:
  • Sort:
Compare

Select any two versions of this STIG to compare the individual requirements

View

Select any old version/release of this STIG to view the previous requirements

This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DOD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.
c
WebSphere MQ channel security must be implemented in accordance with security requirements.
AC-17 - High - CCI-000068 - V-225623 - SV-225623r1146199_rule
RMF Control
AC-17
Severity
High
CCI
CCI-000068
Version
ZWMQ0011
Vuln IDs
  • V-225623
  • V-6958
Rule IDs
  • SV-225623r1146199_rule
  • SV-7259
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
Checks: C-27324r1146197_chk

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: F-27312r1146198_fix

The systems programmer and the ISSO will review the WebSphere MQ Screen interface invoked by the REXX CSQOREXX, reviewing 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.

b
WebSphere MQ channel security is not implemented in accordance with security requirements.
SC-23 - Medium - CCI-002470 - V-225624 - SV-225624r1146202_rule
RMF Control
SC-23
Severity
Medium
CCI
CCI-002470
Version
ZWMQ0012
Vuln IDs
  • V-225624
  • V-6980
Rule IDs
  • SV-225624r1146202_rule
  • SV-111901
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.
Checks: C-27325r1146200_chk

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 ensure that a keyring is identified. i.e., SSLKEYR(sslkeyring-id). Issue the following TSS commands, where ssidCHIN is the Acid for the WebSphere MQ Channel Initiator's userid and sslkeyring-id is obtained from the above action: TSS LIST(ssidCHIN) KEYRING(sslkeyring-id) Note: The sslkeyring-id is case sensitive. In the output find the DIGICERT field for ACID(ssidCHIN). Use this DIGICERT in the following command: TSS LIST(ssidCHIN) DIGICERT(digicert) Note: The digicert is case sensitive. Review the ISSUER DISTINGUISHED 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.

Fix: F-27313r1146201_fix

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 TSS commands, where ssidCHIN is the lid for the WebSphere MQ Channel Initiator's userid and sslkeyring-id is obtained from the above action: TSS LIST(ssidCHIN) KEYRING(sslkeyring-id) Note: The sslkeyring-id is case sensitive. In the output find the DIGICERT field for ACID(ssidCHIN). Use this DIGICERT in the following command: TSS LIST(ssidCHIN) DIGICERT(digicert) 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 TSS Cookbook regarding usage of the TSS commands to administer PKI Certificates 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 for more information.

b
Production WebSphere MQ Remotes must utilize Certified Name Filters (CNF).
CM-6 - Medium - CCI-000366 - V-225625 - SV-225625r1146204_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
ZWMQ0014
Vuln IDs
  • V-225625
  • V-31561
Rule IDs
  • SV-225625r1146204_rule
  • SV-41848
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.
Checks: C-27326r868772_chk

Validate that the list of all Production WebSphere MQ Remotes exist, 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: F-27314r1146203_fix

The responsible MQ systems programmer(s) will create and maintain a spreadsheet that contains a list of all Production WebSphere MQ Remotes and 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 the IBM WebSphere MQ Security manual for details on defining CNF for WebSphere MQ. Generic access will not be granted, such as resource permission at the SSID MQ resource level.

b
User timeout parameter values for WebSphere MQ queue managers are not specified in accordance with security requirements.
SC-10 - Medium - CCI-001133 - V-225626 - SV-225626r1146206_rule
RMF Control
SC-10
Severity
Medium
CCI
CCI-001133
Version
ZWMQ0020
Vuln IDs
  • V-225626
  • V-3903
Rule IDs
  • SV-225626r1146206_rule
  • SV-3903
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.
Checks: C-27327r1146205_chk

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: F-27315r1070322_fix

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.

b
WebSphere MQ started tasks are not defined in accordance with the proper security requirements.
IA-2 - Medium - CCI-000764 - V-225627 - SV-225627r1146209_rule
RMF Control
IA-2
Severity
Medium
CCI
CCI-000764
Version
ZWMQ0030
Vuln IDs
  • V-225627
  • V-3904
Rule IDs
  • SV-225627r1146209_rule
  • SV-7527
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.
Checks: C-27328r1146207_chk

Refer to the following reports produced by the TSS Data Collection: - TSSCMDS.RPT(#STC). - TSSCMDS.RPT(@ACIDS). - TSSCMDS.RPT(FACLIST) - Preferred report containing all control option values in effect including default values. - TSSCMDS.RPT(TSSPRMFL) - Alternate report containing only control option values explicitly coded at TSS startup. Note: The FACLIST report must be created by security personnel. The TSSPRMFL report can be used if security personnel have not executed the required steps documented in the TSS Data Collection. 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. Review WebSphere MQ started tasks and ensure the following items are in effect, this is not a finding. For ssidMSTR FACILITY(STC, BATCH) PASSWORD(xxxxxxxx,0) SOURCE(INTRDR) NOSUSPEND MASTFAC(ssidMSTR) For ssidCHIN FACILITY(STC, BATCH) PASSWORD(xxxxxxxx,0) SOURCE(INTRDR) NOSUSPEND WebSphere MQ queue manager facilities is defined to the Facility Matrix Table using the following sample commands: FAC(USERxx=NAME=ssidMSTR,MODE=FAIL,PGM=CSQ,ID=xx,ACTIVE) FAC(ssidMSTR=SHRPRF,ASUBM,NOABEND,MULTUSER,XDEF,LUMSG) FAC(ssidMSTR=STMSG,SIGN(S),INSTDATA,NORNDPW,AUTHINIT) FAC(ssidMSTR=NOPROMPT,NOAUDIT,RES,WARNPW,NOTSOC) FAC(ssidMSTR=LCFTRANS,IJU,MSGLC,NOTRACE,NOEODINIT) FAC(ssidMSTR=NODORMPW,NONPWR) FAC(ssidMSTR=LOG(INIT,SMF,MSG,SEC9)) FAC(ssidMSTR=DOWN=GLOBAL,LOCKTIME=00,DEFACID=(*NONE*)) Repeat these steps for each queue manager ssid.

Fix: F-27316r1146208_fix

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 ACID. Each WebSphere MQ started task is defined to the STC record with a unique ACID. Each ssidMSTR STC ACID has a corresponding WebSphere MQ MASTFAC as defined in the z/OS. For example, a Started Task Table entry exists for each queue manager started task procedure xxxxMSTR and distributed queuing started task procedure xxxxCHIN. A corresponding userid for each started task exists. Queue manager and channel initiator started tasks will not be defined with the BYPASS attribute. WebSphere MQ queue manager facilities are defined using the control options as specified below: Define each queue manager xxxxMSTR to the TOP SECRET Facility Matrix Table using the following sample commands: FACILITY(USERxx=NAME=xxxxMSTR) FACILITY(xxxxMSTR=MODE=FAIL,PGM=CSQ,ID=xx) FACILITY(xxxxMSTR=ACTIVE,SHRPRF,ASUBM,NOABEND) FACILITY(xxxxMSTR=MULTUSER,XDEF,LUMSG,STMSG,SIGN(S)) FACILITY(xxxxMSTR=INSTDATA,NORNDPW,AUTHINIT) FACILITY(xxxxMSTR=NOPROMPT,NOAUDIT,RES,WARNPW) FACILITY(xxxxMSTR=NOTSOC,LCFTRANS,IJU,MSGLC,NOTRACE) FACILITY(xxxxMSTR=NOEODINIT,NODORMPW,NONPWR) (INIT,SMF,MSG,SEC9)) FACILITY(xxxxMSTR=DOWN=GLOBAL,LOCKTIME=00,DEFACID=(*NONE*))

b
WebSphere MQ all update and alter access to MQSeries/WebSphere MQ product and system data sets are not properly restricted.
AC-3 - Medium - CCI-000213 - V-225628 - SV-225628r1146386_rule
RMF Control
AC-3
Severity
Medium
CCI
CCI-000213
Version
ZWMQ0040
Vuln IDs
  • V-225628
  • V-3905
Rule IDs
  • SV-225628r1146386_rule
  • SV-3905
MVS data sets provide the configuration, operational, and executable properties of WebSphere MQ. Some data sets are responsible for the security implementation of WebSphere MQ. Failure to properly protect these data sets may lead to unauthorized access. This exposure could compromise the availability, integrity, and confidentiality of system services, applications, and customer data.
Checks: C-27329r1146386_chk

Refer to the following report produced by the ACP Data Collection: - SENSITVE.RPT(MQSRPT). Ensure ACP data sets rules for WebSphere MQ system data sets (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 data set rules restrict READ access to data sets referenced by the following DDnames restricted to WebSphere MQ STCs, WebSphere MQ administrators, and systems programming personnel. All access to these data sets is logged. DDname Procedure Description CSQINP1 ssidMSTR Input parameters CSQINP2 ssidMSTR Input parameters CSQXLIB ssidCHIN User exit library The ACP data set rules restrict WRITE and/or greater access to the above data sets to WebSphere MQ administrators and systems programming personnel. The ACP data set rules restrict WRITE and/or greater access to data sets 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 data sets is logged. DDname Procedure Description CSQPxxxx ssidMSTR Page data sets BSDSx ssidMSTR Bootstrap data sets CSQOUTx ssidMSTR SYSOUT data sets CSQSNAP ssidMSTR DUMP data set (See note) ssidMSTR Log data sets Note: To determine the log data set names, review the JESMSGLG file of the ssidMSTR active task(s). Find CSQJ001I messages to obtain data set names. The ACP data set rules restrict ALTER access to archive data sets to WebSphere MQ STCs, WebSphere MQ administrator, and systems programming personnel. All ALTER access to these data sets is logged. Note: To determine the archive data sets names, review the JESMSGLG file of the ssidMSTR active task(s). Find the CSQY122I message to obtain the ARCPRFX1 and ARCPRFX2 data set high-level qualifiers. Except for the specific data set requirements just mentioned, WRITE and/or greater access to all other WebSphere MQ system data sets is restricted to the WebSphere MQ administrator and systems programming personnel.

Fix: F-27317r1146211_fix

The systems programmer will have the ISSO ensure that all WRITE and/or greater access to WebSphere MQ product and system data sets are restricted to WebSphere MQ administrators, systems programmers, and WebSphere MQ started tasks. The installation requires that the following data sets be APF authorized. hlqual.SCSQAUTH hlqual.SCSQLINK hlqual.SCSQANLx hlqual.SCSQSNL hlqual.SCSQMVR1 hlqual.SCSQMVR2 READ access to data sets 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 data sets. WRITE and/or greater access to data set profiles protecting all page sets, logs, bootstrap data sets (BSDS), and data sets 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 data sets. ALL access to all archive data sets in the queue manager's procedure will be restricted to the queue manager userid, WebSphere MQ administrator, and systems programming personnel. Log all ALL access to these data sets.

b
WebSphere MQ security class(es) must not be defined improperly.
AC-3 - Medium - CCI-000213 - V-225629 - SV-225629r1146215_rule
RMF Control
AC-3
Severity
Medium
CCI
CCI-000213
Version
ZWMQ0049
Vuln IDs
  • V-225629
  • V-6959
Rule IDs
  • SV-225629r1146215_rule
  • SV-7535
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.
Checks: C-27330r1146213_chk

Refer to the following reports produced by the TSS Data Collection: - TSSCMDS.RPT(#RDT). - SENSITVE.RPT(WHOOMADM). - SENSITVE.RPT(WHOOMCMD). - SENSITVE.RPT(WHOOMCON). - SENSITVE.RPT(WHOOMNLI). - SENSITVE.RPT(WHOOMPRO.) - SENSITVE.RPT(WHOOMQUE). - SENSITVE.RPT(WHOOXADM). - SENSITVE.RPT(WHOOXNLI). - SENSITVE.RPT(WHOOXPRO). - SENSITVE.RPT(WHOOXQUE). - SENSITVE.RPT(WHOOXTOP). If the following WebSphere MQ Resource Class(es) is (are) defined in the Resource Definition Table (RDT), this is not a finding. MQADMIN MQCMDS MQCONN MQNLIST MQPROC MQQUEUE When SCYCASE is set to MIXED, and the following WebSphere MQ Resource Class(es) is (are) defined in the Resource Definition Table (RDT), this is not a finding. MXADMIN MXNLIST MXPROC MXQUEUE MXTOPIC Note: ssid is the queue manager name (a.k.a., subsystem identifier). Note: If both MQADMIN and MXADMIN resource classes are not defined to the RDT record, no security checking is performed.

Fix: F-27318r1146214_fix

Ensure that all WebSphere MQ resources are defined to TSS. The following should be defined to the RDT: MQADMIN MQCONN MQCMDS MQNLIST MQPROC MQQUEUE When SCYCASE is set to mixed, and the following WebSphere MQ resource classes should be defined to the TSS RDT. MXADMIN MXNLIST MXPROC MXQUEUE MXTOPIC Use the following commands to define (establish ownership of) resources for each WebSphere MQ subsystem to TSS: TSS ADD(deptname) MQADMIN(ssid.) TSS ADD(deptname) MQCMDS(ssid.) TSS ADD(deptname) MQCONN(ssid.) TSS ADD(deptname) MQNLIST(ssid.) TSS ADD(deptname) MQPROC(ssid.) TSS ADD(deptname) MQQUEUE(ssid.) When SCYCASE is set to mixed, CLASMAP Definitions must include the following entries: TSS ADD(deptname) MXADMIN(ssid.) TSS ADD(deptname) MXNLIST(ssid.) TSS ADD(deptname) MXPROC(ssid.) TSS ADD(deptname) MXQUEUE(ssid.) TSS ADD(deptname) MXTOPIC(ssid.) Note: ssid is the queue manager name (a.k.a., subsystem identifier). Another method to ensure protection is to assign the DEFPROT attribute to the resource class in the RDT record by using the following command: TSS REP(RDT) RESCLASS(MQADMIN) ATTR(DEFPROT) TSS REP(RDT) RESCLASS(MQCMDS) ATTR(DEFPROT) TSS REP(RDT) RESCLASS(MQCONN) ATTR(DEFPROT) TSS REP(RDT) RESCLASS(MQNLIST) ATTR(DEFPROT) TSS REP(RDT) RESCLASS(MQPROC) ATTR(DEFPROT) TSS REP(RDT) RESCLASS(MQQUEUE) ATTR(DEFPROT) When SCYCASE is set to mixed. TSS REP(RDT) RESCLASS(MXADMIN) ATTR(DEFPROT) TSS REP(RDT) RESCLASS(MXNLIST) ATTR(DEFPROT) TSS REP(RDT) RESCLASS(MXPROC) ATTR(DEFPROT) TSS REP(RDT) RESCLASS(MXQUEUE) ATTR(DEFPROT) TSS REP(RDT) RESCLASS(MXTOPIC) ATTR(DEFPROT)

c
WebSphere MQ switch profiles must be properly defined to the appropriate ADMIN class.
AC-3 - High - CCI-000213 - V-225630 - SV-225630r1146218_rule
RMF Control
AC-3
Severity
High
CCI
CCI-000213
Version
ZWMQ0051
Vuln IDs
  • V-225630
  • V-6960
Rule IDs
  • SV-225630r1146218_rule
  • SV-7539
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.
Checks: C-27331r1146216_chk

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 MQADMIN (or MXADMIN if SCYCASE is set to MIXED) resource class.

Fix: F-27319r1146217_fix

Switch profiles are special WebSphere MQ profiles that are used to turn on/off security checking for a type of resource. Due to the security exposure this creates, no profiles with the first two qualifiers of ssid.NO will be defined to the MQADMIN or MXADMIN class, with one exception. Due to the fact that (1) all sensitive WebSphere MQ commands are restricted to queue managers, channel initiators, and designated systems personnel, and (2) no command resource checking is performed on DISPLAY commands, at the discretion of the ISSO a ssid.NO.CMD.RESC.CHECKS switch profile may be defined to the MQADMIN or MXADMIN class. Identify if any switch profile permissions exist using the sample TSS command: TSS WHOHAS MQADMIN(ssid.NO.) Use the "TSS REVOKE(acid) MQADMIN(<SwitchProfileName>)" to remove the profile. An additional refresh to an active WebSphere MQ queue manager may be required. A sample is shown below using the value QMD1 as the queue manager name. From the Console: >QMD1 REFRESH SECURITY(*)

b
WebSphere MQ connection class resources must be protected properly.
AC-6 - Medium - CCI-002234 - V-225631 - SV-225631r1146221_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-002234
Version
ZWMQ0052
Vuln IDs
  • V-225631
  • V-6962
Rule IDs
  • SV-225631r1146221_rule
  • SV-7542
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.
Checks: C-27332r1146219_chk

Refer to the following report produced by the TSS Data Collection: - SENSITVE.RPT(WHOHMCON). Review the following connection resources for each queue manager defined to the connection resource class: Resource Authorized Users ssid.BATCH TSO and batch job ACIDs ssid.CICS CICS region ACIDs ssid.IMS IMS region ACIDs ssid.CHIN Channel initiator ACIDs Note: ssid is the queue manager name (a.k.a., subsystem identifier). For all connection resources defined to the MQCONN, if the following guidance is true, this is not a finding. Access authorization restricts access to the appropriate users as indicated above. All access FAILUREs are logged.

Fix: F-27320r1146220_fix

Review the following connection resources defined to the MQCONN or MXCONN resource class: Resource Authorized Users ssid.BATCH TSO and batch job ACIDs ssid.CICS CICS region ACIDs ssid.IMS IMS region ACIDs ssid.CHIN Channel initiator ACIDs Note: ssid is the queue manager name (a.k.a., subsystem identifier). For all connection resources defined to the MQCONN or MXCONN resource class, ensure the following items are in effect: Access authorization restricts access to the appropriate users as indicated above. All access FAILUREs are logged. The following is a sample of the commands required to allow a batch user (USER1) to connect to a queue manager (QM1): TSS ADD(USER1) FAC(QM1MSTR) TSS PER(USER1) MQCONN(QM1.BATCH) ACC(READ)

b
WebSphere MQ dead letter and alias dead letter queues are not properly defined.
CM-7 - Medium - CCI-001762 - V-225632 - SV-225632r1146224_rule
RMF Control
CM-7
Severity
Medium
CCI
CCI-001762
Version
ZWMQ0053
Vuln IDs
  • V-225632
  • V-6964
Rule IDs
  • SV-225632r1146224_rule
  • SV-7267
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.
Checks: C-27333r1146222_chk

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 ensure 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 ensure 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: F-27321r1146223_fix

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.

b
WebSphere MQ queue resource defined to the appropriate resource class must be protected in accordance with security requirements.
AC-3 - Medium - CCI-000213 - V-225633 - SV-225633r1146227_rule
RMF Control
AC-3
Severity
Medium
CCI
CCI-000213
Version
ZWMQ0054
Vuln IDs
  • V-225633
  • V-6965
Rule IDs
  • SV-225633r1146227_rule
  • SV-7545
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.
Checks: C-27334r1146225_chk

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 Data Set and Resource Data Collection: - SENSITVE.RPT(WHOHMQUE). - SENSITVE.RPT(WHOHXQUE). 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 the MQQUEUE (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 WRITE and/or greater 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.

Fix: F-27322r1146226_fix

For all queue resources defined to the MQQUEUE or MXQUEUE resource class, ensure the following items are in effect: Note: ssid is the queue manager name (a.k.a., subsystem identifier). 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. For system queues (i.e., ssid.SYSTEM.queuename), access authorization restricts 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 WebSphere MQ STCs, WebSphere MQ administrators, systems programming personnel, CICS regions running WebSphere MQ applications, auditors, and users that require access to review message queues. ssid.SYSTEM.COMMAND.INPUT ssid.SYSTEM.COMMAND.REPLY ssid.SYSTEM.CSQOREXX.* For the following system queues (i.e., ssid.SYSTEM.CSQUTIL.*) ensure that UPDATE access is restricted to WebSphere MQ STCs, WebSphere MQ administrators, systems programming personnel, CICS regions running WebSphere MQ applications, and auditors. For the real dead-letter queue (to determine queue name, refer to ZWMQ0053), 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), 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. Note: If an alias queue is not used in place of the dead-letter queue, the RACF rules for the dead-letter queue will be coded to restrict unauthorized users and systems from reading the messages on the file. The following is a sample of the commands required to allow a user (USER1) to get messages from or put messages to queues beginning with (PAY.) on subsystem (QM1): TSS PER(USER1) MQQUEUE(QM1.PAY.) ACC(UPDATE)

b
WebSphere MQ Process resources must be protected in accordance with security requirements.
AC-3 - Medium - CCI-000213 - V-225634 - SV-225634r1146230_rule
RMF Control
AC-3
Severity
Medium
CCI
CCI-000213
Version
ZWMQ0055
Vuln IDs
  • V-225634
  • V-6966
Rule IDs
  • SV-225634r1146230_rule
  • SV-7547
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.
Checks: C-27335r1146228_chk

Refer to the following report produced by the TSS Data Collection: - SENSITVE.RPT(WHOHMPRO). - SENSITVE.RPT(WHOHXPRO). For all process resources (i.e., ssid.processname) defined to 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. If this guidance is true, this is not a finding. Note: ssid is the queue manager name (a.k.a., subsystem identifier).

Fix: F-27323r1146229_fix

For all process resources (i.e., ssid.processname) defined to MQPROC or MXPROC resource class, 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). The following is a sample of the commands required to allow a user (USER1) to inquire on processes beginning with the letter V on queue manager (QM1): TSS ADD(USER1) FAC(QM1MSTR) TSS PER(USER1) MQPROC(QM1.V) ACC(READ) ACTION(AUDIT)

b
WebSphere MQ Namelist resources must be protected in accordance with security requirements.
AC-3 - Medium - CCI-000213 - V-225635 - SV-225635r1146233_rule
RMF Control
AC-3
Severity
Medium
CCI
CCI-000213
Version
ZWMQ0056
Vuln IDs
  • V-225635
  • V-6967
Rule IDs
  • SV-225635r1146233_rule
  • SV-7549
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.
Checks: C-27336r1146231_chk

Refer to the following reports produced by the TSS Data Collection: - SENSITVE.RPT(WHOHMNLI). - SENSITVE.RPT(WHOHXNLI). For all namelist resources (i.e., ssid.namelist) defined to 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. If this guidance is true, this is not a finding. Note: ssid is the queue manager name (a.k.a., subsystem identifier).

Fix: F-27324r1146232_fix

For all namelist resources (i.e., ssid.namelist) defined to MQNLIST or MXNLIST resource class, 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). The following is a sample of the commands required to allow a user (USER1) to inquire on namelist TST1 on queue manager (QM1): TSS ADD(USER1) FAC(QM1MSTR) TSS PER(USER1) MQNLIST(QM1.TST1.) ACC(READ) ACTION(AUDIT)

b
WebSphere MQ alternate user resources defined to appropriate ADMIN resource class must be protected in accordance with security requirements.
AC-3 - Medium - CCI-000213 - V-225636 - SV-225636r1146236_rule
RMF Control
AC-3
Severity
Medium
CCI
CCI-000213
Version
ZWMQ0057
Vuln IDs
  • V-225636
  • V-6969
Rule IDs
  • SV-225636r1146236_rule
  • SV-7551
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.
Checks: C-27337r1146234_chk

Refer to the following reports produced by the TSS Data Collection: - SENSITVE.RPT(WHOHMADM). - SENSITVE.RPT(WHOHXADM). For all alternate user resources (i.e., ssid.ALTERNATE.USER.alternatelogonid) defined to MQADMIN resource class (or MXADMIN resource class, 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. If this guidance is true, this is not a finding. Note: ssid is the queue manager name (a.k.a., subsystem identifier).

Fix: F-27325r1146235_fix

For all alternate user resources (i.e., ssid.ALTERNATE.USER.alternateuserid) defined to MQADMIN or MXADMIN resource class, 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). The following is a sample of the commands required to allow payroll server (PAYSRV1) to specify alternate userids starting with the characters PS on queue manager (QM1): TSS ADD(USER1) FAC(QM1MSTR) TSS PER(USER1) MQADMIN(QM1.ALTERNATE.USER.PS) ACC(UPDATE) ACTION(AUDIT)

b
WebSphere MQ context resources defined to the appropriate ADMIN resource class must be protected in accordance with security requirements.
AC-3 - Medium - CCI-000213 - V-225637 - SV-225637r1146239_rule
RMF Control
AC-3
Severity
Medium
CCI
CCI-000213
Version
ZWMQ0058
Vuln IDs
  • V-225637
  • V-6971
Rule IDs
  • SV-225637r1146239_rule
  • SV-7553
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.
Checks: C-27338r1146237_chk

Refer to the following reports produced by the TSS Data Collection: - SENSITVE.RPT(WHOHMADM). - SENSITVE.RPT(WHOHXADM). For all context resources (i.e., ssid.CONTEXT) defined to the MQADMIN resource class (or MXADMIN resource class, 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. If this guidance is true, this is not a finding. Note: ssid is the queue manager name (a.k.a., subsystem identifier).

Fix: F-27326r1146238_fix

For all context resources (i.e., ssid.CONTEXT) defined to the MQADMIN or MXADMIN resource class, 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). The following is a sample of the commands required to allow a systems programming group (SYS1) to offload and reload messages for queue manager (QM1): TSS ADD(SYS1) FAC(QM1MSTR) TSS PER(SYS1) MQADMIN(QM1.CONTEXT) ACC(UPDATE) ACTION(AUDIT)

b
WebSphere MQ command resources defined to MQCMDS resource class are not protected in accordance with security requirements.
AC-3 - Medium - CCI-000213 - V-225638 - SV-225638r1146242_rule
RMF Control
AC-3
Severity
Medium
CCI
CCI-000213
Version
ZWMQ0059
Vuln IDs
  • V-225638
  • V-6973
Rule IDs
  • SV-225638r1146242_rule
  • SV-7555
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.
Checks: C-27339r1146240_chk

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.

Fix: F-27327r1146241_fix

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)

b
WebSphere MQ RESLEVEL resources in the appropriate ADMIN resource class must be protected in accordance with security requirements.
AC-3 - Medium - CCI-000213 - V-225639 - SV-225639r1146245_rule
RMF Control
AC-3
Severity
Medium
CCI
CCI-000213
Version
ZWMQ0060
Vuln IDs
  • V-225639
  • V-6975
Rule IDs
  • SV-225639r1146245_rule
  • SV-7557
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.
Checks: C-27340r1146243_chk

Refer to the following reports produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(WHOHMADM). - SENSITVE.RPT(WHOHXADM). Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZWMQ0060). Access authorization to these RESLEVEL resources restricts all access. No users are permitted access to ssid.RESLEVEL resources in the MQADMIN resource class (or MXADMIN resource class, if SCYCASE is set to MIXED). If this guidance is true, this is not a finding. Note: ssid is the queue manager name (a.k.a., subsystem identifier).

Fix: F-27328r1146244_fix

RESLEVEL security profiles control the number of userids checked for API resource security. RESLEVEL security will not be implemented due to the following exposures and limitations: RESLEVEL is a powerful option that can cause the bypassing of all security checks. Security audit records are not created when the RESLEVEL profile is utilized. If the WARNING option is specified on a RESLEVEL profile, no warning messages are produced. To protect against any profile in the MQADMIN or MXADMIN class, such as ssid.**, resolving to a RESLEVEL profile, an ssid.RESLEVEL permission will be created for each queue manager with an access of none. The following sample command prevents access to ssid.RESLEVEL: TSS PER(ALL) MQADMIN(ssid.RESLEVEL) ACCESS(NONE)