STIGQter STIGQter: STIG Summary: z/OS CA Common Services for RACF STIG Version: 6 Release: 2 Benchmark Date: 20 Jan 2015:

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

DISA Rule

SV-40857r1_rule

Vulnerability Number

V-17452

Group Title

ZB000030

Rule Version

ZCCSR030

Severity

CAT II

CCI(s)

Weight

10

Fix Recommendation

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')

Check Contents

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

Vulnerability Number

V-17452

Documentable

False

Rule Version

ZCCSR030

Severity Override Guidance

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

Check Content Reference

M

Responsibility

Systems Programmer

Target Key

2017

Comments