Cyber Trackr - Free Compliance Library
Cyber Trackr
The Free Compliance Library

z/OS CA Common Services for RACF STIG

  • Version/Release: V6R1
  • Published: 2012-01-10
  • Expand All:
  • Severity:
  • Sort:
Compare

Select any two versions of this STIG to compare the individual requirements

View

Select any old version/release of this STIG to view the previous requirements

b
CA Common Services installation data sets will be properly protected.
Medium - V-16932 - SV-40834r1_rule
RMF Control
Severity
Medium
CCI
Version
ZCCSR000
Vuln IDs
  • V-16932
Rule IDs
  • SV-40834r1_rule
CA Common Services installation data sets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to these data sets could result in violating the integrity of the base product which could result in compromising the operating system or sensitive data.Information Assurance OfficerDCSL-1, ECAR-1, ECAR-2, ECCD-1, ECCD-2
Checks: C-4862r3_chk

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 RACF data set rules for the data sets restricts READ access to all authorized users. ___ The RACF data set rules for the data sets restricts WRITE and/or greater access to systems programming personnel. ___ The RACF data set rules for the data sets specify that all (i.e., failures and successes) WRITE and/or greater access is logged. ___ The RACF data set rules for the data sets specify UACC(NONE) and NOWARNING.

Fix: F-386r3_fix

The IAO will ensure that WRITE and/or greater access to CA Common Services installation data sets is limited to System 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. He will identify if any additional groups have WRITE and/or greater access for specific data sets, and once documented he will work with the IAO to see that they are properly restricted to the ACP (Access Control Program) 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: AD 'sys2.ccs.**' UACC(NONE) OWNER(SYS2) AUDIT(SUCCESS(UPDATE) FAILURES(READ)) PE 'sys2.ccs.**' ID(syspaudt) ACC(A) PE 'sys2.ccs.**' ID(authorized users/*) ACC(R)

b
CA Common Services Started Task name will be properly identified and/or defined to the system ACP.
Medium - V-17452 - SV-40857r1_rule
RMF Control
Severity
Medium
CCI
Version
ZCCSR030
Vuln IDs
  • V-17452
Rule IDs
  • SV-40857r1_rule
CA Common Services requires a started task that will be restricted to certain resources, datasets and other system functions. By 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.Information Assurance OfficerECCD-1, ECCD-2
Checks: C-4865r3_chk

Refer to the following report produced by the RACF Data Collection: - RACFCMDS.RPT(LISTUSER) Verify that the userid(s) for the CA Common Services started task(s) is (are) properly defined. If the following attributes are defined, this is not a finding. PROTECTED

Fix: F-5538r3_fix

The IAO working with the systems programmer will ensure the CA Common Services Started Task(s) is properly identified and/or defined to the System ACP. If the product requires a Started Task, verify that it is properly defined to the System 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): au CAS9 name('STC, CAS9') owner(stc) dfltgrp(stc) nopass – data('CCS stc')

b
CA Common Services Started task will be properly defined to the STARTED resource class for RACF.
Medium - V-17454 - SV-40859r1_rule
RMF Control
Severity
Medium
CCI
Version
ZCCSR032
Vuln IDs
  • V-17454
Rule IDs
  • SV-40859r1_rule
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.Information Assurance OfficerECCD-1, ECCD-2
Checks: C-4867r3_chk

Refer to the following report produced by the RACF Data Collection: - DSMON.RPT(RACSPT) Automated Analysis Refer to the following report produced by the RACF Data Collection: - PDI(ZCCS0032) If the CA Common Services started task(s) is (are) defined to the STARTED resource class profile and/or ICHRIN03 table entry, this is not a finding.

Fix: F-382r3_fix

The IAO working with the systems programmer will ensure the CA Common Services Started Task(s) is properly identified and/or defined to the System ACP. A unique userid must be assigned for the CA Common Services started task(s) thru a corresponding STARTED class entry. The following commands are provided as a sample for defining Started Task(s): rdef started CAS9.** uacc(none) owner(admin) audit(all(read)) – stdata(user(CAS9) group(stc)) setr racl(started) ref