Ensure that only authorized users can run transactions

How it is checked

Audit method: Manual review

This recommendation cannot be checked automatically. A scan lists it with these instructions when you pass --include-manual.

Issue the z/OSMF Compliance data collection REST API to drive collection of compliance evidence in the SMF 1154 record. https://{host}:{port}/zosmf/compliance/rest/v1/facts 1. Wait for the data to be collected; this may take up to a minute in some regions. 2. Customize and run the DFH$54P sample JCL to create a spreadsheet containing data for all of the CICS TS regions. 3. Open the spreadsheet and review the settings of the XTRAN column. 4. They should all be set to the suffix of the transaction class name. The classes are prefixed by G and T. In the ... (full steps: CIS section 1.2.1)

How it is fixed

Fix method: Guidance or infrastructure patch

Categorize the transactions on the system according to who should have access to them. Define profiles for these transactions either generically or in groups in the classes TCICSTRN or GCICSTRN (or the class names used if the default classes aren't used). Give READ access to the appropriate groups for these profiles. An example of this is as follows RDEFINE GCICSTRN memname OWNER(admin) AUDIT(ALL(READ)) UACC(NONE) RALTER GCICSTRN memname ADDMEM(tran1 tran2 tran3) PERMIT memname CLASS(GICICSTRN) ID(group) ACCESS(READ) SETROPTS RACLIST(TCICSTRN) REFRESH 1. Set XTRAN=YES or name. 2. Restart CICS