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 ACF2 Security Technical Implementation Guide

V-224331

CAT II (Medium)

NetView Started Task name must be properly identified/defined to the system ACP.

Rule ID

SV-224331r1144120_rule

STIG

z/OS NetView for ACF2 Security Technical Implementation Guide

Version

V7R2

CCIs

CCI-000764

Discussion

NetView requires a started task(s) that will be restricted to certain resources, datasets, 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 ACF2 Data Collection:

- ACF2CMDS.RPT(ATTSTC).

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

STC
MUSASS
NO-SMC

Fix Text

The NetView systems programmer and the ISSO will ensure that a product's Started Task(s) is properly identified/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 the Started Task is identified and any additional attributes that must be specified.

Example:

SET LID
CHANGE NETVIEW STC MUSASS NO-SMC