z/OS CA Common Services for ACF2 STIG

Version/Release: V6R2
Published: 2015-01-15
Released: 2015-01-20
Expand All:
Severity:
Sort:
Control

Severity

Vuln

Title

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

CA Common Services installation data sets will be properly protected.

AC-3 - Medium - CCI-000213 - V-16932 - SV-40833r1_rule

RMF Control

AC-3

Severity

Medium

CCI

CCI-000213

Version

ZCCSA000

Vuln IDs

V-16932

Rule IDs

SV-40833r1_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 OfficerSystems ProgrammerDCSL-1, ECAR-1, ECAR-2, ECCD-1, ECCD-2

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

Fix: F-180r1_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: $KEY(S2C) $PREFIX(SYS2) CCS.- UID(syspaudt) R(A) W(L) A(L) E(A) CCS.- UID(<tstcaudt>) R(A) W(L) A(L) E(A) CCS.- UID(authorized users/*) R(A) E(A) SET RULE COMPILE 'ACF2.MVA.DSNRULES(S2C)' STORE

CA Common Services Started Task name will be properly identified and/or defined to the system ACP.

IA-2 - Medium - CCI-000764 - V-17452 - SV-40856r1_rule

RMF Control

IA-2

Severity

Medium

CCI

CCI-000764

Version

ZCCSA030

Vuln IDs

V-17452

Rule IDs

SV-40856r1_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 OfficerSystems ProgrammerECCD-1, ECCD-2

Checks: C-4864r1_chk

Refer to the following report produced by the ACF2 Data Collection: - ACF2CMDS.RPT(ATTSTC) Verify that the logonid(s) for the CA Common Services started task(s) is (are) properly defined. If the following attributes are defined, this is not a finding. STC

Fix: F-256r1_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): SET LID insert CAS9 stc name('STC, CAS9')