There are LOGONIDs assigned for started tasks that do not have the STC attribute specified in the associated LOGONID record.

Associated with IA controls: DCCS-1, DCCS-2

SV-161r1_rule There are LOGONIDs assigned for started tasks that do not have the STC attribute specified in the associated LOGONID record.

Vulnerability discussion

If a LOGONID for a started task does not have the STC attribute specified, this could result in system or application unavailability.

Check content

a) Refer to the following report produced by the ACF2 Data Collection: - ACF2CMDS.RPT(ATTSTC) b) Identify all logonids assigned to started tasks. c) Review every logonid record assigned to started tasks to ensure each one has the STC attribute specified. d) If all logonids identified as started tasks have the STC attribute specified, there is NO FINDING. e) If any logonid identified as a started task does not have the STC attribute specified, this is a FINDING.

Fix text

The IAO will ensure that all logonid records assigned to started tasks have the STC attribute specified. All started tasks will be assigned an individual logonid. The logonid for a Started Task Control (STC) will be granted the minimum privileges necessary for the STC to function. In addition to the default LID field settings, all STC logonids will have the following field setting: STC Example: SET LID INSERT logonid STC

Pro Tips

Lavender hyperlinks in small type off to the right (of CSS class id, if you view the page source) point to globally unique URIs for each document and item. Copy the link location and paste anywhere you need to talk unambiguously about these things.

You can obtain data about documents and items in other formats. Simply provide an HTTP header Accept: text/turtle or Accept: application/rdf+xml.