What changed in z/OS ROSCOE for TSS STIG V7R2V7R2 changes

Check text

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). Verify that access to the ROSCOE Install data sets are properly restricted. If the following guidance is true, this is not a finding. The TSS data set rules for the data sets does not restrict UPDATEWRITE and/or ALTERgreater access to systems programming personnel. The TSS data set rules for the data sets does not specify that all (i.e., failures and successes) UPDATEWRITE and/or ALTERgreater access will be logged. If all of the above are untrue, this is not a finding. If any of the above is true, this is a finding.

Fix text

The ISSO will ensure that updateWRITE and allocate/createor greater access to program product data sets is limited to systemsystems programmers only, and all updateWRITE and allocate/createor greater access is logged. Security Personnel and Auditors should have readREAD access. The installing systems programmer will identify and document the product data sets and categorize them according to who will have updateWRITE and allocate/createor greater access and if required that all updateWRITE and allocate/createor greater access is logged. The installing systems programmer will identify if any additional groups have updateUPDATE access for specific data sets, and once documented, will work with the ISSO to ensure they are properly restricted to the Access Control Program (ACP) 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 datasetdata set 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)

V-225598 in V7R2

Check text

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. If the following guidance is true, this is not a finding. ___ The TSS data set rules for the data sets does not restrict UPDATEWRITE and/or ALTERgreater access to systems programming personnel. ___ The TSS data set rules for the data sets does not restrict UPDATEWRITE and/or ALTERgreater 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 text

The IAOISSO will ensure that updateWRITE and/or allocategreater/create access to the ROSCOE started task or batch job data sets is limited to systemsystems programmers and the started task only and all updateWRITE and/or allocategreater/create access is logged. The IAOISSO 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 datasetdata set 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)

V-225599 in V7R2

Check text

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.

V-225600 in V7R2

Title

ROSCOE Started Task name is not properly identified / defined to the system ACP.

Check text

a) Refer to the following report produced by the TSS Data Collection: - TSSCMDS.RPT(@ACIDS). b) Review each ROSCOE STC/Batch ACID(s). forIf the following: ___ Is definedattributes withare Facility of STC and/or BATCH. ___ Is defined, withthis Masteris Facilitynot ofa ROSCOEfinding. ___ IsFACILITY(STC, sourced to the INTRDR.BATCH) PASSWORD(xxxxxxxx,0) cSOURCE(INTRDR) If all of the above are true, there is NO FINDING. NOSUSPEND dMASTFAC(ROSCOE) If any of the above is untrue, this is a FINDING.

Fix text

The ROSCOE systemsystems programmer and the IAOISSO will ensure that a product's Started Task(s) is properly Identified identified/ defined to the Systemsystem ACP. If the product requires a Started Task, verify that it is properly defined to the Systemsystem 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

Discussion

Products that require a started task will require that the started task be restricted to certain resources, datasetsdata sets, and other system functions. ByDefining 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.

V-225601 in V7R2

Check text

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). VerifyIf that the ROSCOE started task(s) is (are) defined in the TSS STC record, this is not a finding.

Fix text

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

Discussion

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.

V-225602 in V7R2

Check text

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. NOTENote: 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 If the Product Facility is properly defined as specified by the product systemsystems programmer. c) If the Product facility control options are defined as indicated by the product system programmer, therethis 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 FINDINGfinding.

Fix text

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)

V-225603 in V7R2

Check text

Refer to the following report produced by the ACP Data Collection: - TSSCMDS.RPT(#RDT). EnsureIf thatthe ProductROSCOE Resource Class(es) is (are) defined in the Resource Definition Table (RDT) as follows: Note:, Identifythis allis ofnot thea attributes and characteristics of the Product resource class in the TSS Resource Definition Table (delete this note)finding. 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 If all of the items in (b) are true, this is not a finding. If any item in (b) is untrue, this is a finding.

V-225604 in V7R2

Check text

Have the product systemsystems 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). VerifyIf the following specifications:keywords specify the values in the ROSCOE configuration/parameter control member, this is not a finding. Keyword Value EXTSEC TSS ACFEXT YES CLLEXT YES JOBEXT YES LIBEXT YES MONEXT YES PRVEXT YES RPFEXT YES UPSEXT YES If the above is true, this is not a finding. If the above is untrue, this is a finding.

Fix text

The product systemsystems programmer will verify that any configuration/parameters that are required to control the security of the product are properly configured and syntactically correct. Refer to 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

V-225605 in V7R2