Rule ID
SV-224737r1146384_rule
Version
V7R2
CCIs
TSS CICS facilities define the security controls in effect for CICS regions. Failure to code the appropriate values could result in degraded security. This exposure may result in unauthorized access impacting the confidentiality, integrity, and availability of the CICS region, applications, and customer data.
Refer to the following report produced by the z/OS Data Collection: - EXAM.RPT(CICSPROC). Refer to the following reports produced by the TSS Data Collection: - 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. Refer to the CICS Systems Programmer Worksheets filled out from previous vulnerability ZCIC0010. Ensure the following items are in effect for each CICS region's facility. If the following guidance is true, this is not a finding. The TSS CICS facility is defined with the control option values specified in the TOP SECRET INITIALIZATION PARAMETERS FOR CICS REGION Table in the z/OS STIG Addendum. Note: An exception to the STIG is MRO CICS regions in production will use SIGN(M) appropriately. XUSER=YES must be coded in each CICS facility. CICS transactions defined in the BYPASS list are not sensitive transactions.
Review the TSS control option values for all CICS facilities. Ensure the following items are in effect for each CICS region's facility: The TSS CICS facility is defined with the control option values specified in table - "TOP SECRET INITIALIZATION PARAMETERS FOR CICS REGION", in the zOS STIG Addendum. Note: An exception is MRO CICS regions in production will use SIGN(M) appropriately. XUSER=YES must be coded in each CICS facility. CICS transactions defined in the BYPASS list are not sensitive transactions.