STIGhubSTIGhub
STIGsRMF ControlsCompare
STIGhub— A free STIG search and compliance tool·STIGs updated 3 days ago
Powered by Pylon·Privacy·Terms·© 2026 Beacon Cloud Solutions, Inc.
← Back to z/OS Compuware Abend-AID for RACF Security Technical Implementation Guide

V-224477

CAT II (Medium)

Compuware Abend-AID Started task will be properly defined to the STARTED resource class for RACF.

Rule ID

SV-224477r1144664_rule

STIG

z/OS Compuware Abend-AID for RACF Security Technical Implementation Guide

Version

V7R2

CCIs

CCI-000764

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.

Check Content

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(ZAID0032).

If the Compuware Abend-AID started task(s) is (are) defined to the STARTED resource class profile and/or ICHRIN03 table entry, this is not a finding.

Fix Text

The ISSO working with the systems programmer will ensure the Compuware Abend-AID Started Task(s) is properly identified and/or defined to the System ACP. 

A unique userid must be assigned for the Compuware Abend-AID started task(s) thru a corresponding STARTED class entry.

The following commands are provided as a sample for defining Started Task(s):

rdef started AAVIEWER.** uacc(none) owner(admin) audit(all(read)) -
	stdata(user(AAVIEWER) group(stc))
rdef started BDCAS.** uacc(none) owner(admin) audit(all(read)) -
	stdata(user(BDCAS) group(stc))
rdef started TDCAS.** uacc(none) owner(admin) audit(all(read)) -
	stdata(user(TDCAS) group(stc))
setr racl(started) ref