Data set masking characters allowing access to all data sets are not properly resticted in the security database. - z/OS TSS STIG

Associated with IA controls: DCCS-1, ECCD-2, DCCS-2, ECAR-3, ECAR-2, ECCD-1, ECAR-1

SV-26592r1_rule Data set masking characters allowing access to all data sets are not properly resticted in the security database.

Vulnerability discussion

TSS provides masking as an additional method for reducing the number of entries that must be made to secure the installation data sets. Shared patterns can be used as the operands of data set parameters. If this masking character (*, *., and/or **) are not restricted, there is the possibility of exposure when granting access to the data set mask allowing access to all data sets. Unauthorized access could result in the compromise of the operating system environment, ACP, products, and customer data.

Check content

Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(GLOBRPT) Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(TSS1010) ___ The ACP data set rules for mask character (*, *., and/or **) allow inappropriate access. ___ The ACP data set rules for mask character (*, *., and/or **) do not restrict all access to batch jobs that perform maintenance to all data sets. ___ The ACP data set rules for mask character (*, *., and/or **) do not specify that all (i.e., failures and successes) access will be logged. The logging requirement is not required for Trusted Started Tasks.

Fix text

The IAO will review access authorization to the data set mask (*, *., and/or **). Evaluate the impact of correcting the deficiency. Develop a plan of action and implement the changes required to restrict access to the data set mask permissions. The IAO will ensure that all access to the data set mask permissions are resticted as follows: Auditors may require READ access to all data sets. STC and batch jobs that require read, update, and/or alter access to perform maintenance to all data sets. All accesses will be logged, the exception is the the logging requirement is not required for Trusted Started Tasks. Example: TSS ADDTO(msca) DATASET(*.) TSS PERMIT(audtaudt) DATASET(*.) ACCESS(READ) ACTION(AUDIT) TSS PERMIT(tstcaudt) DATASET(*.) ACCESS(ALL) TSS PERMIT(usracid) DATASET(*.) ACCESS(UPDATE) ACTION(AUDIT)

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.