What changed in z/OS CA Common Services for TSS STIG V7R2V7R2 changes

Check text

Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(CCSRPT). Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZCCS0000). Verify that the accesses to the CA Common Services installation data sets are properly restricted. If the following guidance is true, this is not a finding. ___ The TSS data set rules for the data sets restrictsrestrict READ access to all authorized users. ___ The TSS data set rules for the data sets restrictsrestrict WRITE and/or greater access to systems programming personnel. ___ The TSS data set rules for the data sets specify that all (i.e., failures and successes) WRITE and/or greater access is logged.

Fix text

The ISSO will ensure that WRITE and/or greater access to CA Common Services installation data sets is limited to systems programmers only, and all WRITE and/or greater access is logged. READ access can be given to all authorized users. The installing systems programmer will identify and document the product data sets and categorize them according to who will have WRITE and/or greater access and if required that all WRITE and/or greater access is logged. The installing systems programmer will identify if any additional groups have WRITE and/or greater access for specific data sets and once documented will work with the ISSO to see that they are properly restricted to the ACP (Access Control Program (ACP) active on the system. Data sets to be protected may begin with: SYS2.CCS. SYS2A.CCS. SYS3.CCS. The following commands are provided as a sample for implementing data set controls: TSS ADD(SYS2) DSN(SYS2) TSS PERMIT(syspaudt) DSN(SYS2.CCS) ACCESS(ALL) ACTION(AUDIT) TSS PERMIT(syspaudt) DSN(SYS2.CCS) ACCESS(READ) TSS PERMIT(authorized users/ALL) DSN(SYS2.CCS) ACCESS(READ)

V-224621 in V7R2

Check text

Refer to the following report produced by the TSS Data Collection: - TSSCMDS.RPT(@ACIDS). VerifyReview that the ACID(s) for the CA Common Services startedSTC/Batch taskACID(s) is (are) properly defined. If the following attributes are defined, this is not a finding. FACILITY(STC, BATCH) PASSWORD(xxxxxxxx,0) SOURCE(INTRDR) NOSUSPEND

Fix text

The IAOISSO working with the systems programmer will ensure the CA Common Services Started Task(s) is properly identified and/or defined to the Systemsystem ACP. If the product requires a Started Task, verify that it is properly defined to the Systemsystem ACP with the proper attributes. Most installation manuals will indicate how a Started Task is identified and any additional attributes that must be specified. The following commands are provided as a sample for defining Started Task(s): TSS CREATE(CAS9) TYPE(USER) - NAME('STC, CAS9') DEPT(xxxx) - FAC(STC,BATCH) PASS(xxxxxxxx,0) - SOURCE(INTRDR) - NOSUSPEND

Discussion

CA Common Services requires a started task that will be restricted to certain resources, datasetsdata sets, and other system functions. ByDefining defining the started task as a userid to the system ACP, It allows the ACP to control the access and authorized users that require these capabilities. Failure to properly control these capabilities, could compromise of the operating system environment, ACP, and customer data.

V-224622 in V7R2

Check text

Refer to the following report produced by the TSS Data Collection: - TSSCMDS.RPT(#STC). Automated Analysis Refer to the following report produced by the TSS Data Collection: - PDI(ZCCS0032). If the CA Common Services started task(s) is (are) defined in the TSS STC record, this is not a finding.

Fix text

The IAOISSO working with the systems programmer will ensure the CA Common Services Started Task(s) is properly identified and/or defined to the Systemsystem ACP. A unique ACID must be assigned for the CA Common Services started task(s) thruthrough a corresponding STC table entry. The following commands are provided as a sample for defining Started Task(s): TSS ADD(STC) PROCNAME(CAS9) ACID(CAS9)

Discussion

Access to product resources should be restricted to only those individuals responsible for the application connectivity and who have a requirement to access these resources. Improper control of product resources could potentially compromise the operating system, ACP, and customer data.

V-224623 in V7R2