Ensure that a user requires authorization to start work under a different userid

Cómo se verifica

Método de auditoría: Revisión manual

Esta recomendación no se puede verificar automáticamente. Un escaneo la lista con estas instrucciones cuando se pasa --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 XUSER column. They should all be set to YES. 4. List the SURROGAT class by using the RACF command RLIST SURROGAT. 5. Look for the CICS ... (full steps: CIS section 1.4.2)

Cómo se corrige

Método de corrección: Guía o parche de infraestructura

Define surrogate profiles as follows: RDEFINE SURROGAT *.DFHSTART OWNER(admin) UACC(NONE) RDEFINE SURROGAT *.DFHINSTL OWNER(admin) UACC(NONE) RDEFINE SURROGAT *.DFHEXCI OWNER(admin) UACC(NONE) RDEFINE SURROGAT *.DFHQUERY OWNER(admin) UACC(NONE) SETROPTS RACLIST(SURROGAT) REFRESH Investigate if surrogate security is needed anywhere if so you will need to define specific profiles similar to the following. Give READ access to the appropriate groups for these profiles. The following is an example of this: RDEFINE SURROGAT executionUserid.DFHSTART OWNER(admin) UACC(NONE) PERMIT executionUserid.DFHSTART CLASS(SURROGAT) ID(group) ACCESS(READ) SETROPTS RACLIST(SURROGAT) REFRESH Set XUSER=YES Restart CICS