Cyber Trackr - Free Compliance Library
Cyber Trackr
The Free Compliance Library

z/OS ROSCOE for TSS Security Technical Implementation Guide

  • Version/Release: V6R9
  • Published: 2024-09-24
  • Released: 2024-10-24
  • Expand All:
  • Severity:
  • Sort:
Compare

Select any two versions of this STIG to compare the individual requirements

View

Select any old version/release of this STIG to view the previous requirements

This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DOD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.
b
ROSCOE Install data sets are not properly protected.
AC-3 - Medium - CCI-000213 - V-225598 - SV-225598r958472_rule
RMF Control
AC-3
Severity
Medium
CCI
CCI-000213
Version
ZROST000
Vuln IDs
  • V-225598
  • V-16932
Rule IDs
  • SV-225598r958472_rule
  • SV-21902
ROSCOE Install data sets provide the capability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to their data sets could result in violating the integrity of the base product which could result in compromising the operating system or sensitive data.
Checks: C-27298r520853_chk

a) Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(ROSRPT) Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZROS0000) b) Verify that access to the ROSCOE Install data sets are properly restricted. ___ The TSS data set rules for the data sets does not restrict UPDATE and/or ALTER access to systems programming personnel. ___ The TSS data set rules for the data sets does not specify that all (i.e., failures and successes) UPDATE and/or ALTER access will be logged. c) If all of the above are untrue, there is NO FINDING. d) If any of the above is true, this is a FINDING.

Fix: F-27286r520854_fix

The IAO will ensure that update and allocate/create access to program product data sets is limited to System Programmers only, and all update and allocate/create access is logged. Security Personnel and Auditors should have read access. The installing Systems Programmer will identify and document the product data sets and categorize them according to who will have update and allocate/create access and if required that all update and allocate/create access is logged. He will identify if any additional groups have update access for specific data sets, and once documented he will work with the IAO to see that they are properly restricted to the ACP (Access Control Program ) active on the system. Data sets to be protected will be: SYS2.ROSCOE SYS2A.ROSCOE SYS3.ROSCOE SYS3A.ROSCOE The following commands are provided as a sample for implementing dataset controls: TSS PERMIT(syspaudt) DSN(SYS2.ROSCOE.) ACCESS(R) TSS PERMIT(syspaudt) DSN(SYS2.ROSCOE.) ACCESS(ALL) ACTION(AUDIT) TSS PERMIT(secaaudt) DSN(SYS2.ROSCOE.) ACCESS(R) TSS PERMIT(audtaudt) DSN(SYS2.ROSCOE.) ACCESS(R) TSS PERMIT(syspaudt) DSN(SYS2A.ROSCOE.) ACCESS(R) TSS PERMIT(syspaudt) DSN(SYS2A.ROSCOE.) ACCESS(ALL) ACTION(AUDIT) TSS PERMIT(secaaudt) DSN(SYS2A.ROSCOE.) ACCESS(R) TSS PERMIT(audtaudt) DSN(SYS2A.ROSCOE.) ACCESS(R) TSS PERMIT(syspaudt) DSN(SYS3.ROSCOE.) ACCESS(R) TSS PERMIT(syspaudt) DSN(SYS3.ROSCOE.) ACCESS(ALL) ACTION(AUDIT) TSS PERMIT(secaaudt) DSN(SYS3.ROSCOE.) ACCESS(R) TSS PERMIT(audtaudt) DSN(SYS3.ROSCOE.) ACCESS(R) TSS PERMIT(syspaudt) DSN(SYS3A.ROSCOE.) ACCESS(R) TSS PERMIT(syspaudt) DSN(SYS3A.ROSCOE.) ACCESS(ALL) ACTION(AUDIT) TSS PERMIT(secaaudt) DSN(SYS3A.ROSCOE.) ACCESS(R) TSS PERMIT(audtaudt) DSN(SYS3A.ROSCOE.) ACCESS(R)

b
ROSCOE STC data sets are not properly protected.
CM-5 - Medium - CCI-001499 - V-225599 - SV-225599r958616_rule
RMF Control
CM-5
Severity
Medium
CCI
CCI-001499
Version
ZROST001
Vuln IDs
  • V-225599
  • V-17067
Rule IDs
  • SV-225599r958616_rule
  • SV-23707
ROSCOE STC data sets provide the capability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to their data sets could result in violating the integrity of the base product which could result in compromising the operating system or sensitive data.
Checks: C-27299r520856_chk

a) Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(ROSSTC) Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZROS0001) b) Verify that access to the ROSCOE STC data sets are properly restricted. The data sets in this group are the data sets identified in the ROSACTxx (if used), ROSLIBxx, and SYSAWSx DD statements of the STC or batch JCL. ___ The TSS data set rules for the data sets does not restrict UPDATE and/or ALTER access to systems programming personnel. ___ The TSS data set rules for the data sets does not restrict UPDATE and/or ALTER access to the product STC(s) and/or batch job(s). c) If all of the above are untrue, there is NO FINDING. d) If any of the above is true, this is a FINDING.

Fix: F-27287r520857_fix

The IAO will ensure that update and allocate/create access to the ROSCOE started task or batch job data sets is limited to system programmers and the started task only and all update and allocate/create access is logged. The IAO will ensure that all other accesses to the ROSCOE started task or batch job data sets are properly restricted and all required accesses are properly logged. Data sets to be protected will be SYS3.ROSCOE.SYS** SYS3.ROSCOE.ROSLIB** The following commands are provided as a sample for implementing dataset controls: TSS ADD(SYS3) DSN(SYS3) TSS PER(syspaudt) DSN(SYS3.ROSCOE.SYS) ACC(R) TSS PER(syspaudt) DSN(SYS3.ROSCOE.SYS) ACC(A) ACTION(AUDIT) TSS PER(roscoe stc) DSN(SYS3.ROSCOE.SYS) ACC(R) TSS PER(roscoe stc) DSN(SYS3.ROSCOE.SYS) ACC(A) ACTION(AUDIT) TSS PER(syspaudt) DSN(SYS3.ROSCOE.ROSLIB) ACC(R) TSS PER(syspaudt) DSN(SYS3.ROSCOE.ROSLIB) ACC(A) ACTION(AUDIT) TSS PER(roscoe stc) DSN(SYS3.ROSCOE.ROSLIB) ACC(R) TSS PER(roscoe stc) DSN(SYS3.ROSCOE.ROSLIB) ACC(A) ACTION(AUDIT)

b
ROSCOE resources must be properly defined and protected.
AC-4 - Medium - CCI-000035 - V-225600 - SV-225600r1029517_rule
RMF Control
AC-4
Severity
Medium
CCI
CCI-000035
Version
ZROST020
Vuln IDs
  • V-225600
  • V-17947
Rule IDs
  • SV-225600r1029517_rule
  • SV-23709
ROSCOE can run with sensitive system privileges, and potentially can circumvent system controls. Failure to properly control access to product resources could result in the compromise of the operating system environment, and compromise the confidentiality and integrity of customer data. Many utilities assign resource controls that can be granted to systems programmers only in greater than read authority. Resources are also granted to certain non systems personnel with read only authority.
Checks: C-27300r1029517_chk

Refer to the following report produced by the TSS Data Collection and Data Set and Resource Data Collection: - SENSITVE.RPT(ZROS0020) Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZROS0020) Ensure all ROSCOE resources and/or generic equivalent are properly protected according to the requirements specified in CA ROSCOE Resources table in the z/OS STIG Addendum. Note: Wherever an access or user group is missing, use the Site Security Plan to determine access and/or user group. If the following guidance is true, this is not a finding. ___ The TSS resources and/or generic equivalent as designated in the above table are owned or DEFPROT is specified for the resource class. ___ The TSS resource access authorizations restrict access to the appropriate personnel as designated in the above table. ___ The TSS resource logging is specified as designated in the above table.

Fix: F-27288r868752_fix

The ISSO will work with the systems programmer to verify that the following are properly specified in the ACP. (Note: The resources and/or resource prefixes identified below are examples of a possible installation. The actual resources and/or resource prefixes are determined when the product is actually installed on a system through the product's installation guide and can be site specific.) Ensure that all ROSCOE resources and/or generic equivalent are properly protected according to the requirements specified in CA ROSCOE Resources table in the z/OS STIG Addendum. Use CA ROSCOE Resources table in the z/OS STIG Addendum. This table lists the resources, access requirements, and logging requirements for ROSCOE ensure the following guidelines are followed: The TSS resources and/or generic equivalent as designated in the above table are owned or DEFPROT is specified for the resource class. The TSS resource access authorizations restrict access to the appropriate personnel as designated in the above table. The TSS resource logging is specified as designated in the above table. The following commands are provided as a sample for implementing resource controls: TSS ADD(dept-acid) ROSRES(rosid) TSS PERMIT(ALL) ROSRES(rosid.ROSCMD.ETSO) ACCESS(READ) TSS PERMIT(syspaudt) ROSRES(rosid.ROSCMD.MONITOR.) ACCESS(ALL) TSS PERMIT(syspaudt) ROSRES(rosid.ROSCMD.MONITOR.AMS) ACCESS(ALL) TSS PERMIT(ALL) ROSRES(rosid.ROSCMD.MONITOR.AMS) ACCESS(READ) TSS PERMIT(syspaudt) ROSRES(rosid.ROSCMD.) ACCESS(ALL)

b
ROSCOE Started Task name is not properly identified / defined to the system ACP.
IA-2 - Medium - CCI-000764 - V-225601 - SV-225601r958482_rule
RMF Control
IA-2
Severity
Medium
CCI
CCI-000764
Version
ZROST030
Vuln IDs
  • V-225601
  • V-17452
Rule IDs
  • SV-225601r958482_rule
  • SV-23711
Products that require a started task will require that the started task be restricted to certain resources, datasets and other system functions. By defining the started task as a userid to the system ACP, It allows the ACP to control the access and authorized users that require these capabilities. Failure to properly control these capabilities, could compromise of the operating system environment, ACP, and customer data.
Checks: C-27301r520862_chk

a) Refer to the following report produced by the TSS Data Collection: - TSSCMDS.RPT(@ACIDS) b) Review each ROSCOE STC/Batch ACID(s) for the following: ___ Is defined with Facility of STC and/or BATCH. ___ Is defined with Master Facility of ROSCOE. ___ Is sourced to the INTRDR. c) If all of the above are true, there is NO FINDING. d) If any of the above is untrue, this is a FINDING.

Fix: F-27289r520863_fix

The ROSCOE system programmer and the IAO 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. A sample is provided here: TSS CREATE(ROSCOE) TYPE(USER) - NAME('*STC* for ROSCO') DEPT(xxxx) - FAC(STC) - MASTFAC(ROSCOE) PASS(xxxxxxxx,0) - SOURCE(INTRDR) NOSUSPEND

b
ROSCOE Started task(s) must be properly defined to the Started Task Table ACID for Top Secret.
IA-2 - Medium - CCI-000764 - V-225602 - SV-225602r958482_rule
RMF Control
IA-2
Severity
Medium
CCI
CCI-000764
Version
ZROST032
Vuln IDs
  • V-225602
  • V-17454
Rule IDs
  • SV-225602r958482_rule
  • SV-24813
Access to product resources should be restricted to only those individuals responsible for the application connectivity and who have a requirement to access these resources. Improper control of product resources could potentially compromise the operating system, ACP, and customer data.
Checks: C-27302r520865_chk

Refer to the following report produced by the TSS Data Collection: - TSSCMDS.RPT(#STC) Automated Analysis Refer to the following report produced by the TSS Data Collection: - PDI(ZROS0032) Verify that the ROSCOE started task(s) is (are) defined in the TSS STC record.

Fix: F-27290r520866_fix

The ROSCOE system programmer and the IAO will ensure that a product's started task(s) is (are) properly identified and/or defined to the System ACP. A unique ACID must be assigned for the ROSCOE started task(s) thru a corresponding STC table entry. The following sample set of commands is shown here as a guideline: TSS ADD(STC) PROCNAME(ROSCOE) ACID(ROSCOE)

b
ROSCOE is not properly defined to the Facility Matrix Table for Top Secret.
IA-2 - Medium - CCI-000764 - V-225603 - SV-225603r958482_rule
RMF Control
IA-2
Severity
Medium
CCI
CCI-000764
Version
ZROST036
Vuln IDs
  • V-225603
  • V-17469
Rule IDs
  • SV-225603r958482_rule
  • SV-24943
Improperly defined security controls for the Product could result in the compromise of the network, operating system, and customer data. *****This vulnerability only applies to Top Secret started tasks. *****
Checks: C-27303r520868_chk

a) Refer to the following reports produced by the TSS Data Collection: - TSSCMDS.RPT(FACLIST) - Preferred report containing all control option values in effect including default values. - TSSCMDS.RPT(TSSPRMFL) - Alternate report containing only control option values explicitly coded at TSS startup. NOTE: The FACLIST report must be created by DECC security personnel. The TSSPRMFL report can be used if DECC security personnel have not executed the required steps documented in the TSS Data Collection. b) Review the FACLIST report. Ensure the Product Facility is properly defined as specified by the product system programmer. c) If the Product facility control options are defined as indicated by the product system programmer, there is NO FINDING. d) If any of the Product facility control options are not defined as indicated by the product system programmer , this is a FINDING.

Fix: F-27291r520869_fix

The Facility ROSCOE comes predefined with CA-TSS. Please ensure you add the following to your TSS parmlib for the FAC(ROSCOE): **** **** ROSCOE * **** FACILITY(ROSCOE=NOLUMSG,NORNDPW)

b
Resouce Class ROSRES is not defined or active in the ACP.
AC-25 - Medium - CCI-002358 - V-225604 - SV-225604r987853_rule
RMF Control
AC-25
Severity
Medium
CCI
CCI-002358
Version
ZROST038
Vuln IDs
  • V-225604
  • V-18011
Rule IDs
  • SV-225604r987853_rule
  • SV-24847
Failure to use a robust ACP to control a product could potentially compromise the integrity and availability of the MVS operating system and user data.
Checks: C-27304r520871_chk

a) Refer to the following report produced by the ACP Data Collection: - TSSCMDS.RPT(#RDT) b) Ensure that Product Resource Class(es) is (are) defined in the Resource Definition Table as follows: Note: Identify all of the attributes and charactistics of the Product resource class in the TSS Resource Definition Table (delete this note). RESOURCE CLASS = ROSRES RESOURCE CODE = X'hex code' ATTRIBUTE = MASK|NOMASK,MAXOWN(08),MAXPERMIT(044),ACCESS,DEFPROT ACCESS = NONE(0000),CONTROL(0400),UPDATE(6000),READ(4000) ACCESS = WRITE(2000),ALL(FFFF) DEFACC = READ c) If all of the items in (b) are true, there is NO FINDING. d) If any item in (b) is untrue, this is a FINDING.

Fix: F-27292r520872_fix

The IAO will ensure the Product resource class(es) is (are) defined in the TSS RDT. The IAO will issue one of the following commands to define the Product resource class(es): TSS REPLACE(RDT) RESCLASS(ROSRES) - MAXLEN(044) - ATTR(MASK|NOMASK,DEFPROT) - ACLST(NONE(0000),CONTROL(0400),UPDATE(6000),READ(4000),WRITE(2000),ALL(FFFF)) - DEFACC(READ) TSS ADDTO(RDT) RESCLASS(ROSRES) - RESCODE(hex-code) - ATTR(MASK|NOMASK,DEFPROT) - ACLST(NONE(0000),CONTROL(0400),UPDATE(6000),READ(4000),WRITE(2000),ALL(FFFF)) - DEFACC(READ)

b
ROSCOE configuration/parameter values are not specified properly.
AC-4 - Medium - CCI-000035 - V-225605 - SV-225605r987813_rule
RMF Control
AC-4
Severity
Medium
CCI
CCI-000035
Version
ZROST040
Vuln IDs
  • V-225605
  • V-18014
Rule IDs
  • SV-225605r987813_rule
  • SV-23714
Product configuration/parameters control the security and operational characteristics of products. If these parameter values are improperly specified, security and operational controls may be weakened. This exposure may threaten the availability of the product applications, and compromise the confidentiality of customer data.
Checks: C-27305r520874_chk

a) Have the the product system programmer display the configuration/parameter control statements used in the current running product to define or enable security. This information is located in the SYSIN DD statement in the JCL of the STC/Batch job. Automated Analysis Refer to the following report produced by the z/OS Data Collection: - PDI(ZROS0040) b) Verify the following specifications: Keyword Value EXTSEC TSS ACFEXT YES CLLEXT YES JOBEXT YES LIBEXT YES MONEXT YES PRVEXT YES RPFEXT YES UPSEXT YES c) If (b) above is true, there is NO FINDING. d) If (b) above is untrue, this is a FINDING

Fix: F-27293r520875_fix

The product system programmer will verify that any configuration / parameters that are required to control the security of the product are properly configured and syntactically correct. See the required parameters below: Example Keyword Value EXTSEC TSS ACFEXT YES CLLEXT YES JOBEXT YES LIBEXT YES MONEXT YES PRVEXT YES RPFEXT YES UPSEXT YES