External RACF Classes are not active for CICS transaction checking.

Implement CICS transaction security by utilizing two distinct and unique RACF resource classes (i.e., member and grouping) within each CICS region. If several CICS regions are grouped in an MRO environment, it is permissible for those grouped regions to share a common pair of resource classes. Member classes contain a RACF discrete profile for each transaction. Grouping classes contain groups of transactions requiring equal protection under RACF. Ideally, member classes contain no profiles, and all transactions are defined by groups in a grouping class.

If CICS Classes are not active, this could result in the compromise of the confidentiality, integrity, and availability of the CICS region, applications, and customer data.

Refer to the following report produced by the RACF Data Collection:

- RACFCMDS.RPT(SETROPTS).

Refer to the CICS Systems Programmer Worksheets filled out from previous vulnerability ZCIC0010.

If each CICS transaction resource class pair are active, this is a finding.

Review each CICS SIT to ensure each region has a unique resource class or resource prefix specified.

The resources classes are activated in RACF using the following command: SETR CLASSACT(<classname>)