Select any two versions of this STIG to compare the individual requirements
Select any old version/release of this STIG to view the previous requirements
Review the member CxxSTYLE in the DSIPARM DD statement concatenation of the NetView CNMPROC STC procedure. Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZNET0040). Verify that all NetView configuration requirements are specified. If the following guidance is true, this is not a finding. Keyword Value SECOPTS.OPERSEC SAFCHECK|SAFDEF SECOPTS.CMDAUTH SAF.FAIL|SAF.table
The systems programmer and ISSO will review NetView configuration parameters and control options for compliance. To ensure authentication of users to NetView, ensure that CxxSTYLE in the DSIPARM DD statement concatenation of the NetView CNMPROC STC procedure has the following initialization parameter(s) specified: (Note: The data set identified above is an example of a possible installation. The data set is determined when the product is actually installed on a system through the product's installation guide and can be site specific.) SECOPTS.OPERSEC=SAFCHECK|SAFDEF When SECOPTS.OPERSEC=SAFCHECK is used, it specifies that operator identification and password or password phrase checking is performed using an SAF security product. The operator identifier must also be defined in DSIOPF, and other attributes given to the operator at logon are taken from the specified profile for the operator in DSIPRF. Security access checks are checked against the authority of the operator that occur when an operator tries to access a data set that is protected in the DATASET class of an SAF product or an MVS system command that is protected in the OPERCMDS class of an SAF product. When SECOPTS.OPERSEC=SAFDEF is used, it specifies that operator identification and password or password phrase checking is done using an SAF security product. Authority to log on as a NetView operator is controlled through the APPL class. The operator identifier must be authorized to the resource name in the APPL class which represents the NetView program. The attributes given to the operator at logon are defined in the NETVIEW segment of the user profile for the operator in the SAF product. For more information, refer to IBM Tivoli NetView for z/OS Security Reference. When SECOPTS.OPERSEC=SAFDEF is specified, any value for SECOPTS.CMDAUTH can be used. Additional details can be obtained in the IBM Tivoli NetView for z/OS Security Reference. SECOPTS.CMDAUTH=SAF.FAIL|SAF.table When SECOPTS.CMDAUTH=SAF.table is used, table specifies the backup table to be used for immediate commands and when the SAF product cannot make a security decision. This can occur when: No resource name is defined in the NETCMDS class which protects or authorizes this command. The NETCMDS class is not active. The security product is not active. When SECOPTS.CMDAUTH=SAF.FAIL is used, command authority checking will fail if the SAF product can reach no decision. Additional details can be obtained in the IBM Tivoli NetView for z/OS Administration Reference.
Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(NETVRPT). Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZNET0000). Verify that access to the NetView install data sets are properly restricted. If the following guidance is true, this is not a finding. The RACF data set rules for the data sets restrict WRITE and/or greater access to systems programming personnel. The RACF data set rules for the data sets specify that all (i.e., failures and successes) WRITE and/or greater access will be logged.
The ISSO will ensure that WRITE and/or greater access to NetView install data sets is limited to system programmers only and all WRITE and/or greater access is logged. Auditors should be granted READ access. The installing systems programmer will identify and document the product data sets and categorize them according to who will have WRITE and/or greater access and if required that all WRITE and/or greater access is logged. The installing systems programmer will identify if any additional groups have UPDATE 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.NETVIEW SYS2A.NETVIEW SYS3.NETVIEW ad 'sys2.netview.**' uacc(none) owner(sys2) - audit(success(update) failures(read)) pe 'sys2.netview.**' id(syspaudt) acc(a) pe 'sys2.netview.**' id(audtaudt) ad 'sys2a.netview.**' uacc(none) owner(sys2a) - audit(success(update) failures(read)) pe 'sys2a.netview.**' id(syspaudt) acc(a) pe 'sys2a.netview.**' id(audtaudt) ad 'sys3.netview.**' uacc(none) owner(sys3) - audit(success(update) failures(read)) pe 'sys3.netview.**' id(syspaudt) acc(a) pe 'sys3.netvidew.**' id(audtaudt)
Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(NETVSTC). Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZNET0001). Verify that access to the NetView STC data sets are properly restricted. If the following guidance is true, this is not a finding. The RACF data set rules for the data sets restricts READ access to auditors. The RACF data set rules for the data sets restricts WRITE and/or greater access to systems programming personnel. The RACF data set rules for the data sets restricts WRITE and/or greater access to the product STC(s) and/or batch job(s).
The ISSO will ensure that WRITE and/or greater access to NetView STC data sets are limited to System Programmers and NetView STC only, unless a letter justifying access is filed with the ISSO. 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 WRITE and/or greater access and if required that all WRITE and/or greater access is logged. He will identify if any additional groups have WRITE and/or greater access for specific data sets, and once documented he will work with the ISSO to see that they are properly restricted to the ACP (Access Control Program) active on the system. Data sets to be protected will be: SYS3.NETVIEW.<systemid>.** (VSAM data sets) The following commands are provided as a sample for implementing data set controls: ad 'sys3.netview.<systemid>.<VSAMDS>.**' uacc(none) owner(sys3) - audit(success(update) failures(read)) - data('netview site VSAM data sets') pe 'sys3.netview.<systemid>.**' id(audtaudt) acc(r) pe 'sys3.netview.<systemid>.**' id(CNMPROC syspaudt tstcaudt) acc(a) The VSAM data set required for greater than READ access are: SYS3.NETVIEW.<systemid>.AAUVSPL SYS3.NETVIEW.<systemid>.AAUVSSL SYS3.NETVIEW.<systemid>.BNJLGPR SYS3.NETVIEW.<systemid>.BNJLGSE SYS3.NETVIEW.<systemid>.BNJ36PR SYS3.NETVIEW.<systemid>.BNJ36SE SYS3.NETVIEW.<systemid>.DSIKPNL SYS3.NETVIEW.<systemid>.DSILIST SYS3.NETVIEW.<systemid>.DSILOGP SYS3.NETVIEW.<systemid>.DSILOGS SYS3.NETVIEW.<systemid>.DSISVRT SYS3.NETVIEW.<systemid>.DSITRCP SYS3.NETVIEW.<systemid>.DSITRCS SYS3.NETVIEW.<systemid>.SDSIOPEN
Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(ZNET0020). Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZNET0020). When SECOPTS.OPERSEC=SAFPW is specified in ZNET0040, this is not applicable. Verify that all NetView resources and/or generic equivalents are properly protected according to the requirements specified in the NetView Resources table in the z/OS STIG Addendum. If the following guidance is true, this is not a finding. The RACF resource access authorizations restrict access to the appropriate personnel. The RACF resource access authorizations are defined with UACC(NONE) and NOWARNING.
The ISSO will work with the systems programmer to verify that the following are properly specified in the Access Control Program (ACP). (Note: The resource class, resources, and/or resource prefixes identified below are examples of a possible installation. The actual resource class, 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.) When SECOPTS.OPERSEC=SAFPW is specified in ZNET0040, this is not applicable. This can be bypassed. Ensure that all NetView resources and/or generic equivalents are properly protected according to the requirements specified in the NetView Resources table in the z/OS STIG Addendum. Additional details can be obtained in the IBM Tivoli NetView for z/OS Security Reference. Use the NetView Resources table in the z/OS STIG Addendum. This table lists the resources and access requirements for NetView, ensure the following guidelines are followed: The RACF resource access authorizations restrict access to the appropriate personnel. The RACF resource access authorizations specify UACC(NONE) and NOWARNING. The following commands are provided as a sample for implementing resource controls: RDEFINE NETCMDS netid.** UACC(NONE) OWNER(ADMIN) - AUDIT(FAILURE(READ)) DATA('Protected per ZNETR020') RDEFINE NETCMDS netid.luname.ADDCMD.** UACC(NONE) OWNER(ADMIN) - AUDIT(FAILURE(READ)) DATA('Protected per ZNETR020') PERMIT netid.luname.ADDCMD.** CLASS(NETCMDS) ID(syspaudt) ACCESS(READ)
Refer to the following report produced by the RACF Data Collection: - RACFCMDS.RPT(LISTUSER). Verify that the userid(s) for the NetView started task(s) is (are) properly defined. If the following attributes are defined, this is not a finding. PROTECTED
The NetView systems programmer and the ISSO will ensure that the product's Started Task(s) is properly Identified/defined to the System ACP. Most installation manuals will indicate how the Started Task is identified and any additional attributes that must be specified. A sample is provided here: au cnmpssi name('stc, netview') nopass dfltgrp(stc) - owner(stc) data('netview subsystem interface') au cnmproc name('stc, netview') nopass dfltgrp(stc) - owner(stc) data('netview')
Refer to the following report produced by the RACF Data Collection: - DSMON.RPT(RACSPT). Automated Analysis Refer to the following report produced by the RACF Data Collection: - PDI(ZNET0032). Verify that the IBM Tivoli NetView started task(s) is (are) defined to the STARTED resource class profile and/or ICHRIN03 table entry, this is not a finding.
The IBM Tivoli NetView system programmer and the ISSO will ensure that a product's started task(s) is (are) properly identified and/or defined to the System ACP. A unique userid must be assigned for the IBM Tivoli NetView started task(s) thru a corresponding STARTED class entry. The following sample set of commands is shown here as a guideline: rdef started CNMPROC.** uacc(none) owner(admin) audit(all(read)) stdata(user(CNMPROC) group(stc)) rdef started CNMPSSI.** uacc(none) owner(admin) audit(all(read)) stdata(user(CNMPSSI) group(stc)) setr racl(started) ref