Ensure that only authorized users can issue SPI commands

점검 방법

감사 방식: 수동 검토

이 권장 사항은 자동으로 점검할 수 없습니다. --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 XCMD column. They should all be set to the suffix of the transaction class name. The classes are prefixed by C and V. In the following ... (full steps: CIS section 1.4.1)

조치 방법

조치 방식: 가이드 또는 인프라 패치

Categorize the SPI commands on the system according to who should have access to them, and what level of access should be given, for example READ or UPDATE. Define profiles for these commands either generically or in groups in the classes CCICSCMD or VCICSCMD (or the class names used if the default classes aren't used). Give the required level of access to the appropriate groups for these profiles. An example of this is as follows: RDEFINE VCICSCMD memname OWNER(admin) AUDIT(ALL(READ)) UACC(NONE) RALTER VCICSCMD memname ADDMEM(cmd1 cmd2 cmd3) PERMIT memname CLASS(VCICSCMD) ID(group) ACCESS(READ) SETROPTS RACLIST(CCICSCMD) REFRESH Change any transactions definitions which specify CMDSEC(NO) to CMDSEC(YES) Set XCMD=YES or name Restart CICS