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 NetView for RACF Security Technical Implementation Guide

V-224521

CAT II (Medium)

NetView Started Task name(s) is not properly identified/defined to the system ACP.

Rule ID

SV-224521r1144958_rule

STIG

z/OS NetView for RACF Security Technical Implementation Guide

Version

V7R2

CCIs

CCI-000764

Discussion

NetView requires a started task(s) that will be restricted to certain resources, data sets, and other system functions. Defining the started task as a userid to the system ACP allows the ACP to control the access and authorized users that require these capabilities. Failure to properly control these capabilities could compromise the operating system environment, ACP, and customer data.

Check Content

Refer to the following report produced by the RACF Data Collection:

- RACFCMDS.RPT(LISTUSER).

Verify that the userid(s) for the NetView started task(s) is (are) properly defined. If the following attributes are defined, this is not a finding.

PROTECTED

Fix Text

The NetView systems programmer and the ISSO will ensure that the product's Started Task(s) is properly Identified/defined to the System ACP. 

Most installation manuals will indicate how the Started Task is identified and any additional attributes that must be specified.

A sample is provided here:

au cnmpssi name('stc, netview') nopass dfltgrp(stc) -
owner(stc) data('netview subsystem interface')
au cnmproc name('stc, netview') nopass dfltgrp(stc) -
owner(stc) data('netview')