UCF STIG Viewer Logo
Changes are coming to https://stigviewer.com. Take our survey to help us understand your usage and how we can better serve you in the future.
Take Survey

ACF2 LOGONIDs assigned for started tasks must have the STC attribute specified in the associated LOGONID record.


Overview

Finding ID Version Rule ID IA Controls Severity
V-223485 ACF2-ES-000670 SV-223485r533198_rule Medium
Description
Activity under unusual conditions can indicate hostile activity. For example, what is normal activity during business hours can indicate hostile activity if it occurs during off hours. Depending on mission needs and conditions, account usage restrictions based on conditions and circumstances may be critical to limit access to resources and data to comply with operational or mission access control requirements. Thus, the operating system must be configured to enforce the specific conditions or circumstances under which organization-defined accounts can be used (e.g., by restricting usage to certain days of the week, time of day, or specific durations of time).
STIG Date
IBM z/OS ACF2 Security Technical Implementation Guide 2020-10-02

Details

Check Text ( C-25158r504564_chk )
From the ACF command screen enter:
SET LID
SET VERBOSE
LIST IF(STC)

If all logonids identified as started tasks have the STC attribute specified, this is not a finding.
Fix Text (F-25146r504565_fix)
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