STIGQter: STIG Summary: IBM z/OS RACF Security Technical Implementation Guide Version: 8 Release: 3 Benchmark Date: 23 Apr 2021:

IBM RACF started tasks defined with the trusted attribute must be justified.

DISA Rule

SV-223661r604139_rule

Vulnerability Number

V-223661

Group Title

SRG-OS-000080-GPOS-00048

Rule Version

RACF-ES-000130

Severity

CAT II

CCI(s)

• CCI-000213 - The information system enforces approved authorizations for logical access to information and system resources in accordance with applicable access control policies.

Weight

10

Fix Recommendation

Review assignment of the TRUSTED attribute in ICHRIN03 and/or the STARTED resource class. Ensure only those trusted STCs that are listed in the IBM z/OS MVS Initialization and Tuning Reference have been granted this authority. Evaluate the impact of correcting the deficiency. Develop a plan of action and implement the changes. While the actual list may vary based on local site requirements and software configuration, the started tasks listed in the IBM z/OS MVS Initialization and Tuning Reference is an approved list of started tasks that may be considered trusted started procedures. Guidelines for reference:

Assign the TRUSTED attribute when one of the following conditions applies:
-The started procedure or address space creates or accesses a wide variety of unpredictably named data sets within your installation.
-Insufficient authority to an accessed resource might risk an unsuccessful IPL or other system problem.
-Avoid assigning TRUSTED to a z/OS started procedure or address space unless it is listed here or you are instructed to do so by the product documentation.

Additionally external security managers are candidates for trusted attribute. Any other started tasks not listed or not covered by the guidelines are a finding unless approval by the Authorizing Official.

The TRUSTED attribute can be removed from a STARTED class profile using the command:
RALT STARTED <profilename> STDATA(TRUSTED(NO))

If the STARTED class is RACLISTed then a refresh command is necessary:
SETR RACL(STARTED) REFRESH

If any Started Tasks exist with the PRIVILEGED attribute then take the following action to remove this attribute:
RALT STARTED <profilename> STDATA(PRIVILEGED(NO))

If the STARTED class is RACLISTed then a refresh command is necessary:
SETR RACL(STARTED) REFRESH

Check Contents

Refer to the list of z/OS started tasks and address spaces in the IBM z/OS MVS Initialization and Tuning Reference.

If the only approved Started Tasks that have the TRUSTED flag enabled are in this list, this is not a finding.

If there are no Started Tasks that have been granted the PRIVILEGED attribute, this is not a finding.

Guidelines for reference:

Assign the TRUSTED attribute when one of the following conditions applies:
- The started procedure or address space creates or accesses a wide variety of unpredictably named data sets within your installation.
- Insufficient authority to an accessed resource might risk an unsuccessful IPL or other system problem.
Avoid assigning TRUSTED to a z/OS started procedure or address space unless it is listed here or you are instructed to do so by the product documentation.

Additionally external security managers are candidates for trusted attribute.
Any other started tasks not listed or not covered by the guidelines are a finding unless approval by the Authorizing Official.

Vulnerability Number

V-223661

Documentable

False

Rule Version

RACF-ES-000130

Severity Override Guidance

Refer to the list of z/OS started tasks and address spaces in the IBM z/OS MVS Initialization and Tuning Reference.

If the only approved Started Tasks that have the TRUSTED flag enabled are in this list, this is not a finding.

If there are no Started Tasks that have been granted the PRIVILEGED attribute, this is not a finding.

Guidelines for reference:

Assign the TRUSTED attribute when one of the following conditions applies:
- The started procedure or address space creates or accesses a wide variety of unpredictably named data sets within your installation.
- Insufficient authority to an accessed resource might risk an unsuccessful IPL or other system problem.
Avoid assigning TRUSTED to a z/OS started procedure or address space unless it is listed here or you are instructed to do so by the product documentation.

Additionally external security managers are candidates for trusted attribute.
Any other started tasks not listed or not covered by the guidelines are a finding unless approval by the Authorizing Official.

Check Content Reference

M

Target Key

4101

Comments